Universal Messaging Clustering Requirements

In Universal Messaging, a cluster is defined as multiple server instances in Universal Messaging installations that are configured for clustering.

This section is intended for use with the upgrade procedure for this product as explained elsewhere in this guide. You must perform all documented tasks for your products in the order they are written in that procedure, with the additional tasks or exceptions noted below.

When you install the new Universal Messaging servers instances, create a cluster that matches your old cluster. You can install the new Universal Messaging server instances in parallel.

When you install the latest fixes on the new Universal Messaging server instances, you can install the fixes in parallel.

When you migrate server instances from old Universal Messaging installations to new Universal Messaging installations, you can migrate the instances in parallel.

If the new cluster nodes are on the same host machines as the old cluster nodes, start all new cluster nodes.

If the new cluster nodes are on different machines than the old cluster nodes, follow the steps below. In those steps, If you are not using a remote join or a zone, "nodes" refers to nodes that are part of the cluster. If you are using a remote join or zone, "nodes" refers to nodes that are part of the remote join or zone.

1. Go to the new_Software AG_directory/UniversalMessaging/server/instance_name/bin directory for one node and create a file named remote_realms_bootstrap.conf. Add a cross-host mapping property to the file for every node using the format instance_name.address=new_host_name_or_IP_address (for example, umserver1.address=myUM1.com or umserver2.address=192.168.0.1). Copy the file to the same location for all nodes.

2. Start all nodes. The remote_realms_bootstrap.conf file in every installation will be renamed remote_realms_bootstrap_old.conf. When a source Universal Messaging server instance is bound to a specific network interface (absolute IP address), the interface of the migrated instance address will bind to 0.0.0.0 (all known interfaces on the port).