Organizing the Transports in the Landscape
Different scenarios are available that support you in organizing the transports in your system landscape. Depending on your requirements decide which one suits best your situation.
-
CMS without CTS integration
In SAP NetWeaver Development Infrastructure (NWDI) the Change Management Service (CMS) is a Java-only transport solution for transporting Java-based applications. CMS is used for configuring the landscape and for performing transports within the landscape.
-
CMS with CTS integration
For heterogeneous system landscapes, an integration of CMS and Change and Transport System (CTS) of the SAP NetWeaver Application Server for ABAP is available. The Software Component Archives (SCAs) assembled in CMS can be attached to a CTS transport request (ABAP-based). In such an integration scenario the development system and if needed consolidation system are configured in CMS but all other target systems ( test, pre-production, production systems, for example) are configured in the CTS communication system (AS ABAP). The granularity of the transport and deployment unit is a whole SCA.
-
CM Services (always with CTS)
For a tight integration between NWDI and CTS, Change Management Services (CM Services) are available that allow you to perform the configuration of the NWDI development and transport landscape completely from within CTS. The idea is that CTS is configuring the whole landscape and is also performing the transports. In the background, CM Services is used to create development configurations and to initially fill up the CBS buildspace and the DTR workspaces if needed. Using CM Services transports can be performed on Software Component Archive (SCA) or on Software Deployment Archive (SDA) granularity.
In this scenario, CMS is used for all transports of Java-based developments (NWDI). Use this scenario in the following situations:
-
If you already know NWDI with CMS and you are fine with the process and the functions offered and you do not need the integration with CTS.
-
If you are new to NWDI, and you do not know neither CMS nor CM Services, and you do not need the integration with CTS.
-
If transporting on SCA granularity is sufficient.
CTS and CMS can be used separately. CMS is used for Java-based development objects. The enhanced CTS is used for transports of ABAP and non-ABAP objects, such as EP content, PI objects, SLD. The following figure shows the transports in an ABAP-based system landscape in the CTS using CTS’s Transport Management System (TMS). The bottom part shows the transports in a Java-based system landscape in the NWDI using the Change Management Service (CMS).
In this scenario, CTS is used for transports to quality and production systems, NWDI is used for source control, build support and transports to development and consolidation systems. Use this scenario only in the following situations:
- If you want to use CTS as the transport tool for the following reasons:
-
CTS allows more flexible transport landscapes compared to CMS.
-
Java transports need to be coupled with other transports.
-
Integration in SAP's Change Control process tools is required.
-
-
If transporting on SCA granularity is sufficient.
If you use the enhanced CTS with NWDI, you can combine ABAP and Java transports to provide:
-
Automatic synchronization for mixed applications (for example, Web Dynpro Java application together with Portal iView); that is, you use a single tool to transport parts of one and the same application instead of using different tools for transporting parts of one and the same application.
-
Central control of all transports into production systems.
-
Traceability of transports, flexible transport routes, scheduling.
The CTS integration in NWDI is implemented during the assembly step in the NWDI, where a Software Component Archive (SCA) is produced that is attached to a TMS transport request. The further transport steps can then be handled using the CTS TMS. Here, the deployment in multiple test and productive systems can be easily handled.
In this scenario, you closely integrate NWDI and CTS. You can use CM Services to manage development configurations and CTS for maintaining transport landscapes and executing transports. Use this scenario only in the following situations:
- If transporting on SCA granularity is not sufficient and you would like to perform transports on a more granular level (SDA/DC) by using deployable transport.
If you use CM Services with NWDI the CTS system is used to configure the landscape and to perform transports. The transport granularity can be single activities and sources, or SDAs based on activities that have been changed. The following graphic shows the workflow of an activity-based SDA transport. Here, the runtime objects (deployable SDAs) of the changed sources are transported, not the sources themselves. The file type used is .dip. It is equally possible to export SCAs and transport them the same way using the Export Service of CM Services.
