Defining and Configuring Non-ABAP Systems 
Procedure
You are in your TMS domain controller. Perform the following steps:
Call transaction STMS.
Choose System Overview.
Choose
SAP System 
Create Non-ABAP System 
.The TMS: Configure Non-ABAP System dialog box is displayed.
Create the non-ABAP system with a system ID and a description.
Select the CTS system as the communication system.
When using NWDI with CM Services: If you want to transport Development Infrastructure objects (SCAs, SDAs, or DTR activities) with CTS and use CM Services, set the Create Development Configuration flag under Development Infrastructure.
In addition to this, specify the URL for the System Landscape Directory (SLD) for the first system in your system landscape (which you use for NWDI) in the following format: http://<host of target system>:<5<system number>00>.
NoteYou can only specify one SLD URL for each transport landscape. If you want to make changes to the URL for a specific system, then the changes also apply to all systems in the landscape.
End of the note.Make the following settings, depending on whether your system is a source system or a target system (or both):
Non-ABAP system as source system
Under Source System Settings, select the Activate Transport Organizer flag and enter the client of the ABAP communication systems where you want to use Transport Organizer.
Non-ABAP system as target system
Under Target System Settings, select the Activate Deployment Service flag. Select the required deployment methods. In the Target Host field, enter the host of your target system in the format <Rechnername> and the two-character system number in the System No. field. After saving your settings, the system automatically generates the complete URL to the target system from the values you entered.
If you have selected the deployment method File with which you can transport any files, then you have to enter a path to a directory in the Directory field where the files can be stored.
NoteWhen using NWDI in connection with CM Services: For Development Infrastructure (DI) type systems (checkbox Create Development Configuration is selected) you have to specify both source and target system settings for the runtime system so that the runtime objects developed in NWDI are automatically deployed on the central runtime system. If you use Activity-based SDA transports, then development system is only of type DI.
End of the note.Save your settings and confirm that you want to distribute the TMS configuration.
The system now generates all required parameters and their values automatically by default. To display and modify these parameters, select your system in the system overview and choose the Transport Tool tab page.
For more information, see Change Standard Settings for Source Systems and Change Standard Settings for Target Systems.
CautionThe following applies to systems with release SAP NetWeaver 7.1 or higher: If you chose the deployment method SDM/DC, you must change the generated target port in the value of the parameter DEPLOY_URL manually from 5<system number>18 to 5<system number>04.
End of the caution.Depending on the deployment methods selected, the system asks you for the users and passwords for the selected deployment methods. Enter them.
If you selected the Development Infrastructure flag under Development Configuration, as described in step 6, the system starts the Development Infrastructure - Configuration Service UI. You can create your development configuration here.
For more information, see Using the Configuration Service.
Result
You have configured your non-ABAP systems and you can now check whether your settings are configured correctly (using the transport control program).
Your systems are ready to be included in a transport route in CTS. In TMS, proceed as usual for ABAP systems.