Skip to Content

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

/wp-content/uploads/2012/03/pic1_88572.png

c.       Enter the appropriate location for the ESR:

/wp-content/uploads/2012/03/pic2_88573.png

2.       In NWDS:

a.       Connect to the ESR:

/wp-content/uploads/2012/03/pic3_88583.png

b.      Enter authorization to access the ESR:

/wp-content/uploads/2012/03/pic4_88584.png

c.       The SWCVs and objects will open up on the left pane:

/wp-content/uploads/2012/03/pic5_88585.png

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”:

/wp-content/uploads/2012/03/pic6_88591.png

b.      To display an existing Data Type, double-click on an object:

/wp-content/uploads/2012/03/pic7_88587.png

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:

/wp-content/uploads/2012/03/pic8_88588.png

5.   Message Mapping can also be created with a GUI tool using drag-n-drop:

/wp-content/uploads/2012/03/pic9_88589.png

6.   Mapping functions are also available:

/wp-content/uploads/2012/03/pic10_88590.png

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.

To report this post you need to login first.

25 Comments

You must be Logged on to comment or reply to a post.

  1. Gautam Purohit

    Hello William,

    Thanks for the informative blog.

    Can you please guide me about how can I change the context of a field using NWDS while creating the message mapping?

    Regards,

    Gautam Purohit

    (0) 
    1. William Li Post author

      At the current version, you will have to use the Node functions.  In the future, there will be a GUI mapping tool in Eclipse, but I do not have any details on whether this capability will be there.

      Regards,

      Bill

      (0) 
  2. Jocelyn Dart

    Thanks Bill,

    Agree re easier-to-use… I used to find Swing editor very confusing. The new editor is much easier to understand and work with.

    (0) 
  3. Rashmi Joshi

    Thank you william…. But I’m new to term Eclipse… I think u ve provided NWDS screen shots here… Where is eclipse tool here???

    Please clear my doubt/confusion.

    Regards,

    Rashmi Joshi

    (0) 
  4. Pavel Korinek

    Hi William,

    Can I use iFlow in NWDS for SAP PI 7.31 dual stack (not AEX)? ESR (Repository) works well, but when I want to connect iFlow (Integration directory) errors occurs: “SAP Process Integration Designer is supported for AEX usage type from release 7.31 onwards”.

    My version is:

        SAP PI: 7.31 SP07

        Eclipse: SAP NWDS EHP 1 for SAP NetWeaver Developer Studio 7.3 SP06

    Thanks for reply.

    Regards,

    Pavel.

        

    (0) 
      1. Amith Dharmasiri

        Hi William,

        We are trying to implement single stack PO 7.4. Our infrastructure team have some quetsions below. Do you have any suggestions or recommendations? If there are documents that our team can take a look, that will be helpful as well.

        Specific topics:

        1. Exactly what are we installing in the DMZ:  an AEX?  I ran across some SAP documents that mentioned “Java Proxy” and “ABAP Proxy” as separate entities, but I could find no detailed information.
        2. Assuming we are going with an AEX – how does this impact sizing?  My understanding is some portion (or possibly even most) of the overhead associated with the external facing interfaces would shift from the PI/PO instance to the AEX. Do we have any idea how much? Since PI/PO and AEX will be on separate servers, it is important that we get this split correctly to avoid either the AEX or PI/PO instance becoming a performance bottleneck.
        3. Does the AEX consume PI/PO licenses (core licenses)?

        Thank you.

        Amith

        (0) 
        1. William Li Post author

          Hi Amith,

          Your questions are somewhat confusing to me.  Below are some notes for PO and AEX.

          • PO is a single-stack (Java) installation, licensed by core, consisting of 3 components (AEX, BPM and BRM).  Although, with this license, instead of installing AEX, you can install a dual-stack PI.  But, the recommended architecture is the single-stack with AEX.
          • There is nothing to be installed in the DMZ.  However, if you need to integrate with external partners, you will need a reverse-proxy in the DMZ, which can be the SAP WebDispatcher or another product of your own.  This is no different than your existing dual-stack PI requirement for external integration.
          • You should not need a PI/PO and AEX, since AEX is just another name for single-stack PI.

          Of course, after all this explanation, you are actually referring to AAE (Advanced Adapter Engine).  Below are some notes on AAE:

          • AAE is normally used to process special messages or to locate your integration in a different geographic location, but still retain central development and operations.  Many times this is used to setup a “federated” PI environment.
          • AAE is install on a separate server, with a different SID.  But it is “connected” to the central PI system.  AAE cannot operate by itself, it requires a PI system.  The PI system can be AEX also.
          • During runtime, AAE has its own message processing engine, therefore, no need to interact with the central PI system.  In another word, there will be no bottlenecks between the PI and AAE.
          • For external integration, you will still need a reverse-proxy in the DMZ, e.g. WebDispatcher.  You can install AAE in the DMZ, but not normally done, unless you have some special requirement.
          • If you want to use AAE specifically for external integration, you should consider just using your existing PI system with a reverse-proxy in the DMZ.

          Regards,

          William

          (0) 
  5. Christopher Probert

    Hi William,

    Many thanks for this and your many other useful blogs. Could I ask for a clarification on your statement:

    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.

    I have been trying to find exactly this, a place where all gaps between the swing based ESR and ID and the NWDS capabilities are documented in one place – was this ever done? if so could you possibly link to it in this blog to make it easier to find? I searched blogs, articles and help.sap.com and could not find any concise list of gaps.

    Many thanks

    Chris

    (0) 
  6. Tanmay Pilane

    Hi William,

    I’ve created an sample IFlow in nwds 7.3.

    But I’m unable to see the Mapping in PO, which i have created in NWDS, so it is giving me mapping exception, when i m trying to run the scenario.

    Regards,

    Pilane.. 🙂

    (0) 
    1. William Li Post author

      Hi Pilane,

      Did you create an Operations Mapping?  The OM must use the same sender and receiver interfaces as what you used in iFlow in order for you to see it.

      Regards,

      William

      (0) 
  7. Alexander Apel

    Hi William,

    i had configured the NDWS like your sample, but now i cant connect to the ESR.

    Error.jpg

    when i start the “normal – Enterprise Services Builder – SwingGUI” my credentials are accepted.

    can you help me?


    Regards,

    Alex

    (0) 

Leave a Reply