| Info |
|---|
What’s Included? Regular System Exports and Workflow Packages can be managed using the CTS+ Integration. Development Toolkit bundles are not part of the integration. |
Introduction
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 landscape.
Key Features of the CTS+ Integration in MediationZone
Regular System Exports and Workflow Packages can be managed using the CTS+ Integration. Development Toolkit bundles are not part of the integration.
Flexible Import Configuration: You can import configurations (regular configuration exports and workflow packages) to any system using SAP CTS+. Imports can be configured to originate from all source systems or a selected few. Allowed source systems are specified in the System Parameter mz.sourcesystems.
‘Loose Coupling’ for Exports: Exports from source systems are not triggered using CTS+. They are produced using 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, then presented or by using mxsh/mzcli commands and then provide them to CTS+ using “loose coupling”for import.
...
For more information on SAP CTS+ Please refer the https://help.sap.com/. You can search for related documentation with ‘CTS+ Documentation’.
...
Verify that your export can be imported into other systems: the export system’s name must be added to the import system’s ‘System Property’,
mz.sourcesystems. Please refer to (LINK TO SYS PARAM USER DOC). https://infozone.atlassian.net/wiki/x/8BVCDCreate your System Export: Use the System Export UI or command line interface commands.
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 to:
Use External References (LINK TO EXT REF USER DOC) when configuring variables that are local for a system, see https://infozone.atlassian.net/wiki/x/7AozD. This way, configurations will be valid for both source and target systems, and only the External References will be system-specific.
Restrict the exports to contain only the use cases you want to import into other systems.
...
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 (LINK TO SYS PARAM USER DOC). https://infozone.atlassian.net/wiki/x/8BVCDMake 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>
Clean Up Unused Configurations (Optional): Manually remove unused configurations from the target system.
...