Non-ABAP Systems and Dual-Stack Systems in
Change and Transport System
Non-ABAP Systems
Non-ABAP systems can be based on SAP NetWeaver Application Server Java or they can be non-SAP systems. CTS handles non-ABAP systems as virtual systems, which means they require an ABAP communication system. The transport control program tp runs on this communication system and it also hosts Transport Organizer (for source systems).
Dual-Stack Systems
Dual-stack systems consist of an SAP NetWeaver Application Server ABAP and an SAP NetWeaver Application Server Java. Before you can configure the SAP Application Server Java half of a dual-stack system, you must first include the dual-stack system in the transport domain and configure it.
Configuration Options for Non-ABAP Systems and Dual-Stack Systems
Non-ABAP systems and dual-stack systems can be the source or target of transports. When you create non-ABAP systems or dual-stack systems as source or target systems in your transport landscape, they are configured automatically with the appropriate standard settings. If you want to adjust these settings to the preferred processes in your system landscape, you can modify the relevant parameters accordingly.
More Information
Defining and Configuring Non-ABAP Systems
Configuring Dual-Stack Systems
Changing the Standard Settings for Source Systems
Changing the Standard Settings for Target Systems