Start of Content Area

Procedure documentation Configuring the Change Management Service  Locate the document in its SAP Library structure

Use

Using the Change Management Service (CMS) with SAP NetWeaver usage type PI is optional. You can use it to transport Integration Builder objects. If you want to use CMS, you must perform some configuration steps first.

Note

You can configure CMS for either repository objects or directory objects independently from each other.

The following sections only cover a basic and initial configuration of CMS for use with PI.

For more information, see Transporting Using the Change Management Service.

Recommendation

Do not use CMS and the Change and Transport System (CTS) at the same time, except when you migrate from CMS to CTS or vice versa.

More information about CTS: Configuring the Change and Transport System.

Deploying the CMS Component

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 7.0 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 current Software Component Archive (SCA) of each component.

       4.      Deploy the downloaded SCAs with your Software Deployment Manager (SDM).

Defining CMS Communication Users in PI (optional)

Different PI systems probably use different Integration Builder 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 you do not want to modify each system’s service users, you can specify dedicated service users for CMS communication. 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 Integration Builder service users (for example, PIDIRUSER and PIREPUSER) 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.sap.aii.directory.serviceuser.pwd

Maintaining CMS Communication Users in CMS

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

...

...

       1.      Access the User Management area of the J2EE Engine of 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 User Administration tab page of the J2EE Engine of 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 Integration Builder 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.

Note

Make sure that the passwords you define for these two users in CMS match the passwords in your PI system. To do so, log on with both users to the J2EE login screen to make sure that the passwords are correct and that they do not need to be changed.

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

For more information, see Roles in the Change Management Service.

Configuring a CMS Domain in CMS

...

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 PI in CMS as described in Configuring a Domain.

       2.      Configure the CMS server as follows:

...

                            a.      Insert the CMS URL (server name and port of the CMS system)

                            b.      Create a CMS user. The user allows CMS to connect to the PI systems.

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

       SAP_XI_CMS_SERV_USER

       SAP_SLD_ORGANIZER

Note

Either restart the J2EE Engine after you have added the roles to the CMS user or wait until the group assignment has been transferred to the J2EE Engine.

Within CMS, it is assumed that there is only one central SLD for all Integration Builder systems of the CMS domain. If more than one SLD is used by the Integration Builder systems, you should choose the master SLD for the domain definition.

Note

A CMS track can only be defined if all software component versions relevant for the track are available within the SLD of the CMS domain.

If you have installed the SLD on a standalone J2EE Engine (and not on an AS-Java including PI), you have to perform the following steps:

...

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

Activating CMS in the Integration Builder

Set or enhance the following exchange profile parameters to activate CMS for use with the Integration Builder. The CMS transport option will then be displayed in the Integration Repository and in the Integration Directory.

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

Integration 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.*

Note

Do not replace existing values here. Just add the new one.

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.

Note

The transport of change lists with CMS is not supported for the Integration Directory.

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

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

Note

Do not replace existing values here. Just add the new one.

       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.

Defining Development Tracks in CMS

For information on defining a development track for PI in CMS, see Creating an XI Track.

Specify the tracks as follows:

      For the Integration Repository, specify http://<servername>:<port>/rep/

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

 

End of Content Area