Reconnecting a Cluster Node After Updating Its Host Name or IP Address

About this task

If the hostname or IP address for a cluster node gets updated, you must reconnect the nodes in the cluster as described in the following steps. Note that if you are not using a remote join or zone, node in the following steps refers to a node that is part of the cluster. If you are using a remote join or zone, node refers to a node that is part of the remote join or zone.

Procedure

  1. In a text editor, create a file with name remote_realms_bootstrap.conf and save the file in the new_Software AG_directory/UniversalMessaging/server/instance_name/bin directory.
  2. In the remote_realms_bootstrap.conf file, add a cross-host mapping property for each node within the cluster in the following format:
    instance_name.address=new_host_name_or_IP_address

    For example, umserver1.address=myUM1.com or umserver2.address=192.168.0.1.

  3. Copy the file to the new_Software AG_directory/UniversalMessaging/server/instance_name/bin directory for each cluster node.
  4. Start all nodes within the cluster.
    At startup the Universal Messaging server reads the remote_realms_bootstrap.conf file and updates its internal server data with the new file entries. After the Universal Messaging server completes the reading of the file, it renames the file to remote_realms_bootstrap_old.conf.

What to do next

To verify that the nodes in the cluster connect successfully, open Enterprise Manager and check if the cluster is running.