Creating Unique JMS DurableSubscriber Name Properties
For destinations that are JMS Topics, if you provide a
DurableSubscriber Name
when you configure the destination resource, the destination becomes a JMS durable topic subscriber with the specified name. This section explains how you can ensure that the
DurableSubscriber Name
value is unique.
- When using topic destination with a durable name in applications using In Memory OM and fault tolerance, do not provide a value for the Client ID setting and do not check the Auto-generate Client ID check box in the JMS shared resource.
- Do not use durable topic destinations for multi-agent applications, even when only one agent instance is active at a time (that is, even when is set to 1). Instead, use queue destinations.
The value of the
DurableSubscriber Name
property can be any unique string and can include any global variables. TIBCO BusinessEvents provides a set of case-variables that produce a unique
DurableSubscriberName
string:
%%Deployment%%:%%EngineName%%:%%SessionName%%:%%ChannelURI%%:%%DestinationName%%
The first variable
%%Deployment%% is a standard TIBCO global variable. The other three are only for use with the
DurableSubscriberName
property within TIBCO BusinessEvents. For details see
Variables to Use with DurableSubscriberName.