Avoiding REGISTRATION COLLISION RVCM Advisory Messages

REGISTRATION COLLISION RVCM Advisory Messages should be avoided.

When you are configuring RVCM using a Rendezvous transport shared resource, an advisory message named REGISTRATION.COLLISION RVCM can be thrown if the same CM name (or CMQ name) is used on all engines.

To prevent name collisions that can result in thrashing, you must ensure that the CM names (and CMQ names) are different on all engines. To do so, add global variables to the CM Name or CMQ Name, and to the ledger file name if a ledger file is used for RVCM, to ensure the uniqueness of these names. Add one or more of the following variables, depending on need (as explained below):

%%EngineName%%
%%ChannelName%%
%%ChannelURI%%

The %%EngineName%% variable is generally required for all names. You must start engines using unique names so that the value of each engine's %%EngineName%%variable be different at runtime.

In addition, if different channels use the same RVCM shared resource, you also need to add %%ChannelName%% or %%ChannelURI%%. Use %%ChannelURI%% in cases where channels using the same RVCM shared resource have the same name but are in different folders.

You must define any of the above String type global variables you use. They are not predefined. However, TIBCO BusinessEvents provides the value at runtime, so you can use any string value or use an empty string as the value when you define the variables.