Since the blog featuring the iFlow tool in Eclipse to configure integration scenarios, I’ve received a few questions from readers and colleagues on whether a similar tool is also available for the ESR. I am happy to say “yes”. The Eclipse ESR tool has been available on a limited base since CE 7.2. With PI 7.31, this tool has been additionally improved. Without going into a full-feature and how-to discussion in a blog, let me just go into the main capabilities. We can create, update and view Data Types, Message Types, Service Interfaces, Message Mapping, etc., all the objects necessary to create an integration scenario.
A step-by-step guide of using Eclipse with the ESR can be found at https://scn.sap.com/docs/DOC-27343.
1. Accessing the tool in Eclipse with the ESR plug-in. The plug-in is available with the NetWeaver Developer Studio (NWDS).
a. In NWDS, go to menu: Window à Preferences
b. Go to: Web Services à Enterprise Service Browser
c. Enter the appropriate location for the ESR:
2. In NWDS:
a. Connect to the ESR:
b. Enter authorization to access the ESR:
c. The SWCVs and objects will open up on the left pane:
3. Create, modify and view the objects:
a. Create objects by right-click on the object type. Using Data Type as an example, click on “New Data Type”:
b. To display an existing Data Type, double-click on an object:
c. To create or update the object, click on the “Add Element” or “Add Attribute” button
4. One difference between the Eclipse version and the Swing version is that when we create Service Interfaces, we do not need to create the Message Type first. This step is included when creating the Service Interface. Using the example below, click on the Operation will take you to select the Data Type and provide a Message Type name:
5. Message Mapping can also be created with a GUI tool using drag-n-drop:
6. Mapping functions are also available:
As the first major release of the Eclipse tool in PI 7.31, there are still some gaps between the Eclipse version and the Swing version. These gaps will be filled in future service packs and enhancement packs.
Whether the Eclipse or Swing tool is used, they both share the same database. Therefore, the work done using the Swing tool will also be visible from the Eclipse tool, and vice versa.
In the future, the gaps between the different releases and SPs will be detailed. This will either be done via a blog, article or SAP documentation.
In my humble opinion, the Eclipse tool is definitely much easier to use, especially for those who had used Eclipse without any previous SAP knowledge. The learning curve is much lower. For those who had used the Swing tool in ESR, the Eclipse tool is even easier since the concept of working with the various objects is already there, e.g. the relationships between Data Type, Message Type and Service Interface.
- SAP Managed Tags:
25 Comments
