Show TOC

Procedure documentationConfiguring Export Destinations Locate this document in the navigation structure

 

Note Note

You need to perform this configuration step on the SAP NetWeaver AS Java of your application system. If the release is different from the release of the SAP NetWeaver AS ABAP communication system read the documentation of the corresponding SAP NetWeaver AS ABAP release for correct instructions on how to configure export destinations.

End of the note.

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 change authorization in SAP NetWeaver Administrator.

  • You have a user with the appropriate authorizations to manage RFC destinations in SAP NetWeaver Application Server Java.

Procedure

Configuring Export Destinations for a Communication System

  1. Start the destination management in SAP NetWeaver Administrator by selecting   Configuration   Destinations  .

    All available destinations are displayed in the destination list.

  2. Create an RFC connection called sap.com/com.sap.tc.di.CTSserver by choosing New.

  3. Save the destination.

  4. In the Details area, enter the Connection Settings.

  5. In the Details area, under Logon Data, we recommend that you select one of the authentication options that use Single Sign-On (SSO) for the connection to your CTS server. These are the Current User options.

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

    Note Note

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

    • Authorizations of the role SAP_CTS_PLUS.

      For amendments to the role SAP_CTS_PLUS, see also SAP Note 1003674, under General limitations.

    • 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. Save your entries.

    If you want to test the connection, choose Test Destination.

Configuring Multiple Export Destinations for Multiple Communication Systems

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

  1. Start the destination management in SAP NetWeaver Administrator (where the CM Services run) by selecting   Configuration   Destinations  .

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