Skip to Content
Author's profile photo Shabarish V Nair

The Code Life Cycle – Managing Custom Code?

In majority of projects that implement SAP PI, developments that require custom adapter modules and java proxies are predominantly less in number. But there are projects in which the most of the developments are based on such custom codes. Also with the single stack concept gaining importance, these developments will gather more storm.


How do you manage your Java code when it comes to SAP PI? 


I assume most of us don’t really bother. We get our coding done on NWDS, compile the code locally, export the Jar or EJB, load them into the server and Voila, we are done.

But as the code base increases, managing this gets tricky. PI, out of the box doesn’t provide you any help either. You can edit your code in ESR but only hope for it to compile on itself. If it could, it would have been wonderful, aint it?

One of the recommended ways is to implement NWDI and have the code centrally maintained. But I personally haven’t found it easy configuring NWDI and start hosting my code. Ignoramus? Mea Culpa! (Maybe SAP can indeed host a good how to guide to help us with this?)

With Eclipse integration into ESR, I believe this will open a new dimension of possibilities. Imagine code management via the IDE integrated with a check in – check out version management feature.

I hope this is what SAP is aspiring toward. In any case, I have already posted this on Idea place and will wait to see if anyone picks this up.



How do you manage your custom Java code? Do you use NWDI extensively for SAP PI projects? Or is there any other way you are achieving this in your SAP PI projects?

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Hi Shabarish,

      I think a good practice for Java Mappings or Java Code used in UDT's to simply put it in the same zip/jar file that you upload into ESR.

      Then the code will always be in the same place with the artefacts that use it and are related to it (other EAI Design runtime's do it the same way).

      For furtheron developments it will be very easy to spot the code then in the place were its used (e.g. download it into NWDS/eclipse and change).

      For Java Proxies, yes there is the only way to do it with NWDI (that#s indeed quite complicated)

      Will be interesting how this will be handeled when the ESR editors move completely into NWDS, but i guess ESR repository will still be centrally stored/versioned.

      With best regards

      Author's profile photo Former Member
      Former Member
      Hi Shabarish,

      I'm using extensively NWDI to manage all the custom adapter modules we are developing, which in a couple of years have grown a lot. I'll try to find time to post a weblog about developing an adapter module within the NWDI infrastructure.

      Anyway, I agree that with PI turning more an only java environment, the ideal way to integrate the java developments would be like you say.

      Author's profile photo Shabarish Vijayakumar
      Shabarish Vijayakumar
      Blog Post Author
      thanks Jorge. It will be great if you could elaborate NWDI setup over a blog or wiki 🙂

      and yes, plugging in NWDS into ESR should also open up ways for code management.