Preparing for installation

System Automation for Multiplatforms is contained in several packages that must be installed on every cluster node that you want to automate. Package type and content depend on the operating system on which you are installing System Automation for Multiplatforms.

Starting the configuration

Execute the following initial configurations:

On all nodes, set and export the environment variable CT_MANAGEMENT_SCOPE to 2 (peer domain scope) for all users of System Automation for Multiplatforms : export CT_MANAGEMENT_SCOPE=2

To permanently set the variable, set and export it in the profile.

On SLES systems, you can create scripts in /etc/profile.d with the following content:
```
sa_mp.sh:
export CT_MANAGEMENT_SCOPE=2
sap_mp.csh :
setenv CT_MANAGEMENT_SCOPE 2
```
Make sure that the environment variable LANG is set to one of the supported locales for the root user. To set the environment variable, use the command:
```
export LANG=xx_XX
```
xx_XX denotes one of the supported languages.

For a list of supported languages and locales, see Supported languages and locales.

Load on nodes

System Automation for Multiplatforms requires some of its subsystems to be processed constantly on the node to ensure that the cluster services are working properly (for example, heartbeat and communication between the subsystems). If this is not possible, System Automation might trigger critical resource protection methods in case those subsystems cannot communicate within a short period of time. This protection mechanism eventually leads to a restart of the node on which this issue occurs.

To prevent an unwanted system restart, constant I/O and swap load must be lower than 10%.

For more information about critical resource protection methods, see Tivoli System Automation for Multiplatforms Administrator's and User's Guide.

Number of nodes in a cluster

Linux®: The maximum number of nodes in a cluster is 32.
AIX®: The maximum number of nodes in a cluster is 130.

Note:

The software packages must be available on the nodes on which you want to install System Automation for Multiplatforms. For example, you can mount the DVD on a PC and use FTP to transfer the files to the node, or you can install the packages over a shared Network File System.
To be sure that the software packages are installed and uninstalled correctly, use the System Automation for Multiplatforms scripts installSAM and uninstallSAM. They also perform requirements checking, license installation and migration tasks.
With the exception of the language packages, all packages are required for System Automation to work. Starting with System Automation for Multiplatforms 4.1 it is no longer possible to uninstall the RSCT package rsct.opt.storagerm without uninstalling the entire product.