This chapter explains how to customize Managed Server transactions.
Note
The environment of all nodes must be the same.
In case of n:1 standby operation, the secondary node environment may already have been set up earlier.
In such a case, set up the environment for the primary node in the same way as it is on the secondary node.
Each execution of the Managed Server transaction creates the settings for one cluster transaction. To build a mutual standby system, execute the procedure for customizing as many times as necessary.
Before starting customization, add to an existing cluster transaction or decide whether to create a new cluster transaction.
Do not move the resource used by Managed Server transactions from a cluster transaction after setup to another cluster transaction.
The following table shows the references to use for information concerning customization methods:
Cluster software | Reference |
|---|---|
Solaris version of SynfinityCluster /PRIMECLUSTER | A.2 Customization for Solaris/Linux/HP-UX version clustered system |
Solaris version of VERITAS Cluster Server | A.2 Customization for Solaris/Linux/HP-UX version clustered system |
Solaris version of Sun Cluster | A.2 Customization for Solaris/Linux/HP-UX version clustered system |
Windows version of MSCS/WSFC | |
HP-UX version of MC/ServiceGuard | A.2 Customization for Solaris/Linux/HP-UX version clustered system |
HP-UX version of VERITAS Cluster Server | A.2 Customization for Solaris/Linux/HP-UX version clustered system |
AIX version of VERITAS Cluster Server | |
AIX version of High Availability Cluster Multi-Processing | 8.3 Customization for AIX version High Availability Cluster Multi-Processing |
Linux version clustered system | A.2 Customization for Solaris/Linux/HP-UX version clustered system |
