Destinations for messages can be either Topics or Queues. A destination can be created statically in the server configuration files, or dynamically by a client application.
Configuration information for static queues and topics is stored in configuration files for the TIBCO Enterprise Message Service server. Changes to the configuration information can be made in a variety of ways. To manage static destinations, you can edit the configuration files using a text editor, you can use the administration tool, or you can use the administration APIs.
Static queues and topics are administered by the server. Clients retrieve the destination using JNDI. For example, the following code retrieves the InitialContext using the JNDI properties specified by env
, then looks up a Topic named MyTopic
.
See Using JNDI with TIBCO Enterprise Message Service for more information about using JNDI with TIBCO Enterprise Message Service.
Dynamic queues and topics are created on-the-fly by applications using QueueSession.createQueue()
and TopicSession.createTopic()
. Dynamic queues and topics do not appear in the configuration files, and exist as long as there are messages or consumers on the destination. A client cannot use JNDI to lookup dynamic queues and topics.
When you use the show queues
or show topics
command in the administration tool, you see both static and dynamic topics and queues. The dynamic topics and queues have an asterisk (*
) in front of their name in the list of topics or queues.
Dynamic queues and topics inherit properties from their respective parents. When shown by the administration tool, properties of a queue or topic may have an asterisk (*
) character in front of its name. This means that this property was inherited from the parent queue or topic and cannot be changed. For more information, refer to Inheritance of Properties and Wildcards * and >.
TIBCO Enterprise Message Service supports temporary queues and topics as defined in JMS specification 1.1 and its API.
Servers connected by routes exchange messages sent to temporary topics. As a result, temporary topics are ideal destinations for reply messages in request/reply interactions.
For more information on temporary queues and topics, refer to the JMS documentation described in Third Party Documentation.
You can create server-based bridges between destinations. This allows all messages delivered to one destination to also be delivered to the bridged destination. You can bridge between different destination types, between the same destination type, or to more than one destination. For example, you can create a bridge between a topic and a queue or from a topic to another topic.
See Destination Bridges for more information about destination bridging.
TIBCO Enterprise Message Service™ User’s Guide Software Release 4.3, February 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |