Configuring RFC Destinations for Central CTS

To enable communication of the central CTS server with its managed systems RFC connections must exist from the central CTS server to the managed systems. For managed non-ABAP systems, the RFC connection must exist from the central CTS server to the ABAP communication system of the managed system.

This includes the following RFC destinations:

Transport Organizer destination: Required for working with transport requests (creating, deleting, changing transport requests). This destination is required for source systems only.
Import destination: Required for importing the CTS plug-ins to the managed systems
Deploy destination: The import process of a transport collection needs this destination to be able to import transport requests that are assigned to a transport collection.

Prerequisites

You have performed a validation in the Central CTS Configuration Web UI and the system tells you that RFC connections are missing.
You use Trusted System to log on to the managed system.
You use Secure Network Connection (SNC) for RFC communication with managed systems.
For the deploy destination, you need a technical user with specific authorizations in all managed systems.

Procedure

The Transport Organizer and import destinations can be re-used from existing SAP Solution Manager destinations. These were created when performing Managed Systems Configuration in SAP Solution Manager Configuration (transaction SOLMAN_SETUP). If the system tells you that either the Transport Organizer or the Import destination is missing, check the SAP Solution Manager Configuration.

The following procedure applies if you want to configure the Deploy destination:

Log on to the central CTS server (SAP Solution Manager system) and call the RFC destination maintenance using transaction code SM59.
Navigate to ABAP connections and create new ABAP R/3 Connections (Type 3).
Enter the data as described in Deploy Destination.
To create the destination, choose Save.
To make sure that the destination has been configured correctly, perform the tests available in transaction SM59.

Note
To perform the authorization test, the user that performs the test (logon user) must have the authorizations as described for the individual RFC destinations. Otherwise, the test can fail even though the RFC destination was correctly configured.

End of the note.

Result

You have configured an RFC connection to a managed system. Afterwards, validate the system again.

More Information

For more information on configuring RFC destinations, see Displaying, Maintaining, and Testing Destinations. If the link does not work, you can search for this documentation or use the following navigation path: http://help.sap.com/nw702 Application Help Function-Oriented View: English Application Platform by Key Capability Platform-Wide Services Connectivity Components of SAP Communication Technology Classical SAP Technologies (ABAP) IDoc Interface/ALE Implementation Application Link Enabling (ALE) Setting Up Communication Maintaining Remote Destinations Displaying, Maintaining, and Testing Destinations .
For more information on Trusted System, see Maintaining Trust Relationships between SAP Systems. If the link does not work, you can search for this documentation or use the following navigation path: http://help.sap.com/nw702 Application Help Function-Oriented View: English Application Platform by Key Capability Platform-Wide Services Connectivity Components of SAP Communication Technology Classical SAP Technologies (ABAP) RFC RFC Programming in ABAP Maintaining Remote Destinations Maintaining Trust Relationships between SAP Systems .
For more information on Secure Network Connection (SNC), see Secure Network Communications (SNC). If the link does not work, you can search for this documentation or use the following navigation path: http://help.sap.com/nw702 Application Help Function-Oriented View: English Security Network and Transport Layer Security Transport Layer Security on the AS ABAP Secure Network Communications (SNC) .
For more information on how to create a user for the deploy destination, see Deploy Destination.