Show TOC

Background documentationSystem Cluster Locate this document in the navigation structure

 

Those systems in your transport landscape that you want to supply with transports at the same time can be grouped into system clusters. You create a system cluster for systems that have the same role (for example, DEV, TST, and PRD). In this way you can, for example, combine a Process Integration (PI) development system together with a Business Suite development system and a Portal development system into a single cluster. You can also combine the relevant test, and production systems into one cluster.

You can combine ABAP and non-ABAP systems into a system cluster.

You configure system clusters centrally in the central CTS server using the Central CTS Configuration Web UI. System clusters are represented in Transport Management System (TMS) by a three-character system identifier (SID), like any other system. However, they are not real systems that you have to install. The cluster SID has to be unique in your transport landscape.

You can configure your system clusters in such a way that the central CTS server takes over the control of your transports. This means the local CTS can be deactivated.

This graphic is explained in the accompanying text.

Figure: Example of a system cluster landscape for PI, Portal, and Business Suite developments consisting of development, test, and production clusters.

The graphic shows a sample three-cluster-landscape. There is one development cluster, one test cluster, and one production cluster. Each cluster contains a PI, a Portal, and a Business Suite system with the respective role (development, test, and production).

More Information

Transport Collection