How to convert WAR application to be able to deploy it with JSPM and SDM?

[Former Member]

We have to be able to deploy an application packaged in WAR file usign the JSPM and SDM GUI tools.

Using the Deploy tool there are no problems to build EAR file from the WAR and deploy it successfully to tha Application Server.

How should we convert our WAR application, or the EAR file created with the DeployTool in order to be able to use these 2 tools?

Using that EAR file with the JSPM and SDM GUI tools doesn't work:

JSPM

The ear file is copied in the inbox directory, but there is the following message:

No applicable support package stack(s) found for deployment in inbox directory
server\sapmnt\trans\EPS\in

SDM GUI:

When providing the EAR file created with the DeployTool, the SDM GUI fails to add it:

com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

After adding these attributes, we couldn't manage to provide valid manifest header.

How can we modify/create valid manifest in order to be able to use the SDM GUI tool?

Please, give us directions how to convert our WAR package in order to use these tools?

[Former Member · Accepted solution]

Hi Sam

Check out the below link

http://help.sap.com/saphelp_nw2004s/helpdata/en/1b/92e4e701b242c2833a7adde6ecad09/frameset.htm

If you have an already built war file then most probably the easiest way to assemble it and deploy it will be to use the deploy tool (http://help.sap.com/saphelp_nw04/helpdata/en/35/e3ee3da7138e5be10000000a114084/frameset.htm) Usually we use the NetWeaver Developer Studio to build and deploy J2EE Applications (http://help.sap.com/saphelp_nw04/helpdata/en/fe/a3996fa314f94f8a0c3475b08636d0/frameset.htm).

OR

As i understand you the source files arent available so rebuilding is out of question.

0. Add web-j2ee-engine.xml in the same path as web.xml

<web-j2ee-engine>

<login-module-configuration/>

</web-j2ee-engine>

1. Create a Dummy EAR file.

2. Add the WAR file to the base directory (path should be blank if you view the EAR in WinZip).

3. Open the application.xml and add the entry for the WAR file

<application id="Application_ID">

<display-name>EAR_Name</display-name>

<module id="WebModule_1127381405488">

<web>

<web-uri><WAR NAME>.war</web-uri>

<context-root>sampleContextRoot</context-root>

</web>

</module>

</application>

Note: The number in module id has some significance, for the time being you have any random number.

Deploy the EAR.

Reward points if usefull