Install Universal Messaging on Cluster Nodes
When you install Universal Messaging on cluster nodes, you must:
Follow the instructions in the
Using Software AG Installer guide.
Work with the cluster vendor's installation consultant to prepare the cluster node to respond to the virtual IP address and have access to the storage files on the shared storage.
To install
Universal Messaging on cluster nodes
1. Install Universal Messaging on the first cluster node and configure to use the shared storage and log file.
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, opt/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=opt/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=opt/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.
2. Unmount the shared storage from cluster node 1 and mount it on cluster node 2.
3. Make the first cluster node inactive.
4. Install Universal Messaging on the second cluster node and configure it to use the shared storage and log file, following the configuration instructions for the first cluster.
5. Make the second cluster node active so that it will respond to the virtual IP address and have access to the storage files on the shared storage.