SAP MII : How to configure

CM (Change Management)
Services with MII

CM Services Integration with MII via

CTS+
 SAP MII: How-To-Guide for configuring CM services with MII

Applicable Release: SAP MII 15.3 SP01

Version 1.0
Date: 22-11-2019

ii
 SAP MII: How-To-Guide for configuring CM services with MII

© Copyright 2019 SAP AG. All rights reserved. These materials are subject to change without notice. These
No part of this publication may be reproduced or transmitted in materials are provided by SAP AG and its affiliated companies
any form or for any purpose without the express permission of ("SAP Group") for informational purposes only, without
SAP AG. The information contained herein may be changed representation or warranty of any kind, and SAP Group shall not
without prior notice. be liable for errors or omissions with respect to the materials.
Some software products marketed by SAP AG and its The only warranties for SAP Group products and services are
distributors contain proprietary software components of other those that are set forth in the express warranty statements
software vendors. accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
Microsoft, Windows, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation. These materials are provided “as is” without a warranty of any
kind, either express or implied, including but not limited to, the
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
implied warranties of merchantability, fitness for a particular
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
purpose, or non-infringement.
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, SAP shall not be liable for damages of any kind including
POWER5, OpenPower and PowerPC are trademarks or without limitation direct, special, indirect, or consequential
registered trademarks of IBM Corporation. damages that may result from the use of these materials.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are SAP does not warrant the accuracy or completeness of the
either trademarks or registered trademarks of Adobe Systems information, text, graphics, links or other items contained within
Incorporated in the United States and/or other countries. these materials. SAP has no control over the information that
you may access through the use of hot links contained in these
Oracle is a registered trademark of Oracle Corporation.
materials and does not endorse your use of third party web pages
UNIX, X/Open, OSF/1, and Motif are registered trademarks of
nor provide any warranty whatsoever relating to third party web
the Open Group.
pages.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
SAP ME “How-to” Guides are intended to simplify the product
VideoFrame, and MultiWin are trademarks or registered
implementation. While specific product features and procedures
trademarks of Citrix Systems, Inc.
typically are explained in a practical business context, it is not
HTML, XML, XHTML and W3C are trademarks or registered implied that those features and procedures are the only approach
trademarks of W3C®, World Wide Web Consortium, in solving a specific business problem using SAP ME. Should
Massachusetts Institute of Technology. you wish to receive additional information, clarification or
Java is a registered trademark of Sun Microsystems, Inc. support, please refer to SAP Consulting.
JavaScript is a registered trademark of Sun Microsystems, Inc.,
used under license for technology invented and implemented by
Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and in several
other countries all over the world. All other product and service
names mentioned are the trademarks of their respective
companies. Data contained in this document serves
informational purposes only. National product specifications
may vary.

i
 SAP MII: How-To-Guide for configuring CM services with MII

Document History
Document Version Description Author
1.0 Initial version Shruthi
Vishwanath

ii
 SAP MII: How-To-Guide for configuring CM services with MII

Table of Contents
1 Overview ......................................................................................................................................... 1
2. Initial Setup and Configuration of CM Services ……………………………………………………………………………..2
2.1 Configuring System Landscape Directory (SLD)……………………………………………. .2
2.2 Configuring NWDI with CM Services ………………………………………………………..5
2.3 Mapping Roles in UME ……………………………………………………………………….7
2.4 Connections from NWDI to CTS+ server and vice versa …………………………………… 7
2.5 Configuring the CM Services Server ………………………………………………………… 8
2.5.1 Creating a User for RFC Destinations from CTS+ System to CM Services ……….8
2.5.2 Creating an RFC Destination from CM Services to CTS+ ………………………...9
3. CTS+ server configurations ……………………………………………………………………………12
3.1 Creating a developer user in CTS+ …………………………………………………………..12
3.2 Configuring RFC Destinations and Logical ports ………………………………………….. 13
3.2.1 Configuring RFC Destinations…………………………………………………….14
3.2.2 Configuring Logical Ports…………………………………………………………17
4. Setting up transport and development configuration landscape………………………………………..20
5. Creating MII source and target systems in CTS+ ……………………………………………………...21
5.1 Creating MII source system with Development Configuration ……………………………...21
5.1.1 Adapting TMS parameters…………………………………………………………24
5.1.2 Configuring the Development Configuration……………………………………...25
5.1.3 Getting the required software component archives ……………………………….31
5.2 Creating MII target system …………………………………………………………………..35
6. Creating Transport Routes ……………………………………………………………………………..37
7. Development and Export process in MII……………………………………………………………….39
8. Troubleshooting & Tips ………………………………………………………………………………..45

iii
 SAP MII: How-To-Guide for configuring CM services with MII

1. Overview

CM (Change Management) services allows transport of sources and/or deployables from source
to target MII systems. Prior to CM services, i.e. with CMS, the user did not have the flexibility of
choosing granular transport options and had to transport the entire SCA irrespective of the
magnitude of the changes in the source system.

Landscape options:

The transport options with granularity are as below :

1.Source Export : Granularity:
a. Software Components
b. Activities
2.Deployable Export : Granularity:
a. Software Components
b. Development Components
c. Activities

Depending on the transport scenario, the configuration of your system landscape looks different.
The main difference is that for source transports a development configuration is needed for your
source (development) system and each target system in your transport route. For a pure
transport of deployables, a development configuration is needed just for the
source/development system.

Mainly two systems are relevant for configuring the CM Services. You need a system, where
NWDI (DTR and CBS) is installed and one that can be used to host the transport landscape
(CTS system).An SLD is required as well to register the development configurations and to
create e.g. Products and Software components.

The figure below shows the different components involved in the transport from MII source to
target systems.

1
 SAP MII: How-To-Guide for configuring CM services with MII

MII source
system

MII target
system

The process for transporting deployables based on activities is shown in the following
figure.Similarly, source exports are possible where the release would be via the Export Web UI.

2. Initial Setup and Configuration of CM Services

2.1 Configuring System Landscape Directory (SLD)

1. On the NWDI system, in the SAP NetWeaver Administrator (http://<host>:<port>/nwa),choose

Configuration → Scenarios → Configuration Wizard

2
 SAP MII: How-To-Guide for configuring CM services with MII

2. Choose Functional Unit Configuration UI

3. Select System Landscape Directory (SLD) and choose Enable Automatically.

4. When prompted for passwords, enter the J2EE Administrator password, and define and
confirm a Master Password according to your policy. To continue executing the
templates, choose Next.

3
 SAP MII: How-To-Guide for configuring CM services with MII

5. Enter SLD server details (NWDI server) depending on if it’s a local SLD or an existing
remote SLD.

6. A success message will be seen once the setup is executed successfully.

4
 SAP MII: How-To-Guide for configuring CM services with MII

2.2 Configuring NWDI with CM Services

1. Select NWDI using CM Services -recommended and click on Enable automatically. We

recommend that you use this option for configuring the NWDI because it automatically
selects the ‘Java Foundation’ as well.

2. When prompted for passwords, enter the Administrator Password, and the Master
Password that you have used before. To continue executing the templates, choose Next.

5
 SAP MII: How-To-Guide for configuring CM services with MII

3. In the next step, the users NWDI_ADM, NWDI_DEV and NWDI_CMSADM are created.
Enter a Master Password for these users CAUTION Remember the master password –
you will need it later on.

4. After the Configuration Wizard has completed the configuration of the NWDI using CM
Services, you can exit the Configuration Wizard.

6
 SAP MII: How-To-Guide for configuring CM services with MII

2.3 Mapping Roles in UME

Go to UME of your NWDI System. Use the URLhttp://<server>:<port>/useradmin.

Search for the group NWDI.Administrators and select it. Go to the tab Assigned Roles,
choose Modify and search for the role SAP_DI_ADMINISTRATOR and add it to the
group. Similarly, the role SAP_DI_DEVELOPER should assigned to the group
NWDI.Developers.

2.4 Connections from NWDI to CTS+ server and vice versa

In order to connect NWDI (where CM services run) and the CTS+ server, the below
connections need to be established.

1. One connection points from the CTS system to the NWDI system. It is needed to call the
Deploy Web Service and the DI Config Services. These services run on the NWDI. They
are needed to create development configurations and if you would like to import a
request into a system for which a development configuration has been created. The
configuration for this connection is done on the CTS system in the transactions
LPCONFIG and SM59. For this destination, you have to create a user on the NWDI
which is then entered as connecting user in SM59 (e.g.CTS_RFC).

2. The second connection points from the NWDI to the CTS system, which means from
Java to ABAP. This connection is created as an RFC destination (JCoConnection) on
the NWDI server and is required to be able to retrieve e.g. a transport request from CTS
when exporting an activity via NWDS or using the DI Export Service UI. For this
connection, the user(s) developing with NWDI (e.g. NWDI_DEV) have to be created on
your CTS system.

7
 SAP MII: How-To-Guide for configuring CM services with MII

¤ Note : Each user who does changes to Java sources and would like to attach these
changes to a transport request has to exist with the same ID both on the CTS system
and on NWDI

3. The third connection points from the AS ABAP of your CTS system to the AS Java of
your CTS system. It is used when deployables are imported e.g. into your test or
productive system. It is not mandatory. Nevertheless, we recommend configuring this
connection as well –it reduces the number of systems that have to be available when
importing a transport request which contains deployables. This destination cannot be
used when importing sources.

2.5 Configuring the CM Services Server

2.5.1 Creating a User for RFC Destinations from CTS+ System to CM Services

This section describes how to create a user on the CM Services server that is needed for
communication between the CTS system and the CM Services.

1. Go to the user administration of your NWDI server. Choose Create User.

2. On the following screen, enter a Logon ID, a real password (you won’t have to change it
later on) and the Last Name. Choose Technical User as Security Policy. Click Save.

8
 SAP MII: How-To-Guide for configuring CM services with MII

3. On the Assigned Roles tab page, search for the roles SAP_CTS_DEPLOY and
SAP_CTS_DI_CONFIGURATOR and assign them to the user CTS_RFC.

2.5.2 Creating an RFC Destination from CM Services to CTS+

An RFC destination is needed on the CMServices server (the NWDI) to be able to retrieve
transport requests from CTS+.

1. In the SAP NetWeaver Administrator of your CM Services system (NWDI), choose

Configuration -> Destinations.

9
 SAP MII: How-To-Guide for configuring CM services with MII

2.Choose create. Now choose Local Java System <SID>as Hosting System. Enter
sap.com/com.sap.tc.di.CTSserver in the Destination Name field and choose Destination Type
RFC. Click Next.

3. Enter the required data as shown in the following figure and click Next:
a. Decide whether you use Load Balancing for your CTS system (in our example, we
don’t do so).
b. Target Host: server name of the CTS system
c. System Number: system number of the CTS system
d. System ID: SID of the CTS system
Click Next.

10
 SAP MII: How-To-Guide for configuring CM services with MII

4. In the Authentication section, select Current User (AssertionTicket) as Authentication for the
connection to the CTS communication system.
Client: Client in which the Transport Organizer Web UI is running (same value as used
when creating the non-ABAP system on the CTS system for parameter
NON_ABAP_WBO_CLIENT). Choose Finish to complete the Destination Wizard.
Click on Ping Destination to check for successful connection.

11
 SAP MII: How-To-Guide for configuring CM services with MII

3. CTS+ server configurations

3.1 Creating a developer user in CTS+

1. Log on to your CTS system and open transaction SU01.

2. Enter NWDI_DEV as User and click on create.

3. Entire required data in Address tab. Click on Logon tab and enter a new password.

4. Click on Roles tab and assign the role SAP_CTS_PLUS. Save the user.

12
 SAP MII: How-To-Guide for configuring CM services with MII

5. Repeat the previous steps for every user who is developing in Java and has to attach
changes to a transport request (be it from within the developer studio or the export service). The
users are required on the CTS system e.g. to get a transport request when exporting. You can
use the user IDs of your developers. Make sure that you use IDs which allow to be used in SSO
mode. Remember that ABAP supports user IDs with a length of up to 12 characters.
NWDI_DEV is used as an example in this guide.

Note: If the users already exist on the CTS system, make sure that they have sufficient
permissions –assign the role SAP_CTS_PLUS to them.

3.2 Configuring RFC Destinations and Logical ports

The figure below shows how the logical ports and destinations are connected. The logical ports
(CTSCONFIG and CTSDEPLOY_DI) use the same RFC destination (CTSCONFIG).
Furthermore the user CTS_RFC which was created on the CM Services server is used for the
RFC connection from CTS to the CM Services system.

Note:

The Deploy Web Service (CTSDEPLOY) e.g. for your portal transports can be hosted on a
different server. For the portal, the Deploy Web Service usually runs on the AS Java of your
SAP Solution Manager. For CM Services the CTS Deploy Web Service on the CM Services
server has to be used in case you use the source transports and for the development system for
the transport of sources and deployables (see Introduction, systems, where parameter
DI_System is set to true). For the test and productive systems, you need the RFC connection
CTSDEPLOY as well. In this case, the RFC connection CTSDEPLOY that might already be in
use for transporting portal content can be used as well. If you are not using CTS for any other
use case on your SAP Solution Manager up to now, take a look at step 5 of this chapter to learn
how to configure CTSDEPLOY.

13
 SAP MII: How-To-Guide for configuring CM services with MII

3.2.1 Configuring RFC Destinations

An RFC destination is needed for the communication between the CTS system and the CM
Services system: CTSCONFIG. The required user CTS_RFC for this RFC connection with
special permission on the CM Services system has already been created in step Creating User
for RFC Destinations from CTS System to CM Services.

Proceed as follows to create the RFC destination:

1. Log on to the client of your CTS system that you are using for transports (=where the
Transport Organizer Web UI runs). Open transaction SM59 and open the HTTP Connections to
External Server section.

14
 SAP MII: How-To-Guide for configuring CM services with MII

2. Enter CTSCONFIG as RFC Destination, a Description, the Target Host (your NWDI/CM
Services server), and as Service No the port of your server where the CM Services and the
Deploy Web Service run. Make sure that the Connection Type is G. Select No Timeout in the
special options tab.

15
 SAP MII: How-To-Guide for configuring CM services with MII

3. Choose Connection Test to check if it is successful with 200 value.

16
 SAP MII: How-To-Guide for configuring CM services with MII

4. To transport deployables you have to configure an RFC destination pointing from the
AS ABAP of your CTS system to the AS Java of your CTS system as well. This
destination should be called CTSDEPLOY.
Enter CTSDEPLOY as RFC Destination, a Description, the Target Host(AS Java of your
CTS system), and as Service No the port of the AS Java that is used for the CTS
system. Make sure that the Connection Type is G.

5. Select Basic Authentication in the Logon & Security tab. Enter a user and the password. The
user should have the role SAP_CTS_DEPLOY assigned on the AS Java.
6. Go to the Special Options tab page and select No Timeout. Test Connection.

3.2.2 Configuring Logical Ports

Two logical ports are needed for the communication between the CTS system and the CM
Services system: CTSCONFIG and CTSDEPLOY_DI. One logical port is required for the
communication between the AS Java and the AS ABAP of your CTS system:
CTSDEPLOY.CTSDEPLOY_DI is needed to reach the Deploy Web Service on the NWDI
system to manage the import of sources(import into NWDI and following automatic deployment
to the development runtime system).The Deploy Web Service on the AS Java of your CTS
system cannot be used in this case One Logical Port CTSDEPLOY is needed for the
communication between the AS ABAP and the AS Java of your CTS system. This port is

17
 SAP MII: How-To-Guide for configuring CM services with MII

needed if you want to use the transport of deployables. If you decide to use the transport of
sources, this port is not needed. Nevertheless, SAP delivers this port by SAP by default and you
should not delete it as you might need it for other transports on your SAP Solution Manager -
e.g. portal content. If you use deployable transport, you do not need the port CTSDEPLOY_DI.
It is only needed if you plan to execute imports into your development system (e.g. because you
manually add a transport request to the queue)

1. Log on to your CTS system in client 000 and call transaction LPCONFIG. Confirm the pop-up
message that the transaction is obsolete. Click Continue. For this purpose, you have to use
transaction LPCONFIG. Enter CO_TDIDICONFIGURATION_SERVICE as Proxy Class and
CTSCONFIG as Logical Port. Make sure that the option Default Port is not set.

Click on Display. Check that the logical port exists, that it is active and that the parameters are
set as shown in the following figure

2. The logical port CTSDEPLOY should be configured with the values shown in the following
figure. It should be the Default Port and it has to be active.

18
 SAP MII: How-To-Guide for configuring CM services with MII

3. Enter the Proxy Class CO_TFLDEPLOY_PROXY_VI_DOCUMENT and the Logical Port

CTSDEPLOY_DI. Click on Create. Enter a Description. Enter CTSCONFIG as HTTP
Destination and /DeployProxy/default?style=document as Path Suffix.

19
 SAP MII: How-To-Guide for configuring CM services with MII

Note : It is correct and it is the intended setup that this logical port also uses the http destination
CTSCONFIG since it also requires a connection to the CM Services system.

4. Save your logical port. You will be asked for a transport request. You can either create a new
one or use an existing one.

5. Activate the logical port.

4. Setting up transport and development configuration landscape

When creating a development configuration for a system, DTR workspaces and CBS buildspace
are created automatically. But initially they are empty! Therefore you have to fill these
buildspaces (and workspaces) with the required libraries (compared to the CMS Check-In and
import to development). In CM Services this is done with the help of the Synchronize Service.

In our example, we will use the deployable transport. For this scenario, the following
configurations are required:

20
 SAP MII: How-To-Guide for configuring CM services with MII

Systems

SRC (S08 in this case): non-ABAP source and target system with development
configuration

TGT (MT7 in this case): non-ABAP target system

Transport Routes:

SRC → TGT : Consolidation and Delivery Route

5. Creating MII source and target systems in CTS+

5.1 Creating MII source system with Development Configuration

1. On your CTS system (domain controller), call transaction STMS and click on System
Overview.

21
 SAP MII: How-To-Guide for configuring CM services with MII

2. Choose SAP System → Create → Non-ABAP-System

3. Enter the SID in the field System. In our example, we enter S08. Enter a Description as well.
Enter your CTS system as Communication System: (the system where you configured the
logical ports and the RFC Destinations –CTSCONFIG etc). Select Create Development
Configuration.

4. If this is the first system with a development configuration that you create, now, a pop-up will
be shown where you have to enter the SLD URL. Enter the URL to the SLD that you have
configured during the NWDI setup. Click on continue.

22
 SAP MII: How-To-Guide for configuring CM services with MII

5. Choose Activate Transport Organizer and make sure that the correct client is set. Choose
Activate Deployment Service and choose SDM or DC(depending on the release of your runtime
system).Enter the Target Host and the System No of your development runtime system. Click
save.

Note : For all runtime systems which are on SAP NetWeaver 7.1 or later, use DC(=Deploy
Controller) as Method. For lower releases SDM is used for deployments.

6. For deployments to the runtime system, a user with appropriate permissions is needed. In the
dialog box <SID>: Set User and Password for Deployment SDM/DC enter a user who has
permissions to execute deployments on the development runtime system.

7. If this is the first DI system that you create, you will now be asked to enter a user and
password for the SLD. Enter the master password that you defined when setting up the NWDI.
Click continue.

23
 SAP MII: How-To-Guide for configuring CM services with MII

Note: If you set up your NWDI to be used with another (already existing) SLD, you have to enter
a user and password for this SLD.

If you do not use CM Services on the system where DTR / CBS run, you have to create the
user that you like to use in here on the CM Services system as well.

8. After you saved the S08 system in TMS, a browser window showing the Development
Infrastructure. Development Configuration Management opens automatically. This UI runs on
the CM Services server. If you do not have single sign-on in place, you have to log on at first.
Use the user NWDI_ADM with the master password that you set when configuring the NWDI
(see chapter Configuring NWDI with CM Services). We will continue with the configuration in
this UI after adapting some parameters for the system S08 in TMS.

5.1.1 Adapting TMS parameters

1. Double-click on the system S08 in System Overview. In Transport tool tab, Change the
parameter DEPLOY_WEB_SERVICE to CTSDEPLOY_DI.

2. You can define that the AS Java gets the files from the AS ABAP (the Transport directory)
when executing an import:

24
 SAP MII: How-To-Guide for configuring CM services with MII

• You can use a mount directory or a shared directory –the parameter

DEPLOY_DATA_SHARE which is used by default.
• You can alternatively explicitly set a SAP Java Connector connection (JCo connection),
with the parameter CTS_FILE_PROVIDER_URI. For the JCo connection you need to
set the File Provider User and Password. In the TMS Configuration of your system
choose Goto File Provider User/Password. The users that are entered in the
destinations CTSDEPLOY and CTSCONFIG in SM59 have to have the permission
Destination_Service_Write_Permission on the CM Services system in addition to the
role SAP_CTS_DEPLOY. We recommend that you create a separate role containing this
action and assign this role to the user that is used when the CTS system connects to the
CM Services system. For more information, refer to SAP Note 1492665 and in the SAP
Library at
http://help.sap.com/saphelp_nw73/helpdata/en/81/5bb741b48d4c6ea8c94b534144ba3a/
content.htm.

Note : You have to delete the DEPLOY_DATA_SHARE parameter to be able to use the
CTS_FILE_PROVIDER_URI parameter. Otherwise the system tries to access the Deploy Data
share. For details on the CTS_FILE_PROVIDER_URI parameter, the possible values and
permissions required refer to SAP Note 1492665.

5.1.2 Configuring the Development Configuration

1. Open Development configuration from the source system that was created above.

25
 SAP MII: How-To-Guide for configuring CM services with MII

2. What you can see on the System Landscape Directory tab should be ok since the information
was passed on from the CTS system. Go to the Local Settings tab and click on Edit to enter all
the fields.

3. Set the options Repository Location and Build Tool Location. This will automatically add the
respective paths. Define the Transport Settings. In our example, we are going to use the
Deployable Export with the options to transport Software Components and Activities. Make sure
that the Export Destination shown in here is the one that you created earlier.

26
 SAP MII: How-To-Guide for configuring CM services with MII

Note : If you have to connect one NWDI to more than one CTS system, you can also define
more than one destination. We recommend that you add the SID of the CTS system to the
name so that you know what the different destinations are made for (e.g.
sap.com/com.sap.tc.di.CTSserver_CTS).

Execute the next step “Software Component Definition” before saving these settings. The DTR
and CBS URLs will be deleted if no software components are added for the development
configuration.

4. Click on the Software Component Definition. You can now add the SCs that you would like to
develop in this development configuration. To do so, click on Add SC. All available software
components are read from SLD and are provided in a list. Retrieving the list from SLD for the
first time might take a while.

5. On the dialog box, you can choose from the existing SCs or create a new one. Refer to the
chapter Creating a new SC for details if you would like to create a new SC. Filter the list
according to the SCs you want to add to the development configuration, select them, and
choose Add, and then Close.

6. The wizard should be executed with relevant entries like SLD url and admin credentials.

27
SAP MII: How-To-Guide for configuring CM services with MII

7. Enter an SC name and enter vendor and release number.

8. On refreshing the list of SC’s, you should be able to view the newly created SC.

28
SAP MII: How-To-Guide for configuring CM services with MII

9. A success message should be displayed after the wizard executes successfully.

10. Add the dependent Software Components. For this, go to SLD

(http://<host>:port/sld). Click on Software Components.

11. Search for the newly created SC and filter Dependencies by Build Time (Context
field).Click on Define Prerequisite Software Component Versions and add MIIBUILDT
15.3.

29
SAP MII: How-To-Guide for configuring CM services with MII

12. Save the configuration.

30
SAP MII: How-To-Guide for configuring CM services with MII

5.1.3 Getting the required software component archives

To synchronize your NWDI with the runtime system concerning the SCAs required / to
be developed, proceed as follows:

1. Make sure that all required SCAs that you need are available –those that are
delivered by SAP and on which your development depends and those that you would
like to develop. Copy them to a folder on your NWDI.

Note: You can get the SCAs delivered by SAP from the Installation / upgrade folder of
your runtime system.

2.Start the Synchronize Service. You can do so using the related links in the
development configuration service. Go to Related Links → Synchronize Service.

3. You will see all the SC’s as below with versions listed.

31
 SAP MII: How-To-Guide for configuring CM services with MII

4. In order to synchronize this to the SCA’s that were downloaded from Service Marketplace,
place all the relevant SCAs with exact matching versions in the NWDI location. Enter the inbox
path as D:/usr/sap/trans/EPS/in. In this case we will place SAPBUILDT and MIIBUILDT in this
location.

The figure below shows the remote SLD (NWDI) server where the SCAs from SMP are placed.

32
 SAP MII: How-To-Guide for configuring CM services with MII

5. Once the versions match with the ones placed in NWDI as above, the option of import
archives will be visible for these SCA’s. For SCAs where there is no SCA available in the inbox,
the recommended action will be to Skip the import for this SC. You can change the action if
needed. Click Next.

33
 SAP MII: How-To-Guide for configuring CM services with MII

6. Click on Synchronize.

The Synchronize Service allows you to compare software component versions on the runtime
system with what is imported into the NWDI. The results of the synchronization are shown in the
log below the Summary table.

7. If you now restart the Synchronize Service, you should see that the version in NWDI and in
the runtime system is now the same.

34
 SAP MII: How-To-Guide for configuring CM services with MII

5.2 Creating MII target system

1. In the System Overview in transaction STMS choose SAP System →Create →Non-ABAP
System.

2. Fill in the following fields:

• System: SID of your test system

• Description
• Select Activate deployment Service and choose the appropriate Method. Enter the
Target Host and the System No. Click on Save.

To transport deployables, the checkbox Create Development Configuration need not be

checked. For deployables, a DTR, CBS setup is not required in the target system.

Note : If you are setting up a landscape for source transport, choose Create Development
Configuration as well. In this case, the DI Configuration Service will be shown automatically
after you finished the configuration for this system. Configure the development configuration
in the same way as you did for your development system. You can use the option Copy
Definition From to configure the development configuration. Choose your development
system as source.

3. Enter a user and password with deploy permissions in target system.

Note: For the parameter DEPLOY_WEB_SERVICE, the value CTSDEPLOY is automatically

entered for each system. This is fine if you transport deployables. If you want to use the
source transport, you have to change this to CTSDEPLOY_DI.

35
 SAP MII: How-To-Guide for configuring CM services with MII

4. To check that the system is configured correctly, click on the button Transp.Tool. In the
result, all the checks should show a green check mark–especially in the sections Deploy
Web Service and Deploy Tool

5. Repeat the previous steps for allother target system that you want to use for the
landscape.You are not limited to a three-systemlandscape. All the options for designing
landscapes that are offered by TMS (more than one target system at a time, groups etc.) are
available for non-ABAP landscapes as well.

36
 SAP MII: How-To-Guide for configuring CM services with MII

6. Creating Transport Routes

To enable transport from source to target system, a transport route should be created. This
configuration is also done in transaction STMS. For the configuration of transport routes, it
doesn’t matter whether you transport sources or deployables.

1. Go to transaction STMS and choose Transport Routes.

2. Click on the change mode button. The editor switches to edit mode and the transport
route can now be created.

37
 SAP MII: How-To-Guide for configuring CM services with MII

3. Choose the source and target system from the topmost row and drag it to the lower
area. Now click on the Add Transport Route button and draw a line from source to
target system.

4. The below popup opens where you can enter the source and target systems. Enter
ZDIT in the Transport Layer field. Click ok.

5. Save the transport route.

38
 SAP MII: How-To-Guide for configuring CM services with MII

7. Development and Export process in MII

1. Login to MII source system. Click on NWDI Configuration in the portal.

2. Click on Edit and enter the NWDI admin credentials (NWDI_ADM). Click on Browse
button. Choose S08 track, select Basic Authentication and save.

Note: Basic authentication would mean that user has to enter credentials each time to
login to source control in workbench. On choosing SSO as the authentication mode,
user will be prompted to login to source control without having to pass credentials.

39
 SAP MII: How-To-Guide for configuring CM services with MII

3. Open workbench. On clicking Source Control → Logon, below pop up requires

credentials to login to NWDI. Enter the admin user and password. Click OK.

4. Click on root and create New Shared Project. The track (content SC :MIICMServices)
is auto populated. Enter required details and click OK.

Create a Bar Chart and a Tag query in this shared project. During creation, a pop up
shows up to add to an activity.

40
SAP MII: How-To-Guide for configuring CM services with MII

5. Click on Show Open activities in Source Control. Choose Activate check box
and click on Checkin button. The activity gets queued up for activation. Click on
Show Activation Requests. The below pop up shows the Request ID with status.
Close the pop up.

41
SAP MII: How-To-Guide for configuring CM services with MII

6. Now open NWDS and click on the created track S08 in Development
infrastructure. Open the Transport view and expand the activities. You will now
see an activity waiting in queue to be released.

7. Right click on the activity and click on Release. In the popup, click on Release
rebuilt deployable DCs. You can also see the target system details in the tab
below.

42
SAP MII: How-To-Guide for configuring CM services with MII

8. Once this is complete, you can see that the activity is in Released state in the
transport view.

8. Now login to TMS in CTS+ and click on Import queue WebUI.

43
SAP MII: How-To-Guide for configuring CM services with MII

9. You can see that the activity is ready to be imported to the target system.
Select the activity and click on the import button. Once this completes, you can
view the changes in the target system (MT7) by logging into workbench.

44
 SAP MII: How-To-Guide for configuring CM services with MII

8. Troubleshooting & Tips

1. Note that the NWDI server has to be excluded from proxy list during setup in order to be able
to save the configuration in MII.

2. For below error, you will have to update configuration in CTS+ in case you have modified
some configuration like changed a password etc

45
 SAP MII: How-To-Guide for configuring CM services with MII

3. Ensure that cimom url is explicitly set to the IP and port of the NWDI (SLD) server.

46
 SAP MII: How-To-Guide for configuring CM services with MII

4. Refer to below notes for more details

Central SAP Note for CM Services: 1361909

Central SAP Note for CTS+: 1003674
Note 1775838 - CMS / CM Services: What to use in which scenario?

5. For Single Sign On (SSO) to work, you need to setup trust between the source MII system
and the NWDI. To do this we add MT8 as a trusted system in NWDI.
a. First, download the latest keystore certificate from source MII system. Go to NWA →
Certificates & Keys → Select TicketKeyStore . In the View Entries tab, select
SAPLogonTicketKeypair-cert.crt. Export this and download from pop up.

47
SAP MII: How-To-Guide for configuring CM services with MII

b. Go to <host>:<port>/sso of the NWDI system and add a New Trusted System here.
Enter details of the source MII system and upload the above certificate.

6. If you have set SSO in MII NWDI Configurations and you try to logon to MII portal and
NWDI with 2 different users, you will run into below error.

48
SAP MII: How-To-Guide for configuring CM services with MII

This can be avoided by logging in to MII with a user which is available on NWDI as well
(ex: NWDI_ADM). This is because, when user logs in to MII with SSO enabled for CM
services, the system looks for this same user when accessing source control entities.

49