Configuring the Change Management Service

Using the Change Management Service (CMS) with the ES Repository is optional. You can use it to transport ES Repository objects. If you want to use CMS, you must perform some configuration steps first.

The following sections only cover a basic and initial configuration of CMS for use with the ES Repository. More information: Transporting ESR Content .

The CMS component is part of the SAP NetWeaver Development Infrastructure (DI). You find the sources for the DI deployment on SAP Service Marketplace at service.sap.com under SAP Support Portal → Downloads → SAP Software Distribution Centre → Download → Support Packages and Patches → Entry by Application Group → SAP NetWeaver → SAP NetWeaver → SAP NetWeaver 2004s → Entry by Component.

1. Choose Development Infrastructure.
2. Select the following components:
   • DI Change MGMT. Server 7.00
   • DI Component Build Server 7.00
   • DI Design Time Repository 7.00
3. Download the most up-to-date Software Component Archive (SCA) of each component.
4. Deploy the downloaded SCAs with your Software Deployment Manager (SDM).

1. Access the AS Java User Management area on your CMS system and define the following roles and actions:
   • Role CMSDeveloper with actions CMS.Display and CMS.Export
   • Role CMSAdministrator with action CMS.Administrate
2. Choose the AS Java User Administration tab page on your CMS system and define the ES Repository service user ESRCMS<SID> with the role CMSDeveloper.

   This service user is used by the ES Repository to send data to CMS. Therefore, its password must be the same in CMS and ES Repository.

   More information: Defining CMS Communication Users .

3. Define a CMS Administrator user with the role CMSAdministrator.

   It is assumed that the CMS Administrator performs the customizing and the later transports. If you need to distribute administration tasks (for example, approval or transports) to different users, you have to define additional roles and users.

   Note

   All users you created during the CMS setup must change their passwords at initial logon or must have set the flag No password change required.

   Be aware that passwords are case sensitive.

   More information:Roles in the Change Management Service (SAP Help Portal) .

Use the Landscape Configurator and configure:

• the CMS domain
• the CMS server
• the System Landscape Directory (as External Server)

Perform the following steps

1. Configure a CMS domain for the ES Repository in CMS as described inConfiguring a Domain (SAP Help Portal) .
2. Configure the CMS server as follows:
   1. Insert the CMS URL (server name and port of the CMS system)
   2. Create a CMS user (for example LSADMIN). The user allows CMS to connect to the ES Repository systems.
   3. Maintain this user with the same password on the AS Java where your ES Repository is installed and assign it to the following user groups:
      • SAP_XI_CMS_SERV_USER
      • SAP_SLD_ORGANIZER

Within CMS, it is assumed that there is only one central SLD for all Enterprise Services Repositories of the CMS domain. If more than one SLD is used, choose the master SLD for the domain definition.

If you have installed the SLD on a standalone AS Java (and not on the AS Java including ESR), you have to perform the following steps:

1. On the AS Java where your SLD is installed, use the Visual Administrator and open the component sap-com/com.sap.lcr*sld
2. Add the CMS user (for example LSADMIN) to the security role LcrInstance WriterAll or to the group SAP_SLD_ORGANIZER.

To be able to use CMS for repository objects, perform the following steps:

1. Access the ES Repository system properties as described under Additional Manual Configuration .
2. Ensure that the following properties are available and set to

   true

   in your development and consolidation systems; do not change these properties in production systems. The CMS transport option will then be displayed in the Enterprise Services Repository.
   • com.sap.aii.ibrep.core.cms.enableClTransport=true

     Determines that the option of transporting change lists with CMS is provided on the user interface.

   • com.sap.aii.ibrep.core.cms.enableTransportWizard=true

     Determines that the CMS transport is provided by the export wizard.

   Normally, these properties must only be set in systems that are planned to be inserted into the development tracks. In all other systems, the transport should be organized by CMS.

More information on defining a development track in CMS:Creating a Development Track (SAP Help Portal) .

For the ES Repository, specify a track as follows: http://<servername>:<port>/rep/