Starting correlators that use Universal Messaging
Note: | The information in this topic is deprecated. It applies to the old Universal Messaging integration which will be removed in a future release. It is recommended that you use the new Universal Messaging connectivity plug-in. |
For a correlator to use Universal Messaging, you must specify one of the following options when you start the correlator:
--rnames list Specifies one or more Universal Messaging realm names (RNAME) separated by commas or semicolons.
Commas indicate that you want the correlator to try to connect to the Universal Messaging realms in the order in which you specify them here. For example, if you have a preferred local server you could specify its associated RNAME first and then use commas as separators between specifications of other RNAMEs, which would be connected to if the local server is down.
Semicolons indicate that the correlator can try to connect to the specified Universal Messaging realms in any order. For example, use semicolons when you have a cluster of equally powered machines in the same location and you want to load balance a large number of clients.
You can specify multiple Universal Messaging realms only when they are connected in a single Universal Messaging cluster. That is, all RNAMEs you specify must belong to the same Universal Messaging cluster. Since channels are shared across a cluster, connecting to more than one Universal Messaging realm lets you take advantage of Universal Messaging's failover capability.
You can specify -r in place of --rnames.
--umConfigFile path You can specify -UMconfig in place of --umConfigFile.