Running Business Processes and Composite Applications 10.5 | Running Business Processes and Composite Applications | Universal Messaging Administration Guide | Using Command Central to Manage Universal Messaging | Universal Messaging and the Command Line Interface | Cluster Configuration Commands | Before You Create or Update a Universal Messaging Cluster
 
Before You Create or Update a Universal Messaging Cluster
*Make sure the server instances that you want to add to the cluster are running.
*Verify that the permissions on the server machines allow connections to the other servers in the cluster.
*Make sure the /naming/defaultContext channel exists only on one or none of the nodes that will form the cluster. The Universal Messaging server instance used as a JNDI provider uses the /naming/defaultContext channel to store JMS references and JNDI objects. If the channel exists on multiple nodes, you cannot create the cluster.
*If you have created custom composite templates for Command Central 9.9 or earlier, ensure that you remove the Universal Messaging server instance name suffix from COMMON-CLUSTER configuration type in the composite template when applying the composite template in Command Central 9.10 or later. For example:
In Command Central 9.9 and earlier:
um-cluster:
description: Cluster configuration for two UM instances
products:
NUMRealmServer:
${node.host}:
instance.port: ${um.instance.port}
instance.ip: ${um.host}
runtimeComponentId: Universal-Messaging-${instance.name}
configuration:
Universal-Messaging-${instance.name}:
COMMON-CLUSTER:
COMMON-CLUSTER-${instance.name}: &umClusterConfig
Name: ${um.cluster}
Servers: # two UM instances cluster
Server:
-
"@name": ${um.host}
URL: "nsp://${um.host}:${um.instance.port}"
-
"@name": ${um.host2}
URL: "nsp://${um.host2}:${um.instance.port2}"
In Command Central 9.10 and later:
um-cluster:
description: Cluster configuration for two UM instances
products:
NUMRealmServer:
${node.host}:
instance.port: ${um.instance.port}
instance.ip: ${um.host}
runtimeComponentId: Universal-Messaging-${instance.name}
configuration:
Universal-Messaging-${instance.name}:
COMMON-CLUSTER:
COMMON-CLUSTER: &umClusterConfig
Name: ${um.cluster}
Servers: # two UM instances cluster
Server:
-
"@name": ${um.host}
URL: "nsp://${um.host}:${um.instance.port}"
-
"@name": ${um.host2}
URL: "nsp://${um.host2}:${um.instance.port2}"

Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.