You can transport configuration objects from the development directory to a consolidation directory, and from there to a productive directory. The following figure shows the usual transport units:
The first sections describe the normal transport path using CMS. In this case, you only transport changes in the development system with the Integration Builder; you control the rest of the transport to the consolidation and productive systems by using the CMS Transport Studio.
The last section deals with exports from the Integration Builder of the consolidation system, which may be necessary in the event of selective changes at short notice.
For more information about other possible transport scenarios, see PI-Transports Using the Change Management Service .
You have created an XI track in the Landscape Configurator and entered the addresses of the development, consolidation, and productive directory. There are no software component versions in the Integration Directory. Therefore, for directory transports using the CMS, you specify the software component version SAP-INTDIR 7.1 (EXCHANGE DIRECTORY 7.1) . This refers to all configuration objects of the Integration Directory.
Once you have made this setting, you can create transport lists for the CMS. The status of the change lists no longer changes to Closed immediately after their release, but first changes to Transportable.
You can deactivate the transport of change lists by using CMS (see also: Deactivating Change List Transports ).
(1) Transporting from the Development to the Consolidation Directory
The transport has two steps: You use the Integration Builder to export your changes from the development directory and then use the Transport Studio to transport the changes to the consolidation system.
Exporting Transport Lists
To release changes to the CMS for transport to the consolidation directory, you use transport lists. The transport sequence is important. To keep the number of units to be transported small and easy to check, you are therefore not permitted to transport using change lists in the development directory (see also: Integration Directory Transports ).
Use an appropriate name for your transport list. The name you use is visible in the Transport Studio later.
Transporting Changes to the Consolidation System in the Transport Studio
A change request for the change or transport list appears in the Transport Studio on the Consolidation tab page.
(2) Transporting from the Consolidation to the Productive Directory
When transporting to the productive directory, you transport the change lists that you released after import to the consolidation directory to the productive system:
If this option is selected, only the change and transport lists selected in the dialog box are considered in assembly. If it is not selected, a complete copy of the software component version is created.
You use the Assembly Mode to determine how the CMS handles unresolved import conflicts in the productive repository.
Stop if a component is inconsistent (Default) Assembly is terminated if there are any unresolved import conflicts.
Assemble consistent component(s) only Assembly is executed for all consistent software component versions. Inconsistent software component versions are skipped.
Assemble inconsistent components too The same as the last mode, except that inconsistent software component versions are also included.
Note that in directory transports the sequence of transport, confirmation, and import is relevant in the assembly, approval, and production steps of the Transport Studio.
Selective Exports from the Consolidation Directory
When you transport using CMS, the entire contents of the Integration Directory are always transported. After an initial complete copy of the consolidation directory, you will not usually want to transport the complete Integration Directory each time. To transport changes in the consolidation directory to the productive directory, proceed as follows: