Introduction
The CTS+ Integration allows users to import configurations (regular configuration exports and workflow packages) to any system using SAP CTS+. The imports can be set to originate from any or a selection of specific source systems. Allowed source systems are specified in the System Parameter mz.sourcesystems.
Exports from source systems are not triggered using CTS+. They are produced using the regular System Export UI, then presented to CTS+ using “loose coupling”. Please refer to CTS+ User Documentation for more information.
Regular System Exports and Workflow Packages can be managed using the CTS+ Integration. Development Toolkit bundles are not part of the integration.
System Parameters
System Parameter | Use |
|---|---|
mz.sourcesystems | This parameter (of type list) is valid only for integrations with SAP CTS+ . It allows for restricting from which source systems an export (regular configuration and Workflow Package) can originate from. Leaving it empty will allow any/all systems. Note that this parameter is valid only when an import is triggered using the CTS+ API. Imports triggered using the System Import UI, or command line interface will not be affected. The value of mz.sourcesystems must be exactly as specified in the System Parameter mz.name of the source system. (Note that mz.name can be changed at any time in the source system; changes will be valid after a restart of the system. mz.name equals mzexport.mzname in an export file. The latter parameter is used when evaluating if an import shall be allowed.) Example of usage: <property name="mz.sourcesystems" value="dev1,test,staging"/> |
Preparing a System Export for CTS+
The export procedure is done using the “loose coupling” mechanism in CTS+. Meaning, you do the export as usual in the source system, then make it available to CTS+ manually.
Verify that your export will be possible to use/import in other systems.; the source/export system’s name must be present in the target/import system’s System Property mz.sourcesystems. Please refer to (LINK TO SYS PARAM USER DOC).
Create your System Export using the System Export UI or command line interface commands.
Make the System Export available to CTS+. Please refer to CTS+ User Documentation for more information. This System Export can then be used for imports to target systems using the CTS+ API.
When creating your configurations and system exports, keep in mind that the full content of an export will be imported to the target system. Thus, we recommend:
Use External References (LINK TO EXT REF USER DOC) when configuring variables that are local for a system. 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 use cases you want to import to other systems.
System Imports triggered via CTS+
The full contents of an export will always be imported to a target system.
Verify that the export will be possible to import to the target systems.; the source/export system’s name must be present in the target/import system’s System Property mz.sourcesystems. Please refer to (LINK TO SYS PARAM USER DOC).
Make sure you have valid (local) External References present in/for the target system.
Trigger the import via the CTS+ API. Please refer to CTS+ User Documentation for more information.
You can verify the originating source of any configuration present in a system in the Properties UI of that configuration. The Comment column in the History tab will contain the following parameters if the configuration originates from an export:
LOG: Imported from <export file>
CTS+ Transport ID: <CTS+ ID>
SOUCE SYSTEM: <mz.name / mzexport.mzname>
ORIGINAL COMMENT: <original comment>
Optionally, clean out not used configurations manually in the target system.