Skip to Content

How to Transport external JAR file in EP 7.02(Webdynpro Java) through NWDI

Aug 11, 2017 at 04:51 AM


avatar image


We have created a webdynpro java application and added an external jar file to that application in NWDS. We have added the jar file as mentioned below

project->Right Click-> Properties->Java Build Path-> Libraries-> Add External Jars

But While we are trying to Activate the Activity System is showing build error.

I will be thankful if anyone provide me the procedure of transporting external jar files in EP.

Thanks & Regards,

Subhadip Sengupta

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Milen Dontcheff
Aug 12, 2017 at 01:46 PM

If this external jar is a build library - such scenario is not possible. The required build libraries are defined in the project definition in the SLD.

After the SCA Build-Time dependencies are imported in the CMS - Landscape Confirugator.

Then when you import in the CMS - Transport Studio a central build with these libraries is done.

Then there is an import in the NWDS, of the dev. configuration track. With this the build libraries are copied and when a Sync is executed the DTR workspaces are copied to the local DTR workspaces.

At this very moment you do try to add a new build library. The activation fails because when the activity is activated it refers to a library that is not know by the CBS. (the activation of activity is happening on the CBS, after check-in and release of the activity from the NWDS)

The required and recommended build-time dependencies are stated in this note:

1080927 - Creating CMS Tracks for Common Application Types (7.0x)


Portal Application for NetWeaver 7.0 SAPBUILDT _ - SAPJEE _ - SAPJTECHS _ - EPBUILDT _ - EPPSERV _ -10003474.. EPBC _ - EPBC2 _ - EPWDC _


So what is supported as build libraries resides in these SCAs. If you do try to use something extra it is not necessary that it will work and it is not the NWDI to blame.

All in all, one might not add, per wish, an extra build libraries in the NWDS. What is necessary for the build process should be defined in the development configuration track.

Else, this jar file is a result of a compilation of a source code. Then it is better to add the source code in a local DC and to copy this local DC to a DC in the development configuration track imported from the NWDI. More information here:

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

Of course the relationship between the puplic parts, from and to, this DC, is an extra task for the developers. The copied DC should be referred correctly otherwise the build will failed with a Broken DCs - f.e. "INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid as they refer to non-existent public parts."

Adding an extra libraries to a certain local project will work only if you do a local development. Then you need to deploy the project, in at least SDA, directly from the NWDS to the AS Java RTS.

1833230 - deployment of j2ee archive which is no SDA is not supported

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

However, as you might see here the result will be "a J2EE Engine 7.0-compatible EAR file that contains all necessary components and deployment descriptors".

10 |10000 characters needed characters left characters exceeded
MADHU N G Aug 14, 2017 at 09:30 AM

Hi Subhadip,

Create an external library DC and add the required jar files into libraries folder. Then create a Public part in the library DC and then provide reference to the jar file.

Now add this External Library DC as Dependent DC to your Webdynpro DC. This should solve the issue.

Let me know if you need further info.



10 |10000 characters needed characters left characters exceeded