Integrating CMS Transports with the Change and Transport System 

Use

This topic is relevant only if you are using CMS.

Prerequisites

●      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 task.

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

·         Prerequisites for Using CTS combined with NWDI:

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

·         Prerequisites for the target systems of CTS transports:

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

Procedure

Configure the CTS System

The necessary steps are mostly 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.

For more information, see Performing Configuration Steps for Non-ABAP Transports.

       2.      Define transport systems.

                            a.      Create Non-ABAP source systems.

                            b.      Create Non-ABAP target systems. For more information, see Defining and Configuring Non-ABAP Systems

       3.      Define transport layers and routes.

Configure the AS Java System

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

...

       1.      Create a new RFC-destination in the Visual Administrator of the NWDI server. It must be named sap.com/com.sap.tc.di.CTSserver. For more information, see Maintaining RFC Destinations.

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

Performing the Transport - Export

...

       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.      Within the Assembly step the CTS integration takes place. For more information, see Creating a Software Component Archive (Assembly).

       3.      During Assembly the SCA file will be 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 with the button Follow CTS Request).

Performing the Transport - Import

...

       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.