Conigma CCM

System landscapes

Basics

In Conigma CCM, transports take place abstractedly on the basis of import steps. Normally one does not reuqest the import into a specific system, but to perform specific import step (e.g. "Import in QA").

Based on the configuration data defined in Conigma, it is then automatically determined which requests should be transported into which systems.

So-called "software components" and "delivery steps" are defined:

  • Software component: A rule that describes a set of transport requests that follow the same delivery logic. Example: "All requests from system DE1" or "All Workbench requests from system DE2".

  • Delivery step: An abstraction of 1-N possible target systems. For example, "Step QA" can mean that an import into system QA1, QA2 or QA3 takes place, depending on which component a request belongs to.

The following diagram illustrates this procedure:

If an import into step "QA" is requested via Conigma, this may result in an import of different requests into 3 QA systems in this example.

Figure in Conigma CCM

The setup described above would be mapped in the Conigma CCM as follows:

It should be noted that not only individual systems and clients can be specified.

For clients, a comma-separated list, a range (separated with "-") or the value "*" can also be specified. This way the number of rows in the Delivery Matrix can be reduced significantly.

For the special case of a delivery matrix which serves as a definition for targets for the initialization of transports of copies, a TMS target group can be specified instead of a target system.