Show TOC

Transporting Configuration Objects using CMSLocate this document in the navigation structure

Use

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

The use of the CMS for Integration Directory transports is optional and not necessarily required. It presents an alternative for transports between different Integration Directories, which you can also execute using the file system.

Note

The Usage Type DI is delivered with SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1. If you have installed Usage Type PI and DI both on the same system, you can now upgrade your system from SAP NetWeaver 7.0 to SAP enhancement package 1 for SAP NetWeaver PI 7.1. Please be informed, that this is a limited delivery. Only the Change Management Service (CMS) in connection with PI is allowed to be used. The Design Time Repository (DTR) and the Component Build Service (CBS) are not supported in DI shipped with SAP enhancement package 1 for SAP NetWeaver PI 7.1. CMS is not to be used for any use case other than transports in PI. We recommend that you use the features of the enhanced Change and Transport System for transporting PI objects as well.

Prerequisites

Installation and Technical Configuration

You must first install and configure CMS before you can use it for ESR content transports.

More information: Configuring the Change Management Service

General Concepts

Familiarize yourself with the general concepts of Integration Directory transports using CMS before you plan and execute your transports. The same applies to the concepts of ESR content transports (for more information: PI Transports using the Change Management Service (CMS) , Transport units for CMS Transports (Integration Directory) ).

The general concepts of Integration Directory Transports are also valid for CMS transports (more information: Integration Directory Transports ).

Procedure

1. Configuring an XI Track in the CMS Landscape Configurator

To transport ESR content using CMS, you must configure an XI track (repository type: XI).

Note

You launch the CMS tools from your Web browser.

The track determines the transport route for the configuration objects for each software component version. 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 7.1 (EXCHANGE DIRECTORY 7.1) . This refers to all configuration objects of the Integration Directory.

You enter the server addresses for a maximum of three different 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>/dir/.

More information: Creating an XI Track , Deactivating a Change List Transport (Integration Directory)

2. Transporting Configuration Objects within a Transport Landscape

More information: Transporting Configuration Objects