Show TOC

Procedure documentationConfiguring Export Destinations Locate this document in the navigation structure

 

To configure an export destination, proceed as described under Configuring Export Destinations for a Communication System.

When using SAP NetWeaver Development Infrastructure (NWDI) in connection with CM Services: You generally proceed as described under Configuring Export Destinations for a Communication System. In exceptions it is possible that you want to use different communication systems for different non-ABAP systems of your SAP application, for example, because you use multiple development system for different releases alongside each other and want to manage the transports across different communication systems. In this situation you have the possibility to configure different export destinations for the different non-ABAP systems of your SAP application. Proceed as described under Configuring Multiple Export Destinations for Multiple Communication Systems.

Prerequisites

  • You have a user with change authorization in Visual Administrator of the SAP NetWeaver Application Server Java.

Procedure

Configuring Export Destinations for a Communication System

  1. Open Visual Administrator on the installation drive of the SAP Application Server Java (AS Java) on which your application is running.

  2. Choose   Cluster   Server   Services   Destinations  .

  3. Create an RFC-type destination with the name sap.com/com.sap.tc.di.CTSserver by selecting Create.

  4. Under Connection Settings, enter the connection data of your communication system.

  5. Under Logon Data, select the Current User (Logon Ticket) option as authentication for the connection to your communication system. We recommend that you use Single Sign-On (SSO).

    If you cannot use SSO, select the Configured User option and enter your preferred language, a client, and an appropriate user and password.

    Note Note

    The user needs the following authorizations on the communication system (ABAP):

    • Authorizations of the role SAP_CTS_PLUS.

    • Authorizations for the RFC connection using the Java Connector.

      For more information, see SAP Note 460089.

    End of the note.

    Caution Caution

    Enter the same client here that is set in TMS in the NON_ABAP_WBO_CLIENT parameter for the corresponding non-ABAP system of your SAP application.

    End of the caution.

  6. Use the default settings under Repository Connection and Pool Settings.

  7. Save your entries.

    If you want to test the connection, choose Save and Test.

Configuring Multiple Export Destinations for Multiple Communication Systems

This procedure only applies if you use NWDI in connection with CM Services:

  1. Call Visual Administrator on the installation drive of the AS Java where the CM Services are running.

  2. Proceed as described under Configuring Export Destinations for a Communication System.

    When creating the RFC-type destination, you can select a name of your choice. We recommend you use the standard name sap.com/com.sap.tc.di.CTSserver and add an underscore and the system ID of the communication system:

    <sap.com/com.sap.tc.di.CTSserver_SID>.

  3. Create an export destination with a unique name for every communication system of your transport landscape that you want to use for the non-ABAP systems of your SAP application in connection with CM Services.

Result

You have configured one or more export destinations. Your SAP application is now coupled closely to the Change and Transport Management System.

When using NWDI in connection with CM Services, you must specify the name of the export destination in the transport settings (that was configured for the non-ABAP system) when configuring the development configuration for a non-ABAP system in the Development Infrastructure - Configuration Service.

For more information, see Managing Transport Settings.