Configuring the Change Management Service

Deploying the CMS Component

The CMS component is part of the SAP NetWeaver Development Infrastructure (DI).

To find the sources for the DI deployment, perform the following steps:

1. Go to the SAP Service Marketplace at service.sap.com .

2. Choose SAP Support Portal  Software Downloads  Support Packages and Patches  A-Z Index: N  SAP NetWeaver  SAP EHP1 FOR SAP NETWEAVER 7.3  Entry by Component  Development Infrastructure.

3. Select DI CHANGE MGMT. SERVER 7.31

4. Download the support package related to your PI or AEX installation

5. Deploy the downloaded SCA.

Defining CMS Communication Users in PI respectively AEX (optional)

Different PI respectively AEX systems probably use different repository and directory service users and passwords for communicating with CMS. If you want each of these systems to use the same service user name and password for CMS communication, but do not want to modify each system's service users, you can specify dedicated service users for CMS communication.

1. PI Systems

   To do so, use the following parameters in the exchange profile:

   com.sap.aii.repository.serviceuser.name.cms

   com.sap.aii.repository.serviceuser.pwd.cms

   com.sap.aii.directory.serviceuser.name.cms

   com.sap.aii.directory.serviceuser.pwd.cms

   Do the following to avoid that passwords can be read as plain text in the exchange profile:

   1. Export the exchange profile.

   2. Change type from pwd to string in the file that contains the parameters

      com.sap.aii.repository.serviceuser.pwd.cms

      com.sap.aii.directory.serviceuser.pwd.cms

   3. Import the modified file with option overwrite .

   4. Delete the file that contains the readable passwords.

   If you do not specify these parameters, the names and passwords of the repository and directory service users (for example, PIREPUSER and PIDIRUSER) specified with the following parameters will be used:

   com.sap.aii.repository.serviceuser.name

   com.sap.aii.repository.serviceuser.pwd

   com.sap.aii.directory.serviceuser.name

   com.sa p.aii.directory.serviceuser.pwd

2. AEX Systems

   To do so, use the following parameters in the Java system properties, service XPI service: AII Config Service: :

   • com.sap.aii.repository.serviceuser.name.cms

   • com.sap.aii.repository.serviceuser.pwd.cms

   • com.sap.aii.directory.serviceuser.name.cms

   • com.sap.aii.directory.serviceuser.pwd.cms

   If you do not specify these parameters, the names and passwords of the repository and directory service users (for example, PIREPUSER and PIDIRUser) specified with the folowing parameters will be used:

   • com.sap.aii.repository.serviceuser.name

   • com.sap.aii.repository.serviceuser.pwd

   • com.sap.aii.directory.serviceuser.name

   • com.sap.aii.directory.serviceuser.pwd

Activating CMS

Set or enhance the following exchange profile parameters to activate CMS. The CMS transport option will then be displayed in both the Enterprise Services Repository and the Integration Directory.

Normally, these parameters 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.

Enterprise Services Repository

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

1. Ensure that the following parameters are available and set to true in your development and consolidation systems; do not change these parameters in production systems:

   • 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.

2. Add the following value to com.sap.aii.ib.client.properties:

   • com.sap.aii.ibrep.core.cms.*

Integration Directory

To be able to use CMS for directory objects; perform the following steps:

1. Ensure that the following parameter is available and set to true in your development system:

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

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

2. Add the following value to com.sap.aii.ib.client.properties:

   • com.sap.aii.ibdir.core.cms.*

3. Ensure that the following parameter is available and set to true in your consolidation system:

   • com.sap.aii.ibdir.core.cms.enableClTransport=true

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

Do not change any of these parameters in production systems.

Maintaining CMS Communication Users in CMS

To maintain the CMS communication user in CMS, perform the following steps:

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 dedicated service users for CMS communication you specified in the previous section as CMS users with role CMSDeveloper.

   If you have not specified any dedicated service users for CMS communication, use the repository and directory service users (for example, PIREPUSER and PIDIRUSER).

   These service users are used by PI to send data to CMS. Therefore, their passwords must be the same in CMS and PI.

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.

More information: Roles in the Change Management Service .

Configuring a CMS Domain in CMS

Use the Landscape Configurator to configure the following:

• CMS domain

• CMS server

• System Landscape Directory (as an External Server )

Perform the following steps

1. Configure a CMS domain for PI respectively AEX in CMS as described in Configuring a Domain .

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. The user allows CMS to connect to the PI respectively AEX systems.

      This user (for example LSADMIN) must be maintained as service user in all PI respectively AEX systems (including SLD) with the same password. For PI it requires the following ABAP roles:

      • 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 and Integration Directories 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 an AS Java including PI respectively AEX), you have to perform the following steps:

1. On the AS Java where your SLD is installed, use the SAP NetWeaver Administrator and choose Configuration Management    Security    Authentication.

2. Add the CMS user (for example LSADMIN) to the security role LcrInstance WriterAll or to the group SAP_SLD_ORGANIZER .

Defining Development Tracks in CMS

More information on defining a development track for PI in CMS: Creating an XI Track .

Specify the tracks as follows:

• For the Enterprise Services Repository, specify http://<servername>:<port>/rep/

• For the Integration Directory, specify http://<servername>:<port>/dir/