Show TOC

Procedure documentationCreating or Changing System Clusters

 

You create system clusters to group different systems with the same role. You do this in the Central CTS Configuration Web UI.

From a technical point of view, this means creating a virtual system with a system ID as a system cluster, and assigning systems that are to be contained in the cluster.

Note Note

When creating a cluster landscape, see also the note on so-called “uneven” cluster landscapes in the System Cluster topic. The link to the topic is in the More Information section.

End of the note.

Prerequisites

  • The systems fulfill the basic requirements to be included in system clusters (Release and Support Package level).

  • You are in the Central CTS Configuration Web UI.

Procedure

Creating a New Cluster
  1. To create a new cluster and add systems to it, choose Start of the navigation path Cluster Next navigation step Create Cluster End of the navigation path.

  2. In the dialog box, enter the required information, such as Cluster ID and Description. The Cluster ID must consist of three characters and must be unique within the transport domain.

  3. If you are configuring a source cluster, that is if you want to group development (source) systems in one cluster, select the Source cluster check box.

    For source clusters, you must select a client. The client is required to create transport collections. Therefore, you must select the client in which you want to use Transport Organizer and in which you want to create transport collections. Since the cluster is a virtual system, you must use the client of the ABAP communication system of the cluster. The correct client is usually the production client of the system to which you are currently logged on.

  4. Optional: If you want to add systems to the system cluster, select the systems from the list.

    Note Note

    If you want to add a system to the cluster that is not contained in the list, check that the configuration of the Landscape Management Database (LMDB) is consistent. You can do this in LMDB on the tab page Transport Domains.

    End of the note.

    For source systems, also select the client where you want to use Transport Organizer and in which you want to create transport requests.

    • For ABAP and dual-stack systems: All clients that exist in the ABAP system are displayed. Select the client in which development takes place. If you want to develop in multiple clients of an ABAP system you can add the system more than once using different clients.

    • For non-ABAP systems: The client that has been defined as TMS parameter NON_ABAP_WBO_CLIENT for this system is pre-selected. You cannot edit the client here.

    • For virtual or external systems: You must enter a client only if extended transport control is active in the system. You can either select one of the clients that exist in the system (or in the communication system) or enter any other client. This option is useful if you want to prepare the cluster assignment for systems or clients which do not yet exist.

    For target systems, it depends on your transport strategy whether you must select a client or not.

    • For target ABAP and dual-stack systems: You must select a client only if extended transport control is active in the system. All clients that exist in the system can be selected. If extended transport control is not active, no client can be selected.

    • For target non-ABAP systems: No client can be selected.

    • For virtual or external systems: You must enter a client only if extended transport control is active in the system. You can either select one of the clients that exist in the system (or in the communication system) or enter any other client. This option is useful if you want to prepare the cluster assignment for systems or clients which do not yet exist.

  5. If you want to distribute the TMS configuration to all systems in the transport landscape after the cluster has been created, select the corresponding checkbox.

  6. Choose Check to check your entries for completeness and consistency without closing the dialog box.

  7. If the check does not display any errors create the cluster.

Note Note

The cluster can only be created if the client is valid.

End of the note.
Changing an Existing Cluster
  1. To change an existing cluster, select the link with the cluster ID.

  2. Choose Display <-> Change.

    Except for the cluster ID, you can change any data of the cluster.

  3. Optional: To add systems to the cluster, choose Add Row and select the system that you want to add to the cluster. If a client is required, proceed as described under Creating a New Cluster.

  4. Optional: To remove systems from the cluster, choose Delete Row for the corresponding system.

    Note Note

    Before you remove a system from a cluster make sure that there are no modifiable transport requests of this system that are part of modifiable transport collections of the cluster. Otherwise, you will get an inconsistent system state.

    If you have defined an import target for the removed system you must delete the entry for this system after removing the system from the cluster.

    End of the note.
  5. Repeat the previous steps for all systems that you want to add to the cluster or delete from it.

  6. If you want to distribute the TMS configuration to all systems in the transport landscape after the cluster has been changed, select the corresponding checkbox.

  7. Choose Check to check your entries for completeness and consistency without closing the dialog box.

  8. If the check does not display any errors save your changes.

Result

The cluster has been created in the transport domain of the system to which you are logged on or changes have been made to an existing cluster of this transport domain.