Problem maintaining a source code of the Java mapping in NWDI

[Former Member]

This is a two part question.

We've developed a Java mapping and need to preserve the source code somewhere, so we chose to create a Java development component in our project software component, along with a BPM project that is in the same software component.

Java mappings use AbstractTransformation. NWDS contains with the necessary dependencies to compile a class that extends the above. However, when we build the activity that contains a class that extends the above in NWDI, it fails, because NWDI is unable to find the dependencies. This is the first question - how do we make NWDI find the necessary dependencies?

The second issue that we are having is with the basic workaround that we have achieved for the above. We have commented the code out and commit just the comment to NWDI to compile. This resolves the dependency issue and does not cause any runtime issues since this code is not given to NWDI to create a runtime component. Instead it is promoted manually as a JAR, exported from NWDS, into ESR, and then it is promoted up to other environments as an ESR object. Here is the issue: NWDI is stuck trying to compiling an outdated version of this sources code, before it was commented out! No matter what changes we send up, it always tries to compile an outdated version. Is there some kind of cache in NWDI that can be refreshed? How can we force it to compile the latest changes?

[former_member189220]

Hello Leo,

If the initial question, in this forum thread, is answered from your perspective, then please click on the “Accept” link (to any of them) to complete this question. More details here. https://blogs.sap.com/2017/08/15/what-to-do-with-my-answered-questions/

Otherwise, please post more details on the present impediment you do face.

Thank you, in advance, for your contribution to the better administration of the SAP Community!

Regards,

[former_member189220]

Hello Leo,

1

"how do we make NWDI find the necessary dependencies?"

A.: You have define a product in the SLD. There you define the custom SCA and the Build-Time dependencies...

Defining Products in a Single Development Configuration

http://help.sap.com/SAPhelp_nw73/helpdata/en/49/0efe80f6934a18e10000000a42189b/content.htm?frameset=...

Working with Products and Software Components

http://help.sap.com/SAPhelp_nw73/helpdata/en/48/c46580095735b6e10000000a42189d/frameset.htm

Then you do "Update CMS" in the CMS - Landscape Configurator. In case you do use CM Services, you have to execute Check SCs from Software Component tab.

Then you execute import in the CMS - Transport Studio. In case of CM Services - you do synchronize with the RTS.

Imports

https://help.sap.com/viewer/39222f18c2ab428985c7f3e041b11e26/7.5.6/en-US/4910e94a3d9d132ee10000000a4...

Only then you can import the track / development configuration in the NWDS.

2.

"No matter what changes we send up, it always tries to compile an outdated version. Is there some kind of cache in NWDI that can be refreshed? How can we force it to compile the latest changes?"

A.: If you bypass the NWDI, then you do not need the activity. You can revert the activity from DTR UI and export and deploy manually the EAR file to the AS Java.

Deleting Open Activities in the DTR Web UI

https://help.sap.com/saphelp_nw70/helpdata/en/46/5d032c1e661cbee10000000a11466f/frameset.htm

3.

In case you do use NWDI, it is better to define the necessary build-time dependencies. You can refer to the required SCAs for a different type of development in these SAP notes:

1465468 Required SCs for Specific Type of Development in 7.1 Track

1463541 Required SCs for Specific Type of Development in 7.2 Track

1457908 Required SCs for Specific Type of Development in 7.3 Track

1572743 Required SCs for Specific Type of Development in 7.31 Track and 7.40 Track

2313256 - Required SCs for Specific Type of Development in SAP NetWeaver 7.5

Regards,