Preparation Steps 

Use

Order of the Systems

You must specify the order in which you want to provide the systems with Support Packages or upgrades. In a track, the SAP NetWeaver Development Infrastructure (NWDI) recognizes four system roles (Development – Consolidation – Test – Production) which define how systems are provided with imports.

The runtime systems are updated in the order specified by the transport route in NWDI.

Tracks are provided with transports in the same way. Support Packages cannot be imported into a track until the source track of the Support Packages has itself received them.

NWDI Systems Without Runtime Systems

It is not always the case that all systems in an NWDI track are connected to a J2EE runtime system. If so, the Support Package import starts in the first runtime system in the track, as specified by the system's role.

In the first track of the NWDI landscape, the consolidation system and the production system are each connected to a runtime system. No runtime system is allocated to the development system. The JSPM import of the Support Package then starts in the first runtime system of the track (the consolidation system). However, the NWDI imports for the Support Packages must be performed early in the track – in the development system.

Procedure

To import new software components smoothly in an NWDI-driven system landscape, the following prerequisites must be fulfilled.

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

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

If the NWDI server and the runtime system do not share one and the same transport directory, for example due to security reasons or caused by the physical distance between the NWDI server and the runtime system, you have to make manual copies of files at certain points in the process. You can use operating system utilities (ftp, cp, or copy) to make these file transfers. You must intervene the process at the following stages:

...

●      During an import into a J2EE system that acts as a Dev or Cons system within an NWDI track, JSPM and SAPJup copy all SCAs into the directory $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME). You have to copy these files manually into the corresponding directory on the NWDI server.

●      After the assembly of the modified software components in the NWDI track, the modified SCAs are available in the directory $(TRANSDIR)/EPS/in/assembled on the NWDI server. You have to copy these files manually into the corresponding directory on the J2EE runtime system. See Importing Support Packages into Follow-On Systems.

Required NWDI Version

The server on which the NWDI is running must have at least version SAP NetWeaver 7.0 SP05.

If you have distributed your NWDI across multiple AS 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 SAP NetWeaver 7.0 SP05.

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 SAP NetWeaver 7.0 SP04, 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 SAP NetWeaver 7.0 SP 5, you also need to specify connection data for AS 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 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 Changing the Status of the Import Lock.