JMS Channels : Creating Unique JMS DurableSubscriber Name Properties

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 where more than one agent instance is active at a time. Instead, use queue destinations.
The value of the DurableSubscriber Name property can be any unique string and can include any global variables. 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 BusinessEvents. See Table 14, Variables for Use with DurableSubscriberName, for details.
Do not attempt to use %%EngineName%%, %%SessionName%%, %%ChannelURI%%, or %%DestinationURI%% in any area of BusinessEvents software except the DurableSubscriberName property.
 
The name of the BusinessEvents engine. The name used is established using a series of checks. See Appendix B, Determining the Engine Name in TIBCO BusinessEvents Administration for details.
The name of the agent class that is associated with the durable subscriber. Agent classes are defined in the CDD resource. See TIBCO BusinessEvents Administration for details about CDD configuration.
/folder/.../channel_name