Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

...

Info

CTS+ Integration Inclusions

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

Flexible Import Configuration: You can import configurations (regular configuration exports and workflow packages) to any system using SAP CTS+. The imports Imports can be set configured to originate from any all source systems or a selection of specific source systemsselected 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 regular System Export UI, then presented to CTS+ using “loose coupling”. Please refer to CTS+ User Documentation for more information.

...

...

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

Use

Description

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

enables you to restrict the source systems from which exports (regular configuration and Workflow Package)can originate

from. Leaving it empty will allow any/all systems. Note that this parameter is valid only

. 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

using
  • via the CTS+ API. Imports

triggered using
  • initiated through the System Import UI

,
  • or the command line interface

will
  • are not

be affected
  • impacted.

  • The value of

mz.sourcesystems
  • this parameter must

be
  • exactly

as
  • match the value specified in the

System Parameter
  • mz.name system parameter of the source system. (

Note that
  • mz.name can be changed at any time in the source system

;
  • but changes will

be valid after a restart of
  • only take effect after the system is restarted. mz.name

equals
  • corresponds to mzexport.mz.

mzname
  • name in an export file.

The latter
  • This parameter is used

when evaluating
  • to determine if an import

shall
  • should be

allowed.
  • permitted)

Info

Example

...

- System Parameter use

Code Block
<property name="mz.sourcesystems" value="dev1,test,staging"/>

Preparing a System Export for CTS+

The export procedure is done handled in CTS+ using the “loose coupling” mechanism in CTS+. Meaning, you do approach. This means you first perform the export as usual in the source system, then manually make it available to CTS+ manually.

  1. Verify that your export will be possible to use/import in can be imported into other systems.; : the source/ export system’s name must be present in added to the target/ import system’s System Property ‘System Property’, mz.sourcesystems. Please refer to (LINK TO SYS PARAM USER DOC).

  2. Create your System Export using : Use the System Export UI or command line interface commands.

  3. 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 : 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. 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.

System Imports triggered via CTS+

The full contents When triggering a system import using CTS+, keep in mind that the entire content of an export will always be imported to a into the target system.

  1. Verify that the export will be possible to import to can be imported into the target systems.; the source/: The export system’s name must be present in added to the target/ import system’s System Property ‘System Property’, mz.sourcesystems. Please refer to (LINK TO SYS PARAM USER DOC).

  2. Make sure you have there are valid (local) External References present in /for the target system.

  3. Trigger the import via the CTS+ API. Please refer to CTS+ User Documentation : See the steps outlined in the CTS+ documentation at https://help.sap.com/ for more information.

...

  1. Verify Configuration Source: To check the source of any configuration

...

  1. , view the Properties UI

...

  1. . In the History tab

...

  1. , 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>

...

  1. Clean Up Unused Configurations (Optional): Manually remove unused configurations from the target system.