Show TOC

Prerequisites for Non-ABAP Transports Locate this document in the navigation structure

The following components must be configured before you can use the enhanced Change and Transport System:

  • CTS Deploy Web service (SAP NetWeaver AS Java)

    This is a Java Web service responsible for communicating with the deployment tools in non-ABAP systems. The transport control program tp communicates with the CTS Deploy Web service when deploying the non-ABAP objects.

  • Deploy Web service client (SAP NetWeaver AS ABAP)

    This client on the ABAP side makes it possible for the transport control program tp on the SAP NetWeaver AS ABAP to communicate with the CTS deploy Web service on the SAP NetWeaver AS Java.

    The Deploy Web service client is comprised of the logical port CTSDEPLOY (which contains the name of the Deploy Web service and additional parameters) and the HTTP connection CTSDEPLOY (which contains the destination of the Deploy Web service).

  • Transport Organizer Web UI (SAP NetWeaver AS ABAP)

    A tool - an ABAP Web Dynpro application - where you create and edit transport requests for non-ABAP systems.

  • Transport Directory

    Consistent transport directory for SAP NetWeaver AS Java and SAP NetWeaver AS ABAP.

    Note Note

    If you cannot use a consistent transport directory, you can alternatively use a Java Connector connection for the data transfer. For more information, see Defining a Method for the File Transfer from the Source System and Defining a Method for the File Transfer to the Target System.

    End of the note.
  • CTS Export Client (source system)

    The objects to be transported and created or changed on the source system. The different export mechanisms in the workbenches of the applications and the export service take on the role of the CTS Export Client. The CTS Export Client communicates with the transport system by proposing a transport request for selection and attaching non-ABAP objects from the application to the transport request. This is called Close Coupling.

    For more information, see the documentation or guide on CTS integration of each application.

  • Import Service (target system - SAP NetWeaver AS Java)

    The objects from the source system are imported into the target system. The various deployment tools (SDM, Deploy Controller, and so on) take on the import service on the target system.

    For more information, see the documentation or guide on CTS integration of each application.

The figure below is a simple depiction of how these components interact:

This graphic is explained in the accompanying text.

Even if you only want to transport non-ABAP objects with the Transport Management System (TMS), then you must also have an SAP NetWeaver Application Server ABAP.