Transporting Using the Change Management Service

Use

Change Management Service (CMS) is part of SAP NetWeaver usage type Development Infrastructure. This service enables you to configure your transport landscape and manage the transport of objects between different systems.

The use of the CMS for design and configuration objects is optional. It presents an alternative for transports between different ES Repositories and Integration Directories, which you can also execute using the file system (more information: Transporting Objects Using the File System).

Prerequisites

Installation and Technical Configuration

Before you can use CMS together with usage type PI, you must first install CMS and configure it for use with PI.

More information: Configuring the Change Management Service

Configuring an XI Track in the CMS Landscape Configurator

To transport design or configuration objects using CMS, you must configure an XI track (repository type: XI) in the CMS Landscape Configurator.

You launch the CMS tools from your Web browser.

The track determines the transport route for the configuration and design objects for each software component version:

●      For repository transports, you assign the software component versions that you want to use to the track. You can only assign software component versions from the System Landscape Directory (objects from local software component versions cannot be transported using CMS).

●      There are no software component versions in the Integration Directory. Therefore, for directory transports using the CMS, you specify the software component version SAP-INTDIR 3.0 (EXCHANGE DIRECTORY 3.0). This refers to all configuration objects of the Integration Directory.

You enter the server addresses for a maximum of three different ES Repositories or Integration Directories: one for development (DEV, mandatory), one for consolidation (CONS, mandatory), and one for the productive environment (PROD, optional). Enter a URL with the following structure: http://<server>:<port>/rep/ or http://<server>:<port>/dir/.

Transport Scenarios

CMS supports the following scenarios for transporting design and configuration objects:

In the case of transport scenarios with linked tracks, the objects versions in PROD1 must be identical to those in DEV2. You can only link XI tracks from different system landscapes; this means if you link two tracks, A and B, a system from track A may not appear in track B. You can enter the systems for both system landscapes in a System Landscape Directory.

Activities

Once you have set up your tracks by using the Landscape Configurator in CMS, execute the transports by using the Transport Studio and the ES Builder or Integration Builder (see: Overview).