Within each channel, destinations direct incoming and outgoing information. A channel resource is not ready to use until it has at least one destination.
Global Var? 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). The event to be created from incoming messages unless otherwise specified. As a convenience, you can open the selected event resource by clicking the underlined label.Optional, but only if you always specify an event type in the incoming message. Serializer/
Deserializer Specify a serializer class to convert messages to simple events and simple events to messages. See the following sections for details: The TIBCO Rendezvous subject for incoming and outgoing messages. 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. Maximum number of message events that the queue can hold.The default value, zero (0) means an unlimited number of events. The number of events to discard when the queue exceeds its maximum event limit.The default value, zero (0) means events are never discarded. 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. (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.) 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. The acknowledgement mode. See Changing the JMS Message Acknowledgment Mode for a table explaining the various modes.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.You can also set a TTL (JMSExpiration) in an event. See Using JMS Header Properties in Incoming and Outgoing Messages. 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. TIBCO BusinessEvents provides a set of case-sensitive variables that produce a unique DurableSubscriberName string. See Creating Unique JMS DurableSubscriber Name Properties for details. The maximum number of events to be held in the queue. The default is zero (0), which allows unlimited events in the queue. Time to wait when sending an event to this local destination:Default is -1.
Copyright © TIBCO Software Inc. All Rights Reserved.