Transporting Non-ABAP Objects in Change and
Transport System
Use
The enhanced Change and Transport System (CTS+) 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-based objects:
○ Software Component Archives (SCAs)
○ Enterprise Application Archives (EARs)
○ Software Deployment Archives (SDAs)
● 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)
● Non-ABAP objects from the SAP NetWeaver usage type PI (Process Integration):
○ Integration Builder objects (TPZs)
● System Landscape Directory content objects (products, software components, technical systems, and business systems)
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.
Any exceptions or constraints to this information are documented in SAP Note 1003674.
Implementation Notes
The enhanced CTS functions are available when you import Support Package Stack (SPS) 15 of SAP NetWeaver 7.0. You also require an SAP Application Server Java with the same Support Package level.
We recommend that you configure a dual-stack system.
Integration with Other Components
The enhanced functions are integrated into Change and Transport System.
The UIs of the associated applications have also been enhanced. To transport non-ABAP objects in CTS, you require a TMS domain controller. We recommend that you configure a dual-stack system as the domain controller.
The CTS Deploy Web service must exist on the SAP NetWeaver Application Server of the dual-stack system. The deployment proxy must exist in SAP NetWeaver Application Server ABAP.
You can also use the CTS Deploy Web service 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. More information about using the CTS Deploy Web service in another SAP NetWeaver system is available in SAP Note 1003674.
Restrictions
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.
You must use Transport Organizer Web UI for the creation and administration of transport requests for non-ABAP systems. You cannot use Transport Organizer Classic UI (transaction SE09) for non-ABAP systems. Transport Organizer Classic UI is only suitable for ABAP-only systems and dual-stack systems.
More Information
Change and Transport System - Overview (BC-CTS)
Configuring the Transport Domain
Configuring Dual-Stack Systems
Configuring the CTS Deploy Web Service