SLD + NWDI set up for Custom Adapter module development : Dependencies issues ?

[mhuchet]

Hi,

I want to develop a Custom Adapter Module for my SAP PO 7.5, from NWDS 7.5 connected to NWDI.

For that, I am following this blog: https://blogs.sap.com/2017/05/29/adapter-module-development-in-nwdi/

Based on oss note "2313256 - Required SCs for Specific Type of Development in SAP NetWeaver 7.5", for a "J2EE", we should add these 2 dependencies to our SC:

• ENGFACADE
• SAP_BUILDT

But based on above blog, we should have these 3 dependencies :

• ENGFACADE
• SAP_BUILDT
• SAP_XIAF

So in doubt, in my SLD, I created a SWCV and in its dependencies, I added these 3 "Build Time" SC:

• DI BUILD TOOL 7.50 <=> SAP_BUILDT
• J2EE ENGINE FACADE 7.50 <=> ENGFACADE
• XI ADAPTER FRAMEWORK 7.50 <=> SAP_XIAF

Then in NWDI CM services, I added my new SC to my Development Configuration, and I am well seeing its 3 dependencies. 🙂

But, in NWDS, I have 2 problems 😞

Problem n°1:
when I create an EJB or EAR Development Component, e.g "af/rest/xxx/ear", me I have a prefix = "bpm/", and so my full name is "bpm/af/rest/xxx/ear".

• Is it normal to have this "bpm" prefix ? whereas I am NOT developing a BPM, but for a custom Adapter Module !
• Can I change somewhere this "bpm" prefix name ?

Problem n°2:
to my EJB or EAR Development Component "bpm/af/rest/xxx/ear", when I want to add the lib dependencies, still by following the blog, me I CANNOT add these 2 below ones.
it look,like my "SAP_XIAF" is empty 😞

• sap.aii.af.ifc.facade of SAP_XIAF
• sap.aii.af.lib.facade of SAP_XIAF

So where is the true ? should I have this "SAP_XIAF" SWCV in BuildTime dependencies of my SC (in SLD)?

regards

Mickael HUCHET

[mhuchet]

Hi Ryan,

yes, I saw also this blog and I used that solution several years ago, but here I would prefer to use the NWDI approach. I will continue to search, else if someone know what could be the reason of my above problems, I am interesting by your point of view.

Thanks

Regards

Mickael HUCHET

[Ryan-Crosby]

Hi Mickael,

I actually found the original document from SAP that I had used in reference previously and it describes the method in the blog. As far as using NWDI it has been a long time for me so I can't offer any guidance. My feeling is that if SAP has a guide showing this other method then it is surely ok to use - sometimes I feel like we get too many options and it's difficult to sort out when one should be used vs. another.

Regards,

Ryan Crosby

[Ryan-Crosby]

Hi Mickael,

I have done custom adapter module development a little differently in the past, which may get you around these two problems. What I had done for the EJB project was to download the required libraries from the PI/PO system, and reference them as external JARs so I could run the build. In the top level EAR project I then reference the EJB project for the build of the EAR which will get deployed, and then maintain the web XML file metadata.

Something more like this blog:

https://blogs.sap.com/2019/05/03/how-to-create-custom-adapter-module-in-sap-pipo-for-ejb-3.0-version...

Regards,

Ryan Crosby