Check-in Java Mappings from NWDS to Imported Archive

[helmut_skolaut3]

Hi all,

when I am exporting a Java Project to ESR into an imported Archive for a standalone project it works fine:

It works fine:

We have now introduced NWDI and I am synchronizing all developments with the DTR. When I want to export the project as .jar-File to the local file system and import from the Enterprise Service Repository perspective the .jar-file again into the Imported Archive, it works fine.

Nevertheless it's not convenient enough for me. I want to do it same way like above but after I have chosen the Change List and pushed the "Finish" button, nothing happens.

I have analyzed that using WireShark and there is only one HTTP request/response pair logged in that case that looks identical to the first HTTP request/response pair of the approach with a standalone project.

Does anybody know what I am doing wrong, where I can find further logging, or maybe know that problem and its solution?

Regards
Helmut

[former_member189220 · Accepted solution]

Provided, you have not found a workaround or (re)solution, I would like to point out some things about your scenario:

1. It is not possible to export EAR, SDA, SCA or other archive from the NWDS and to import it in the NWDI. More details in this SAP KBA:

2473044 - Assembly in CMS & export in NWDS are they compatible?

2. If NWDI is involved, one should create development configuration track (in it add the SCA(s) that is "To Be Developed") and import this dev.conf.track in the NWDS. Then one might execute a copy of the DC from the local development configuration to the one, imported from the NWDI. More information here:

Working with Development Configurations

Creating a Development Track

Migrating Local Developments to a Centralized NWDI Environment (Developer's Viewpoint)

(Step 3: Copying Local DCs to NWDI Track SC )

3. If this does not work for your scenario, you might consider to use CTS+ and make the necessary granularity there. Only you need to make sure to convert the file (that you transport between the systems defined in the TMS) in a format that is compatible with the NWDI and AS Java where it will be deployed. In other words one might NOT use the EAR file (in such format) in a software logistics scenario (unless it is not converted before that). More explanations in SAP note: 1833230- deployment of j2ee archive which is no SDA is not supported

If you have standard j2ee archives that you want to transport with CTS+, you must convert them to valid SAP archives before transporting them. For more information, see the following documentation:

SAP NetWeaver 7.3: http://help.sap.com/saphelp_nw73/helpdata/en/4a/f06fb255332475e10000000a42189c/frameset.htm

SAP NetWeaver 7.3 EhP1: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4a/f06fb255332475e10000000a42189c/frameset.htm

In case you have more specific questions please let me know.