Show TOC

 Transporting Non-ABAP Objects in Change and Transport System Locate this document in the navigation structure

 

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.

The aim is to have one transport tool that supports all development workbenches and applications. The tools for creating applications and content remain the same. The different workbenches of the applications offer options to attach your objects to a CTS transport request. The level of integration depends on the particular workbench and application.

In this way the enhanced Change and Transport System provides a unified transport tool and makes the work of administrators easier when executing imports. You only need access to one tool to execute imports for different backend systems. The deployment tools are called automatically. CTS allows you to monitor imports and analyze errors. The import queues and history in CTS give an overview of imports that have already been executed or which are planned.

Implementation Considerations

The usage types Application Server Java and Application Server Java Extensions must be installed. The AS Java is required as Deploy Web Service host.

Even if you want to use enhanced CTS only for non-ABAP systems, you still require an SAP NetWeaver Application Server ABAP for the domain controller.

The communication system where the Transport Organizer Web UI is located must be a Unicode system.

Configuration steps are required to enable your systems to transport non-ABAP objects using Change and Transport System.

Integration

The enhanced functions are integrated into Change and Transport System. The UIs of the associated applications have also been enhanced.

SAP provides a close integration into CTS for some SAP applications. This means that non-ABAP objects can be attached to transport requests directly from the SAP application. Examples of closely integrated applications are:

  • SAP HANA

  • Lifecycle Management Console (LCM) of SAP BusinessObjects Business Intelligence (BI)

  • SAP NetWeaver Development Infrastructure (NWDI)

  • SAP NetWeaver Portal

  • Process Integration (PI)

See the Resources on CTS+ page in SAP Community Network (SCN) at http://scn.sap.com/docs/DOC-8576 for examples of guides of these and other applications that provide integration in the enhanced CTS.

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. Refer to the individual application's documentation for more information.

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.

More Information

  • For examples of guides of the individual applications on how to configure the application for the enhanced CTS, see the Resources on CTS+ page in SAP Community Network (SCN) at http://scn.sap.com/docs/DOC-8576.

  • For prerequisites and limitations of the enhanced Change and Transport System, see SAP Note 1003674.

  • For further documentation on transporting objects of the individual applications, see the following information: