Administration Guide > Installation > New Installation > Automation Engine and Cluster

Automation Engine and Clusters

Clusters group computers in order to achieve increased computer capacity or workload distribution. AE can also run in a cluster.

Installation and configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. for a cluster are almost the same as they are for an individual computer. The most important steps are listed below. Other settings in the cluster itself depend on the cluster software in use.

Automation Engine

It is useful to integrate your Automation Engine in a cluster if it has only been installed on one computer.

Install the Automation Engine in a separate directory.
Enter the cluster's virtual IP address in the INI-file parameter hostname= (section [TCP/IP]).
Install the ServiceManager on all the cluster's computers in order to ensure that the server processes can be started if the computer is changed. The ServiceManager must be available as a cluster service.

Agents

Agents can also run in a cluster.

Install the agent in a separate directory.
Enter the cluster's virtual IP address in the INI-file parameter UC_EX_IP_ADDR (section [VARIABLES]).
Install the ServiceManager on all the cluster's computers in order to ensure that the agents can be started if the computer is changed. The ServiceManager must be available as a cluster service.

Example: Microsoft Cluster

Keep the following instructions in mind when installing a Windows agent in a cluster:

There are two different installation types. The ServiceManager and the agent are either installed on a shared disk (Type 1) or the ServiceManager is installed on a local disk and the agent on a shared disk (Type 2).

Type 2 does not require you to switch the cluster group during the installation. The ServiceManager must be installed on each node.

Type 1:

Install the Windows agent and the ServiceManager on a shared disk of the Microsoft Cluster. Perform the installation first on the primary node and, after switching the disk, on the secondary node in the same directory.
Enter the cluster's virtual IP address in the agent's INI-file section [VARIABLES]. Do so using the variable UC_EX_IP_ADDR.
Register the ServiceManager as a service (command "UCYBSMGR –install Phrase"). Leave the start type set to "Manually"; do not set it to "Automatically". Start this procedure on the computer on which the second installation was made, then switch the disk and continue on the primary node.
In the MSCS, define the Automic ServiceManager.Phrase as resource type "Generic Service".
Select the dependencies' shared disk and, if required, the IP address assigned to the group.
If the agent needs to use particular settings, use an extra variable for the host characteristics.

Type 2:

Install the ServiceManager on each node on a local disk unit.
Register the ServiceManager as a service on each node (command "UCYBSMGR –install Phrase"). Leave the start type set to "Manually"; do not set it to "Automatically."
Install the Windows agent on a shared disk of the Microsoft Cluster.
Enter the virtual IP address of the cluster or of the group in the agent's INI-file section [VARIABLES]. Do so using the variable UC_EX_IP_ADDR.
In the MSCS, define the Automic ServiceManager.Phrase as resource type "Generic Service."
Select the shared disk as a dependency and, if required, select the IP address assigned to the group.
The group can now be started on a node.
Use the ServiceManagerDialog to adjust the services (such as agent properties, automatic start).
Copy the updated *.smd and *.smc files to the other nodes (from the ServiceManager's installation folder).
If the agent should use particular settings, create a separate variable for the host characteristics.
The key that is used to communicate to the Server is entered in the Keystore file when the agent starts on the first node for the first time. Define the name and path of the Keystore file in the agent's INI file.
A copy of the first node's Keystore file must be available on the second node on which the agent should run using the same name. Otherwise, you cannot start an agent of the same name on a different computer if it is already registered on the system. This procedure is always required regardless of the authentication method that is used.