Destination(Queues & Topics) Properties-1

Destination properties are properties that can be applied to queues and/or topics that describe specific behavior of the destination. Each property is described in short and please refer the EMS documentation for deeper understanding.

1. Failsafe: For Both Queue and Topic

TIBCO Enterprise Message Service provides two modes for persisting topic/queue messages in external storage. These two modes are:

• normal
• failsafe

In Normal mode all persistent messages are written to the storage in an asynchronous mode, ie data may be in the system buffers for a short duration before written to the disk.

Whereas in failsafe mode, data is not retained in the buffers and written to the disk synchronously. This ensures that in case of any software or hardware failure data is not lost.

In situations where loss of data is not acceptable, use failsafe. One should keep in mind that failsafe mode is a performance hit and should analyze and carefully use this property based on the need.

2. secure: Both for Queue and Topic

The secure property, when set on a destination, specifies permissions should be checked for that destination. When a topic or a queue does not have the secure property turned on, any authenticated user can perform any actions with that topic or queue. When the property is turned on, the administrator can assign permissions to the users. For this property to work, the authorization property must also be enables at the server level configuration file.

Note:The remaining Properties of Destinations will be posted in coming days, Please check for this blog updates daily to keep in touch.

Read more...

TIBCO EMS Destinations:Queues & Topics

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.

Static Queues and Topics
Static Queues and topics are administered by the server. The configuration information is stored in the configuration files for the Tibco EMS server, which is located in TIBCO_HOME/ems/bin folder. The files are queues.conf and topics.conf. 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 or you can use the administration tool. An EMS Client retrieves the destination information from the JNDI.

Dynamic Queues and Topics
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.

Temporary Queues and Topics
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.

To read Properties of destinations ClickHere

Read more...