Configuring 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 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.
You have change authorization in SAP NetWeaver Administrator.
You have a user with the appropriate authorizations in SAP NetWeaver Application Server Java.
The Java user that the CTS Deploy Web service runs under has the action Destination_Service_Write_Permission.
Start the destination management in SAP NetWeaver Administrator by selecting .
Choose the Destinations tab.
All the available destinations are displayed in the destination list.
Create an RFC connection called sap.com/com.sap.tc.di.CTSserver by choosing Create.
Choose Continue.
Under Connection and Transport Security Settings, select the Current User (Logon Ticket) option as authentication for the connection to your CTS server. 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.
Caution
Enter the client entered in the parameter NON_ABAP_WBO_CLIENT in TMS.
Under Specific Data accept the default settings.
Save your entries.
If you want to test the connection, choose Ping Destination.
This procedure only applies if you use NWDI in connection with CM Services:
Start the destination management in SAP NetWeaver Administrator (where the CM Services run) by selecting .
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>.
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.
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.