Integrating CMS Transports with the Change and Transport System

• Prerequisites for a leading Change and Transport System (CTS) system:

  • Application Server ABAP (AS ABAP) and Application Server Java (AS Java) of SAP NetWeaver 7.0 SPS 14 or higher. We recommend a dual stack installation - you can use the SAP Solution Manager for that.

  • The CTS leading system is configured as the TMS domain controller where the non-ABAP systems with their transport route configuration are maintained centrally.

• Prerequisites for the integration of NWDI with CTS:

  • NWDI Server on SAP NetWeaver 7.0 SPS 14 or higher.

• Prerequisites for the target systems of CTS transport:

  • Any SAP NetWeaver (AS Java) release can be addressed.

The necessary steps are performed in the Transport Management System (TMS).

To configure the CTS system, proceed as follows:

1. Configure the enhanced CTS components in the AS ABAP transport domain controller to be able to transport non-ABAP objects.
2. Define transport systems.
   1. Create non-ABAP source systems.
   2. Create non-ABAP target systems. For more information, see Defining and Configuring Non-ABAP Systems in the Transporting Non-ABAP Objects in Change and Transport System section of the Change and Transport System documentation.
3. Define transport layers and routes.

For the integration of CTS in NWDI, the following configuration has to be done:

1. Create a new RFC destination for the NWDI server. We recommend that you name it sap.com/com.sap.tc.di.CTSserver. You can also choose a different name. For more information about creating the RFC destination, see Configuring Export Destinations in the Transporting Non-ABAP Objects in Change and Transport System section of the Change and Transport System documentation.
2. Configure the CMS track. You must mark the track as Connected to CTS and specify the exact CTS upload system to connect the track to. The TMS non-ABAP source system for that transport route is the SID of the runtime system that is connected as NWDI Development System.

   To do that, open the CMS Web UI and under the Landscape Configurator, choose Track Data. Enable the Connected to CTS checkbox and configure the CTS system to connect to. For more information, see Creating a Development Track.

1. Go to the NWDI Transport Studio and transport the changes through the NWDI track. For more information, see Transports with the NWDI: Transport Studio.
2. The CTS integration takes place within the Assembly step. For more information, see Creating a Software Component Archive (Assembly).
3. During assembly, the SCA file is attached to the TMS transport request.
4. If no automatic release is configured for that TMS source system, release the transport request in the Transport Organizer Web UI (which is opened using the Follow CTS Request button).

1. The transport request is waiting for import in the import queue of the target system.
2. The import is done in TMS. For more information, see Importing Transport Requests with Non-ABAP Objects in the Transporting Non-ABAP Objects in Change and Transport System section of the Change and Transport System documentation.