CMS Transports (ES Repository) 

General

Use the following tools for ESR content transports using Change Management Services (CMS).

●      Use the Landscape Configurator of CMS to set the transport landscape using XI tracks.

●      Use the Enterprise Services Builder to export ESR content of the development system or of the consolidation system (for emergency corrections) and to track completed transports.

●      use the Transport Studio to perform transports using CMS:

This section focuses on the basic steps and options for CMS transports. More detailed procedures are referenced at the relevant points.

Configuration of the Transport Landscape

CMS supports the defintion of different transport landscapes using the definition of XI tracks in the Landscape Configurator. The following scenarios are supported:

In the case of transport scenarios with linked tracks, the objects versions in PROD1 must be identical to those in DEV2. You can only link XI tracks from different system landscapes (see also: Connecting Tracks); this means if you link two tracks, A and B, a system from track A may not appear in track B. You can enter the systems for both system landscapes in a System Landscape Directory.

ESR Content Transport within a Transport Landscape

In CMS mode, you perform transports of ESR content using the ES Builder and the Transport Studio of CMS. The tools focus on the following transport areas:

Transport Functions in the ES Builder and Transport Studio

Enterprise Services Builder (ES Builder)	Determining the object set for transport
	Status Display
	Resolving conflicts in imports
	Finding Transports
Transport Studio:	Importing change requests to the target system (Development, Consolidation, Assembly)
	Assembling software component versions (Assembly)
	Quality assurance step (Approval)

In the following it is assumed that you have already created an XI track in the Landscape Configurator for the contents of the Enterprise Services Repository that are to be transported. To transport contents of the ES Repository using CMS you must enter the software component versions of the contents to be transported in the XI track.  Furthermore, the change list transport is activated.

Transport Units in the ES Builder

Specify the object set of a transport for design objects in the ES Builder. You can transfer either change lists or transport lists to the CMS. Once the change or transport list has been exported from the Integration Builder or ES Builder, it appears as a change request in the Transport Studio.

Change Lists

The Integration Builder collects all changes to objects in a change list. It stands to reason that these are the changes you want to transport (from the development system, for example). Once you have released the change list, its status changes from Open to Transportable. To transfer it to the CMS, choose Release for Transport in the context menu on the Change Lists tab page. All changes at the time of release are transported in a change list.

Transport Lists

To compile a list of objects independently of change lists, you use the transport wizard to create transport lists. To create a transport list, proceed as follows:

...

       1.      Select Tools → Export Design Objects (Enterprise Services Builder).

       2.      Select the Transport Using CMS mode and determine the object set in the next step.

You can use change lists as a filter when determining the object set in the transport wizard. Objects lists compiled in this way nevertheless have all the normal properties of a transport list.

The ES Builder displays the transport list on the Change Lists tab page. This list is transferred directly to the CMS and has the status Waiting for export…until the process is complete. Object versions that are active at the time the transport list is compiled are transported in a transport list.

Interaction with the Transport Studio

Within an XI track you can transport objects from a development system (DEV) to a consolidation system (CONS) and then from the consolidation system (CONS) to a productive system (PROD). Depending on the target system, the ES Builder provides various options for determining the transport units:

Transport Units by XI Track and Transport Scenario

Type of XI Track	Supported Transport Units (Depending on Transport Scenario)
	From DEV to CONS	From CONS to PROD
ES Repository	Change and transport lists	Usually: Software component versions (in the Transport Studio)
		Change and transport lists (emergency corrections in the ES Builder)

As shown in the table, the usual transport units and the necessary steps depend on the type of the XI track and the transport scenario.

In the CMS Transport Studio, there are a number of tab pages for each track, which you work through one after the other during a transport. The tab page on which your exported change or transport lists are shown depends on the ES Builder you are working with (development, consolidation, or productive system). The following figure shows the process for the ES Builder.

You usually export transport requests from the development system, which appear in the import queue of the Transport Studio for the consolidation system. You control the rest of the transport from here.

If you have to make emergency corrections in the ES Repository of the consolidation system then you can, in addition to the normal transport route (shown above), export change or transport lists from the ES Builder  These exports can be necessary, for example, due to time-critical emergency corrections. In the Transport Studio, they appear on the Assembly tab page. You can then either reassemble the whole software component version or create a package containing just the changes for the productive system.

More information: Transporting Design Objects

The following table sums up the normal procedure of transports in CMS (as shown in the figure above). The sequence of the tab pages in the Transport Studio corresponds to the transport route within a track.

Development Status of the XI Track in the Transport Studio

Step	Tab Page	Use
	Check-In	You use check-in to make archive files with the extension .PRA that you have received from an external source known to the Change Management Service, and make them available for transport through the development landscape. Checked-in archives are added to the import queue on the Development tab page. Integration Builder or ES Builder users do not use this function at present because both tools have their own import function (more information: Transporting Objects Using the File System).
0	Development	This import queue contains checked-in archives and exports from other XI tracks connected to this track (more information: Connecting Tracks).
1	Consolidation	Once a transport request has been exported in the development ES Builder, this is where the change requests appear for each software component version for import to the consolidation system of the ES Repository.
2	Assembly	After import in the consolidation system, this is where you assemble transports of software component versions.
3	Approval	This tab page displays assembled software component versions. You use this step for quality assurance, to decide which changes to import to the productive system.
4	Production	After approval, the transport is ready for import to the productive system. The corresponding tab page is only displayed if you have entered a productive system in the corresponding track.