Transporting ESR Content using the Change Management Server
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 ESR content transports is optional and not necessarily required. It presents an alternative for transports between different ES Repositories, which you can also execute using the file system.
Installation and Technical Configuration
You must first install and configure CMS before you can use it for ESR content transports.
General Concepts
Familiarize yourself with the general concepts of ESR content transports using CMS before you plan and execute your transports. The general concepts for ESR content transports also apply to CMS transports.
More information: ESR Content Transports , CMS Transports (ES Repository) , Transport untis for CMS Transports (ES Repository)
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). For more information, see Creating an XI Track and XI Tracks
You launch the CMS tools from your Web browser.
The track determines the transport route for ESR content for each software component version. You can only assign software component versions from the System Landscape Directory (objects from local software component versions cannot be transported using CMS).
You enter the server addresses for a maximum of three different ES Repositories: 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/.
More information: Deactivating a Change List Transport (ES Repository)
2. Executing ESR Content Transports within a Transport Landscape
More information: Transporting Design Objects