Show TOC

Configuring Export DestinationsLocate this document in the navigation structure

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

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 Change Management Service (CMS) or 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 of SAP NetWeaver Application Server Java.

  • 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 of SAP NetWeaver Application Server Java by selecting Start of the navigation path Configuration Management Next navigation step Security Next navigation step Destinations End of the navigation path.

  2. Choose the Destinations tab.

    All available destinations are displayed in the destination list.

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

  4. Choose Continue.

  5. Under Connection and Transport Security Settings, 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.

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

    • Authorizations of the role SAP_CTS_PLUS.

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

    • Authorizations for the RFC connection using the Java Connector. For more information, see SAP Note 460089 Information published on SAP site.
    Caution Enter the client entered in the parameter NON_ABAP_WBO_CLIENT in TMS.
    For more security recommendations, see Security for the Enhanced Change and Transport System (CTS+).

  6. Under Specific Data accept the default settings.

  7. Save your entries.

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

Configuring Multiple Export Destinations for Multiple Communication Systems

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

  1. Start the destination management in SAP NetWeaver Administrator (where the CMS/CM Services run) by selecting Start of the navigation path Configuration Management Next navigation step Security Next navigation step Destinations End of the navigation path.

  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 CMS/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 CMS, you must specify the name of the export destination when creating a development track under RFC Destination. For more information, see Creating a Development Track in the Development Infrastructure administration documentation of the SAP NetWeaver Application Server Java.

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, refer to Managing Transport Settings under Using CM Services in the Development Infrastructure administration documentation of the SAP NetWeaver Application Server Java.