GRC
HR
SCM
CRM
BI


Article

 

The insideEdge (SAPinsider Vol. 4, Iss. 4)

by Franz-Josef Fritz | SAPinsider

October 1, 2003

by Franz-Josef Fritz, Vice President NetWeaver Product Management and Standards, SAP AG SAPinsider - 2003 (Volume 4), October (Issue 4)
 

Creating an application and then advancing it through its life-cycle paces takes a toll on an IT organization. Developing a business application is clearly a big effort. But so is ushering that application through testing and integration cycles, transporting it to production environments that may span different systems and stretch across different countries, ensuring its high availability, and then monitoring, managing, and updating that software. The ABAP development community learned these lessons early on, and we at SAP right along with them. With R/3 and the ABAP environment, we had more than 10 years to master these life-cycle issues and to deliver tools for higher productivity and quality.

Now the younger Java development community is facing the very same pain points. Normally, Java developers have to manually deal with deployment and distribution issues. They are also finding diminishing productivity returns as the size of their development group grows. Typical Java development environments don’t yet have the kinds of efficiencies ABAP developers take for granted — in particular, they lack the automated and consistent creation of executables, a central dictionary for data types and DBMS table definitions, a change management system, and tools for automated testing. But they should, and they can with SAP Web Application Server.

SAP Web Application Server will offer your Java developers an equally robust and scalable development and runtime environment as it offers your ABAP developers — on one common platform. This has profound TCO implications for your Java-based application development initiatives and for your system management: you maintain only one application infrastructure, you reduce the number of different application server types and administration tools, you increase development productivity and quality significantly, and you can adapt the infrastructure to the hardware size and OS/DBMS combination of your choice to meet your needs.

You can start testing the waters with this Java development platform right now. For many of you, the technology is in-house already, or soon will be. SAP Web Application Server is the foundation platform for SAP R/3 Enterprise, mySAP ERP, mySAP SCM, mySAP CRM, mySAP SRM, mySAP BI, and more. If you have any of these solutions, you have SAP Web Application Server. The application platform is also the foundation layer on which SAP NetWeaver components are built. So if you have SAP Enterprise Portal, BW, or XI, you have SAP Web Application Server. And it is the platform upon which xApps are built.

Let me close with this note: The impact of Java on the whole SAP solution landscape will grow over time. It’s a good idea for ABAP and Java developers alike to get prepared.

An email has been sent to:






More from SAPinsider



COMMENTS

Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!


SAPinsider
FAQ