Transporting Non-ABAP Objects in Change and Transport System 
The enhanced Change and Transport System enables you to transport Java objects and SAP-related non-ABAP applications in your system landscape, alongside ABAP objects. You can also administer non-ABAP systems in a CTS transport domain in SAP NetWeaver Application Server ABAP.
Transportable Objects
You can use CTS to transport the following additional objects:
Java-based and J2EE/JEE-based objects
Software Component Archives (SCAs)
Enterprise Application Archives (EARs)
Software Deployment Archives (SDAs)
DTR activities
More information: Integrating NWDI Transports with the Change and Transport System
Objects from the SAP NetWeaver usage type SAP NetWeaver Portal (EP)
Enterprise Portal Archives (EPAs)
Enterprise Portal Applications (PARs)
Knowledge Management objects (KM Content and KM Configurations)
More information: Transporting Portal Objects
Exporting KM Content
Non-ABAP objects from the SAP NetWeaver usage type PI (Process Integration)
Integration Builder objects (TPZs)
More information: Transporting Objects from SAP NetWeaver XI by Using CTS
System Landscape Directory content objects (products, software components, technical systems, and business systems)
More information: https://www.sdn.sap.com/irj/sdn/nw-sld
Content objects created using Master Data Management
You can transport these objects together with ABAP objects in a single transport request. When you run imports in Transport Management System (TMS), the system performs the appropriate deployment step automatically.
Best practices, and any exceptions or constraints to this information are documented in SAP Note 1003674.
Implementation Considerations
The enhanced CTS functions are available as of SPS 12 of SAP NetWeaver 7.0. For an overview of the functions provided by each SPS, see the Release Notes.
You require an SAP NetWeaver Application Server ABAP and an SAP NetWeaver Application Server Java. We recommend that you use a dual-stack system (such as an SAP Solution Manager system) as the domain controller.
Note
You can also use the Java components required by CTS in the SAP NetWeaver Application Server Java of a different SAP NetWeaver system. You only need the SAP NetWeaver Application Server ABAP as the domain controller in this case.
Integration
The enhanced functions are integrated into Change and Transport System. The UIs of the associated applications have also been enhanced.
SAP NetWeaver Development Infrastructure (NWDI) is integrated more closely with CTS from SAP NetWeaver 7.0 Enhancement Package 1 You can use this version to create development configurations in Transport Management System (TMS) and to transport both individual activities and versions of an entire software component (SCA) in transport requests. For more information about the concepts and how to use NWDI's new CTS-linked capabilities, see SAP Note 1167568.
Constraints
In some scenarios, you need to perform some manual actions when you add objects to transport requests. Some object types require you to perform manual actions after the deployment as well.
Even if you only want to use enhanced CTS for non-ABAP systems, you still require an SAP NetWeaver Application Server ABAP for the domain controller.
You must use Transport Organizer Web UI for the creation and administration of transport requests for non-ABAP systems. Transport Organizer Classic UI (transaction SE09) is only suitable for ABAP-only systems and dual-stack systems. We recommend that you use the Web UI for the non-ABAP objects of a dual-stack system as well.