Channels and Destinations : Destination Resource Reference

Destination Resource Reference
Within each channel, destinations direct incoming and outgoing information. A channel resource is not ready to use until it has at least one destination.
The Destinations section of a channel has the following fields.
The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. See Identifiers (Names).
Serializer/
Deserializer
Specify a serializer class to convert messages to simple events and simple events to messages. See the following sections for details:
RVCM Pre Registration
For TIBCO Rendezvous certified message publishers, specify pre-registered listener names as a comma separated list.
How you want the Rendezvous listener to behave when it receives more messages than the MaxEvents limit. Choose one of:
Discard_None (default)
When MaxEvents or DiscardAmount are zero (unlimited), the LimitPolicy must be Discard_None.
The number of events to discard when the queue exceeds its maximum event limit.
Specifies whether the destination is a queue or a topic. Check the checkbox if the destination is a queue. If the destination is a topic, do not check it.
Required. The name of the queue or topic. (If no name is specified, BusinessEvents Studio does not create a JMS destination.)
Specifies a filter to pick up messages from the destination. This is a standard JMS selector based on SQL92 semantics.
The delivery mode property instructs the server concerning persistent storage for the message. Select one of the following:
PERSISTENT (default)—In JMS message headers this is represented by the code 2.
NON-PERSISTENT—In JMS message headers this is represented by the code 1.
RELIABLE— This value is an extension to the standard, used in TIBCO Enterprise Message Service. In message headers this is represented by the code 22.
You can also set an acknowledgement mode in a node’s engine properties. The setting in the destination overrides the engine property setting.
Default is EXPLICIT_CLIENT_ACKNOWLEDGE
The message priority. Takes a numerical value between 0 and 9. Larger numbers represent higher priority.
The length of time that the message will live (in milliseconds) before expiration. If set to 0, the message does not expire.
Durable
Subscriber
Name
For destinations that are JMS Topics, if you provide a DurableSubscriber Name, the destination becomes a JMS durable topic subscriber with the specified name. If you do not provide a value, the destination becomes a non-durable topic subscriber.
The value of this property can be any unique string and can include any global variables. BusinessEvents provides a set of case-sensitive variables that produce a unique DurableSubscriberName string. See Creating Unique JMS DurableSubscriber Name Properties for details.
Default is: %%EngineName%%:%%SessionName%%:%%ChannelURI%%:%%DestinationName%%
The maximum number of events to be held in the queue. The default is zero (0), which allows unlimited events in the queue.
-1  Waits indefinitely
 0  Does not wait
>0  Waits for the number of milliseconds specified