Build Integration Scenarios Entirely within SAP NetWeaver Developer Studio: The Enterprise Services Repository Perspective
- by Dr. Volker Stiehl, Professor, Ingolstadt Technical University of Applied Sciences
- January 26, 2012
Starting with SAP NetWeaver Process Orchestration 7.31, it is possible to develop complete integration scenarios entirely within SAP NetWeaver Developer Studio. Before the introduction of new perspectives within SAP NetWeaver Developer Studio, the Swing-based clients Enterprise Services Builder and Integration Builder had to be used for this purpose. Learn how to work within the Enterprise Services Repository perspective to build the basic artifacts (e.g., data types, message types, service interfaces, message mappings, and operation mappings) on which every integration scenario relies.
The Enterprise Services Repository perspective in SAP NetWeaver Developer Studio is used to model all the artifacts that represent messages and mappings. The artifacts are being used within the integration engine of the Advanced Adapter Engine Extended, the Java-only deployment option of SAP NetWeaver Process Integration. Over time the perspective takes over the functionality you most probably know from the Enterprise Services Builder, the Swing client for maintaining design time artifacts in the Enterprise Services Repository.
SAP has decided to strategically move into the Java world for SAP NetWeaver Process Integration (SAP NetWeaver PI). This move was proven by the first Java-only deployment option of SAP NetWeaver PI called Advanced Adapter Engine Extended (AEX). For more information about AEX, see the introductory article “SAP NetWeaver 7.3 AEX: A New Installation Option for SAP NetWeaver PI” by Elke Doering and Peter Gutsche.
With the latest offering, SAP NetWeaver Process Orchestration 7.31, which is in essence a combined installation of SAP NetWeaver Business Process Management (SAP NetWeaver BPM), SAP NetWeaver Business Rules Management (SAP NetWeaver BRM), and the AEX on one Java Virtual Machine (JVM), the next step was done: The functionality of the modeling and configuration tools moved as dedicated perspectives into SAP NetWeaver Developer Studio. Consequently, there will be no further investments in new functionalities for the two Swing clients called Enterprise Services Builder and Integration Builder.
Whereas the Enterprise Services Builder functionality was already addressed in the Enterprise Services Repository perspective (ESR perspective) in SAP NetWeaver Developer Studio, the Integration Builder functionality is now covered with SAP NetWeaver Process Orchestration 7.31 as a new SAP NetWeaver Development Studio perspective in the Process Integration Designer (PI Designer). To show what is already covered in the new perspectives, I will guide you through a complete integration scenario and how it is built from scratch using only the SAP NetWeaver Developer Studio-based tools. As you follow the steps in this scenario, you experience a new modeling and configuration approach for message handling in the AEX. In this installment I will concentrate solely on the ESR perspective.
Would you like to see this full item?