Active/Passive Cluster Configuration on Windows Server
Perform the following steps to configure Universal Messaging for high availability.
1. Mount and configure the shared drive, and add the shared drive to the cluster. For more information about adding and configuring a shared drive, see the Microsoft Server documentation for your Microsoft Server version.
2. Install Universal Messaging on the cluster nodes.
Use the same directory name on all cluster nodes. Ensure that the data directory paths for the shared storage and the log file are the same in all the installations (for example, C:\SoftwareAG_UM).
The data directory path in the Server_Common.conf configuration files must correctly refer to the same shared storage path. For example, the data directory path in all the nodes is specified as wrapper.java.additional.4="-DDATADIR=H:\UMSharedStorage\Data".
The log file path in the Server_Common.conf configuration files must correctly refer to the same shared log directory path. For example, the log file path in all the nodes is specified as wrapper.java.additional.22="-DLOGFILE=H:\UMSharedStorage\Data\nirvana.log".
If you are using the Software AG default internal user repository, ensure the user database file is located in the shared location. By default, the location is Universal Messaging_directory /common/conf/users.txt. The user database file is defined in the jaas.conf configuration file:
{com.softwareag.security.jaas.login.internal.InternalLoginModule sufficient
template_section=INTERNAL internalRepository="../../../../common/conf/users.txt";}
Note:
If you want to make changes that are automatically migrated in a future upgrade/migration, set the corresponding properties in the
Custom_Server_Common.conf file as described in the section
JVM Options.
3. Create the Universal Messaging cluster in Windows Server. See the Microsoft Server documentation for instructions to create a failover cluster.
4. Create the Universal Messaging cluster group. Define all the resources and dependencies required to run Universal Messaging.
5. Configure Universal Messaging as a clustered service.
You can run Universal Messaging as a service or an application.
6. Customize the Universal Messaging startup behavior. For instructions to configure the startup behavior, see the relevant Microsoft Server documentation.
You can configure the number of possible attempts for starting the Universal Messaging server before failover.
7. Verify failover in the cluster using Windows Server tools.
You or a system administrator can verify failover when there is a hardware failure.
8. Ensure that the installation and configuration enables the Universal Messaging server to failover correctly from one cluster node to the other.