A UTM cluster application is intended to run on more than one computer. It has the following characteristics:
The UTM cluster application has to run under the same user ID on all computers to ensure that the same access permissions apply to the files used.
The configuration of the UTM cluster application, including the KDCFILE for all nodes, is created in a single generation run and is therefore the same for all nodes. This also applies in particular to the application name of the UTM cluster application.
The computers that belong to a cluster must be compatible in terms of hardware status and software configuration. Discrepancies involving compatible correction statuses, operating system versions and updates are possible. For details, see the Release Note.
The node applications of a UTM cluster application must all run under the same operating system (e.g. Solaris) with the same bit mode (32-bit or 64-bit on all nodes). Mixed configurations, such as Unix and BS2000 computers or even Solaris and Linux computers in combination are not possible.
A number of files that can be accessed jointly by all nodes are required in order to run a UTM cluster application. These are the UTM cluster files. For detailed information on the UTM cluster files, refer to the section "Runtime environment".
There are also files which are local to each node. A node application’s KDCFILE must be accessible from all node applications. You have to create these files with a node-specific filename prefix. For detailed information on the files local to the nodes, refer to the section "Runtime environment".
Special properties of a cluster on Unix and Linux systems
To run a cluster application, the user IDs used must not only have the same names on all the computers, but must also be managed internally by the operating system using the same user number assigned when the user ID was set up.
In order to run scripts across different computers, the nodes must mutually permit ssh access for the execution IDs.
On Unix and Linux systems, the Network File System/Service (NFS4) is used to access the common files. You can, for instance, use NetApp FAS as the NFS4 server system.
Special properties of a cluster on Windows systems
The Windows computers must all be members of a common Windows domain.
An identical Windows domain login must be used as the execution ID on all nodes.
On Windows, Windows shares are used with the CIFS protocol common on Windows.