SAP NetWeaver Process Integration 7.1: Service Interface Implementation Example for Enterprise Service Consumption or Provisioning
I want to show you the different steps to execute when you implement a service interface in SAP NetWeaver Process Integration 7.1. In this particular example we will follow one of the service interface patterns introduced in this new version (the TU&C/C pattern). I won’t cover here the modeling and service provisioning and consumption proxies.
This blog also represents a summary document is supposed to link many other documents (referenced here) that will finally give a comprehensive idea of this topic:
- The “Web Services Reliable Messaging in SAP NetWeaver Process Integration 7.1” (http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/304335f7-f33c-2a10-ae80-9c9ffdc86415) : It introduces some details about WS-Reliable Messaging and its implementation in the forthcoming release.
- “Implementing a Distributed Two-Phase-Commit Scenario with Web Services and SAP NetWeaver PI 7.1” (http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00ffdb4d-e869-2a10-7688-891d7eea1b12) : It presents the TU&C/C pattern.
- In “Introduction to Global Data Types in SAP NetWeaver PI 7.1 (preview)” (http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4037b3fc-fb52-2a10-4888-e28362af626e): This article introduces the core components technical specification and how it is used to create the global data types.
- Also “Usability Features in SAP NetWeaver PI 7.1 Development and Configuration Times” (http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e7734f-e969-2a10-24b6-df58a710941c): SAP NetWeaver PI 7.1 includes a wealthy set of development utilities that together with the runtime stability and performance make this SAP NetWeaver component the natural choice for your process integration scenarios.
Before showing the steps proposed, I want to briefly introduce what could be the different approaches regarding process integration implementation.
-Development either already exists or starts in the application systems. You normally reuse existing WSDLs, BAPIs, data base tables, etc. Business Model is already defined; process integration can usually be seen as systems synchronization.
-The configuration is performed also in the application systems.
- Outside-In (also referred as “Central”):
-Development starts in the Enterprise Services Builder. Precisely in Enterprise Services Repository. You start by modeling the integration, later the SAP Application Systems are able to access and automatically create proxies for the service interface operations. Other technical integration methods are also available.
-The configuration is carried out centrally using the Integration Directory (optional).
Here I describe the list of steps required to implement a service interface. Consider that in order to see the recordings, you need the free SAP Tutor personal player. It can be downloaded directly from the service marketplace (https://service.sap.com/~sapidb/011000358700001572552002).
Create Basic Component in the ES Repository
First of all let’s take a very brief introduction to the development environment and an introduction to the topic: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/904e733f-5567-2a10-5f97-efed02306e69.
Create Service Interfaces
Supposing you already did the previous modeling, you should now go ahead and create you service interfaces and operations:http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30efd18a-5667-2a10-2ebc-b11032bfb9e4
Create the Operations Mappings
The operation mapping replaces the interface mapping, and you have to create one for each operation of the service interface: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ce8da5-5667-2a10-59b3-f780a94b37cd
After the design time activities have finished, it is time to update or confirm the configuration of the SLD objects: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/806520d0-5667-2a10-398b-c217ee345a95
Check Business Systems configuration in the Integration Directory
Before working on the specific configuration, you have to make sure the systems are properly configured in the Integration directory: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50ff30ec-5667-2a10-0eaf-f47f625f2c4f
Perform Configuration in the Integration Directory
Finally, you can go ahead and configure your integration: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8052b723-5767-2a10-8285-e2025088299a
Additional Steps for ABAP environments
After PI steps are done, it is time logon the back-end systems and create the proxies and consumer or provider methods, which are performed using wizards in a similar fashion than before using transaction SPROXY or the ABAP Object Browser (SE80).