12/23/2020 Adapter Module development in NWDI | SAP Blogs

Community

Ask a Question Write a Blog Post Login

Former Member
May 29, 2017 5 minute read

Adapter Module development in NWDI

7 Likes 7,147 Views 2 Comments

Like it or not, as a PI/PO developer one will eventually face the need to develop certain custom Adapter
Modules to ful ll speci c customer requirements. So in this blog we are going to describe how this can be done
in NWDS (SAP NetWeaver Development Studio) using NWDI (SAP NetWeaver Development Infrastructure). By
doing this, custom java developments are secured in a center repository and can be shared with other
developers easily.

Re-requisite: A Development Con guration is needed, which contains Build Time dependencies to at least
following software components:

ENGFACADE
SAP_BUILDT
SAP_XIAF

Once a Development Con guration is con gured and ready for use. We need to imported it into a NWDS client.

1). Create an EJB development component

Make sure that you are in the NWDS perspective “Development Infrastructure”, and proceed as follow.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 1/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

Note, if the naming reservation service has not been setup for the development con guration, you will only see
the vendor as “demo.sap.com” and with name pre x eld disable (as number 1 and 2 indicated above). It is ne
https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 2/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

like that, just give the development component a name separate either by “/” or “_”.

After clicking on “Finish”, the NWDS client would ask to switch to the “Java EE” perspective. Click on “No”, since
there are still a couple of things to be taken care of.

2) Create an EAR development component

Because an EJB development component cannot be deployed into a SAP PI runtime directly, we need to create
an EAR development component to do the deployment.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 3/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

Click on “Next” and “Next”. When promoted with which projects to refer to, tick the check box in front of the EJB
development component. So that when deploying the EAR into a PI runtime, the NWDS client knows it should
include the EJB development component.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 4/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

Click “Finish”. Then when the NWDS client asks to switch perspective, still click on “No”. Because we still have
one thing left.

3) Add dependencies to the EJB and EAR development components

Following Build Time dependencies are needed for the EJB development component:

sap.aii.af.ifc.facade
sap.aii.af.lib.facade
tc/bl/logging/api

To add a dependency to a development component, rst select it and then choose the tab “Dependencies”.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 5/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

Click on “Finish” and then repeat the same steps for the remaining dependencies. In the end It looks like below
for the EJB development component.

Then add Build Time, Deploy Time and Run Time dependencies for the EAR development component:

sap.aii.af.ifc.facade
sap.aii.af.lib.facade
tc/bl/logging/api

The process is pretty much the same as for EJB development component, only this time we need to tick the
checkboxes in front of Deploy Time and Run Time as shown below.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 6/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

In the end It looks like below for the EAR development component.

4) Java Session Bean creation

Now switch to the perspective “Java EE” to create a Java Session Bean. Expand the EJB project; navigate to the
folder “ejbModule”; and right click on it.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 7/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

Click on “Finish”.

A sample custom adapter module implementation would look like below:

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 8/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

Then add bean entries to the “META-INF/ejb-j2ee-engine.xml” le.

Now, we have completed the adapter module development.

5) Deploy the customer Adapter Module into SAP PI runtime

Go back to the NWDS perspective “Development Infrastructure” to build and deploy the EAR development
component.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 9/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

After deployment, you should be able to nd the adapter module from the SAP PI NetWeaver Administrator
(Path: http://<host>:<port>/nwa >> Troubleshooting >> Java >> JNDI browser).

Follow RSS feed Like

6) Check in the source code

Until now, we have deployed the custom Adapter Module into the SAP PI runtime, but still the Java source code
remains in the local NWDS client. Next we need to check in the source code, so that they are stored in the NWDI
server and are available for other developers to check and rework.

Now switch to the NWDS perspective “Development Infrastructure”.

Write some meaningful comments, so that one can always understand what has been done. He can revert it to
previous versions if needed.

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 10/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs

Alert Moderator

7) Remove the source code from a local NWDS client

Assigned tags
Because source codes have been checked into the NWDI server, we can now remove the developments from our
local NWDS
NW Java client. Infrastructure (NWDI) | SAP Process Integration | adapter module |
Development

Related Blog Posts

How to import SAP Projects into NWDI Track

By ARCHANA KUMARI , Mar 30, 2017
De ne an older JDK as the default for Build in NWDI 7.x
By Michael Pytel , Aug 05, 2014

How to setup NWDI with CM Services and CTS+ for Process Orchestration
By Former Member , Oct 10, 2013

Later on, if someone else want to have a look at the source code and work on it, he can just load the source
code from NWDI development con guration to his local NWDS client.
Related Questions

NWDI Set up for Custom Adapter module development

By Ravi Gupta , Oct 24, 2017

XI Adapter Framework SC marked with skipnwdideployment

By Former Member , Oct 16, 2007
NWDI newbie questions
By Former Member , Mar 23, 2010

Then he is ready to start working on any changes. But always remember to check in his changes to NWDI
server!

2 Comments

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

Ravi Gupta

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 11/12
12/23/2020 Adapter Module development in NWDI | SAP Blogs
October 27, 2017 at 9:44 am
Hi Kevin,

Nice blog. I followed the steps and deployed EAR on the PO development server.  During deployment, I am
getting a warning  –

DC admodule/ejb does not contain any archives for deployment

And the deployment sign is green. When I try to nd the module in JNDI browser, I see nothing. Am I missing
something.

Like(0)

Former Member | Post author

November 8, 2017 at 1:33 pm

Have you added entries in META-INF/ejb-j2ee-engine.xml?

Like(0)

Find us on

Privacy Terms of Use

Legal Disclosure Copyright

Trademark Cookie Preferences

Newsletter Support

https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/ 12/12