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.
TIBCO Rendezvous Destinations Configuration Properties
See TIBCO Rendezvous documentation for more details on these settings.
Field | Global Var? | Description |
---|---|---|
Subject | Yes | The TIBCO Rendezvous subject for incoming and outgoing messages. |
RVCM Pre Registration | Yes | For TIBCO Rendezvous certified message publishers, specify pre-registered listener names as a comma separated list. |
LimitPolicy | Yes | How you want the Rendezvous listener to behave when it receives more messages than the MaxEvents limit. Choose one of:
Discard_None (default) Discard_First Discard_Last Discard_New When MaxEvents or DiscardAmount are zero (unlimited), the LimitPolicy must be Discard_None. |
MaxEvents | No | Maximum number of message events that the queue can hold.
The default value, zero (0), means an unlimited number of events. |
DiscardAmount | No | The number of events to discard when the queue exceeds its maximum event limit.
The default value, zero (0) means events are never discarded. |
JMS Destinations Configuration Properties
See TIBCO Enterprise Message Service documentation for more detail on these settings.
Field | Global Var? | Description |
---|---|---|
Queue | Yes | Specifies whether the destination is a queue or a topic. Select the check box if the destination is a queue. If the destination is a topic, do not select it. |
Name | Yes | Required. The name of the queue or topic.
TIBCO BusinessEvents ignores JMS destinations with null or empty-string queue or topic names. It logs an error message for the ignored destinations. If a JMS message is sent out through an ignored destination, TIBCO BusinessEvents throws an exception and the message is not sent out. TIBCO BusinessEvents also does not receive JMS messages (events) through these ignored destinations. |
Selector | Yes | Specifies a filter to pick up messages from the destination. This is a standard JMS selector based on SQL92 semantics. |
DeliveryMode | No | The delivery mode property instructs the server concerning persistent storage for the message. Select one of the following:
You can also set a delivery mode in an event. |
AckMode | Yes | The acknowledgement mode. See
JMS Message Acknowledgement Modes for more details on the various modes.
The default value is EXPLICIT_CLIENT_ACKNOWLEDGE. |
Priority | No | The message priority. Takes a numerical value between 0 and 9. Larger numbers represent higher priority.
You can also set a priority in an event. The default value is 4. |
TTL | Yes | The length of time that the message will live (in milliseconds) before expiration. If set to 0, the message does not expire.
You can also set a TTL (JMSExpiration) in an event. The default value is 0. |
Durable Subscriber Name | Yes | 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. TIBCO BusinessEvents provides a set of case-sensitive variables that produce a unique DurableSubscriberName string. The default value is: %%EngineName%%:%%SessionName%%:%%ChannelURI%%:%%DestinationName%%. |
Local Destinations Configuration Properties
Local destinations do not use serializers, deserializers, or default events.
HTTP Destinations Configuration Properties
Field | Global Var? | Description |
---|---|---|
Is JSON Payload | No | Specifies whether payload is JSON |
Is Page Flow | No | Enables Action Rule Function based approach. If selected, the system disables the Default Event and Serializer/Deserializer fields for input. |
ContextPath | No | Context URI for the web application. The field is active for input if the Is Page Flow check box is selected. |
Action Rule Function | No | The Action Rule function to be executed when an HTTP message arrives at the context URI for the web application. The field is active for input if the Is Page Flow check box is selected. |