Preparing the Systems 

To import Support Packages smoothly in an NWDI-driven system landscape, the following prerequisites must be fulfilled.

Shared Transport Directory for CMS Server and the WebAS Java Runtime Systems

Before you can use the JSPM to import Support Packages into an NWDI-driven system landscape, the CMS server and the WebAS Java runtime systems must share a transport directory. This directory is used to exchange data between the NWDI and JSPM.

If you cannot perform this reconfiguration, some manual steps are required (see Appendix: Special Cases).

Required NWDI Version

The server on which the NWDI is running must have at least version NetWeaver 04s, Support Package 5.

If you have distributed your NWDI across multiple SAP WebAS Java systems to accommodate your project, we recommend that you keep the entire NWDI on the same version.

Version of the Runtime Systems

The J2EE runtime systems into which you want to import Support Packages must have the version NW04s SP 5.

If not, you must deploy the following software deployment archives in these systems:

●      SLUtiljddschma.sda

●      SLUtil.sda

●      cvers.ear

These SDAs are available as attachments in SAP Note 901520.

Reconfiguration of the Runtime Systems

Up to and including NetWeaver 7.0 Support Package 4, you need only to enter the connection data for communication with the Software Deployment Manager (SDM) when you configure runtime systems in tracks. As of SP 5, you also need to specify connection data for SAP WebAS Java:

●      URL of the server

●      User with administrator authorizations

●      Password

This data enables the deployment information about the imported software components to be updated in the relevant runtime system.

To specify this data, choose the Runtime Systems tab page for each track in the CMS Landscape Configurator and enter the required data for the runtime systems. (See also Configuring Runtime Systems.)

The user with the administrator authorizations must have been created in the appropriate runtime systems.

Setting the Import Locks in the Test Systems and Production Systems for All Tracks

To avoid unscheduled development transports into the runtime systems, you must lock the import queues of the test systems and production systems in the CMS Transport Studio (see also Changing the Status of the Import Lock).

For more information, see:

Maintenance of an NWDI-Driven System Landscape

Start of the Support Package Import Process