Import containers

Functional scope 

An import container is a container in which change requests and their associated transports are collected for an import step. When the import container is executed, the transports assigned to the change request are imported into the systems configured in the import container. The import container can be started manually, via context menu or automatically (time-controlled). The imports then follow the delivery routes maintained in the Delivery Matrix. A more detailed description of the import execution using import containers can be found in section Executing an import container

During the import process of an import container, several checks are carried out before and after the execution (precalculations / post-import actions). The main purpose of these checks is to ensure that the transport request does not contain missing dependencies on the target system(s) (e.g. Detection of missing predecessors  or Detection of overtakers ), can be imported successfully and does not cause inconsistencies. If all checks are successful, the import container takes over the actual import of the transport requests using asynchronous jobs that perform the import on each target system.

It is also possible to simulate an import container. In this case, all precalculations are also carried out without actually importing the transport request. This allows you to react to possible problems in advance and correct them if necessary before the actual import takes place.

Of course all these functionalities are configurable. The most important configuration elements of an import container are described in the Import options and the following sub chapters.