Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

Importing Objects into the ESR

Objective

After completing this lesson, you will be able to import objects into a process

ESR Interface Importation

You can create required objects in the Enterprise Services Repository (ESR) of a Java AS. These objects can then imported into the process in SAP NetWeaver Developer Studio (NWDS).

The easiest way to import interfaces from the ESR is to choose the Import function of service interfaces in the product. The import starts with a selection from which source an object shall be imported. Here the ESR can be chosen. A prerequisite is, that the locally installed NWDS is linked to a ESR of an AS Java. If the assignment works, the ESR is displayed, and the required object can be chosen.

To Export ESR Objects

To export the ESR objects, use the high level procedure as follows:

Steps

From the SAP PI landing page of the source system, launch the ESR.
In the ESR, right-click on the software component or namespace that you would like to export, and then choose the Export button.
You are then required to specify a location on your local file system in which to save the TPZ file. Don’t forget to properly name the TPZ file.
If you want like to export multiple software components, then repeat steps 1 to 3 for each software component.

To Import the Data to ESR

To import the data that you just exported from the previous steps, use the high level procedure as follows:

Steps

From the target SAP Process Orchestration (PO) landing page, launch the ESR.
On the menu, choose Tools, and select Import Configuration objects. You will then see a pop-up menu, from which you need to select Client and choose the TPZ file from your local file system.
Once you have selected the file, choose Import.
Steps 1 to 3 can be repeated multiple times if you want to export more software components or namespaces.

Interfaces for Trigger Creation

Depending on the business process and application functionality to be supported by a service interface belongs to one of these categories:

Inbound
Outbound
Abstract

Service interfaces represent the principle deliverable as a result of the activities performed during design time in the ES Repository. Once the service interface is ready, it can be released for proxy generation and further implementation on the application side (for example, an SAP ABAP or Java back end system). During the process of proxy generation, the following development objects will automatically be created on the application side:

Proxy development objects (that is, classes, methods, and data types): A service definition for mediated or point-to-point communication using the Web service runtime.
Inbound (service provider): You want to expose specific application functionality available on the back end system to service consumers. The consumers of your services can be either other application systems or humans. From an SAP PO perspective, the system receiving or processing the requests is the inbound or server (proxy) application.
Outbound (service consumer): You need to consume information provided by an external system from your back end system. The invocation of an outbound service can be either automatically or manually triggered from the back end system. From an SAP PO perspective, the system sending the messages is the outbound or client (proxy) application.
Abstract (only applicable for SAP Process Integration (PI) dual-stack systems): A special type of interface used in integration processes, and part of the cross component Business Process Management (ccBPM) framework. Abstract interfaces cannot be used to generate and implement service interfaces on the back end system. Furthermore, they can only run under dual-stack (ABAP) systems and therefore are not applicable for SAP PO Java-only systems.

Next lesson