Show TOC

Background documentationSystem Cluster


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.

The graphic shows a sample three-cluster track. 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).

Note Note

When creating a cluster track, for example, consisting of a development, a test, a pre-production, and a production cluster, it is possible from a technical point of view to set up a so-called “uneven” cluster track. “Uneven” means that not all system clusters in the cluster track contain the same number of systems with the same roles. For example, if the PI track does not have a pre-production system, but all other tracks have one, you can create a pre-production cluster for the other applications and omit PI from the pre-production cluster.

However, if you want to use these clusters with projects in Change Request Management or Quality Gate Management, you must carefully set up your projects so that they support the “uneven” cluster track. For more information, see chapter 7.3.2. of the guide How To... Set Up cCTS for ChaRM and QGM.

End of the note.

More Information