Integrating NWDI Transports with the Change and Transport System 

Prerequisites

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

○       Application Server ABAP (AS ABAP) of SAP NetWeaver 7.0 SPS 12 or higher.

○       The CTS leading system is configured as an SAP system in which the transport route configuration is maintained centrally for all systems in the same transport domain, that is, as a Domain Controller.

○       We recommend using a dual stack installation – you can use the SAP Solution Manager for that task.

●      Prerequisites for the target systems of CTS transports:

○       AS ABAP target systems: no specific release is required. CTS compatibility is sufficient.

○       Non-ABAP target systems:

■       Scenario CTS and PI: minimum release is SAP NetWeaver 2004 SPS 13.

■       Scenario CTS and EP: minimum release is SAP NetWeaver 2004 SPS 09.

■       For other scenario target systems, any SAP NetWeaver release can be addressed.

You can use the CTS deploy Web service in the AS Java of a different SAP NetWeaver system with SPS 12. You only need the AS ABAP as the Domain Controller in this case. More information about using the CTS deploy Web service in another SAP NetWeaver system is available in SAP Note 1003674.

Procedure

Configuring the CTS System

The necessary steps are mostly performed in the Transport Management System (TMS). To set up an AS ABAP system for managing transports into any kind of SAP systems you only need to update (or upgrade) an existing system to SAP NetWeaver 7.0 SPS 12 or to install a new system.

To configure the CTS system, proceed as follows:

...

       1.      Configure the AS ABAP transport domain controller; that is, the SAP system in which the transport route configuration is maintained centrally for all systems in the same transport domain.

More information: Configuring the Transport Domain.

       2.      Define transport systems.

                            a.      Create Non-ABAP systems.

                            b.      Configure Non-ABAP systems.

       3.      Define transport layers and routes.

...

■       Creation of objects and preparation for transport (developer, in the appropriate development environment).

■       Creation of a workbench request (administrators using the ABAP Transport Organizer, or developers using a Web UI in their development system. If developers (in the PI area, for example) are familiar with the ABAP part, they can use the Transport Organizer also directly).

■       Attachment of the development objects to the request (developers using a Web UI in their development system).

■       Import into target systems (administrators using the ABAP Transport Organizer).

Configure the AS Java System

       1.      You have to configure the Destination Services of AS Java.

More information: Configuring the Destination Service.

       2.      Create a new RFC-destination. It must be named sap.com/com.sap.tc.di.CTSserver.

More information: Destination Service and Maintaining RFC Destinations.

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

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.

More information: Creating a Development Track.

Performing the Transport

...

       1.      Open the Change Management Service (CMS) Web UI.

More information: Launching the NWDI Web User Interface.

       2.      In the Transport Studio, open the Approval tab.

       3.      Choose Release to CTS from History button.

       4.      In the dialog that appears, choose Approved in History to display the SCA files, select an SC displayed here, and confirm with Release to CTS…

       5.      In the dialog that appears, log on with a user that has transport permissions on the CTS System. If a transport request is available, the SCA file can be attached. Complete the dialog.

Additional Information – CTS, SPAM, JSPAM, and NWDI

In a typical system landscape there different transport tasks - the CTS is only one of these. These tasks are:

●      System update:

○       ABAP environment.

○       Java environment.

●      Transports of new development objects from Development to Quality Assurance and Production.

○       ABAP and mixed (ABAP/Java/Portal) environment.

○       Java only environment.

In the following table you see when to use which tool:

	SPAM	JSPAM	CTS	CMS of  usage type DI
ABAP system update	X
Java system update		X
Transports in ABAP or mixed environment			X
Transports in the Java environment  during development				X
Transports in the Java environment  during development in a modification scenario		X (combined  with CMS)		X (combined with JSPM)