Introduction
The SAP CTS+ (Change and Transport System Plus) is an advanced tool for managing the transport of software configurations and changes across different environments within an IT landscapeintegration in MediationZone enables streamlined management of configuration and workflow transport across different environments. This integration allows for greater control, flexibility, and efficiency when moving configurations between development, test, and production systems. You can find more information on SAP CTS+ in the https://help.sap.com/.
Key Features of the SAP CTS+ Integration in MediationZone
...
Simplified Configuration Management: Manage regular system exports and workflow packages
...
seamlessly through the SAP CTS+
...
interface. Please note that Development Toolkit bundles are
...
excluded from this integration.
Flexible Import
...
Options: You can easily import configurations
...
to any system in your landscape using
...
CTS+.
...
‘Loose Coupling’ for Exports: In this integration, the export step and the CTS+ transport are handled separately. The System Export is done independently meaning that you would trigger the exports via the regular System Export UI, or by using mxsh/mzcli commands and then provide them to CTS+ for import.
...
For more information on SAP CTS+ Please refer the https://help.sap.com/. You can search for related documentation with ‘CTS+ Documentation’.
System Parameters
...
System Parameter
...
Description
...
mz.sourcesystems
...
This parameter (of type list) is valid only for integrations with SAP CTS+. It enables you to restrict the source systems from which exports (regular configuration and Workflow Package)can originate. If the parameter is left empty, exports from any system will be allowed.
Things to note:
This parameter is only effective when an import is triggered via the CTS+ API. Imports initiated through the System Import UI or the command line interface are not impacted.
The value of this parameter must exactly match the value specified in the
mz.namesystem parameter of the source system. (mz.namecan be changed at any time in the source system but changes will only take effect after the system is restarted.mz.namecorresponds tomzexport.mz.namein an export file. This parameter is used to determine if an import should be permitted)
| Info | ||
|---|---|---|
Example - System Parameter use
|
Preparing a System Export for CTS+
The export is handled in CTS+ using the “loose coupling” approach. This means you first perform the export as usual in the source system, then manually make it available to CTS+.
...
The source systems for imports can be customized—either allowing all systems or limited to specific ones, as defined by the
cts.source.systemsproperty. For more information, see https://infozone.atlassian.net/wiki/x/8BVCD
...
.
...
Make the System Export available to CTS+: See the steps outlined in the CTS+ documentation at the https://help.sap.com/ for more information. Once the export is made available to CTS+, it can be used for importing into target systems via the CTS+ API.
Note!
When setting up your configurations and system exports, remember that the entire content of an export will be imported into the target system. Therefore we recommend the following:
...
Decoupled Export Process: With loose coupling between export and transport, exports are triggered separately from the CTS+ transport process. Use the System Export tool in Desktop, or the https://infozone.atlassian.net/wiki
...
Restrict the exports to contain only the use cases you want to import into other systems.
System Imports triggered via CTS+
When triggering a system import using CTS+, keep in mind that the entire content of an export will always be imported into the target system.
...
Verify that the export can be imported into the target systems: The export system’s name must be added to the import system’s ‘System Property’, mz.sourcesystems. Please refer to https://infozone.atlassian.net/wiki/x/8BVCD
...
Make sure there are valid (local) External References in the target system
...
Trigger the import via the CTS+ API: See the steps outlined in the CTS+ documentation at https://help.sap.com/ for more information.
...
Verify Configuration Source: To check the source of any configuration, view the Properties UI. In the History tab, the Comment column will display:
LOG: Imported from
<export file>CTS+ Transport ID:
<CTS+ ID>SOURCE SYSTEM:
<mz.name / mzexport.mzname>ORIGINAL COMMENT:
<original comment>
...
/spaces/MD93/pages/205656966/mzsh?atl_f=content-tree command line tool, to create export files, which you then upload to CTS+ for transport and deployment.
Subsections
This section contains the following subsections: