TIBCO EMS Destination Types and Properties Overview

---

Before moving on to post, Follow this link to get an overview on JMS Message Models.

  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.

  Destinations Overview Types : Static Creates by EMS Administrators. Dynamic Creates by the application, lasts till the EMS server is restarted. Temporary Creates by the applicaiton, lasts till the client application disconnects from the server. Properties :    Properties can be assigned to either Topics or Queues. You can set proeprties directly in the topics.conf or queues.conf or by using setprop topic or setprop queue command in the EMS Administration Tool. Refer to this post to create and modify destination properties Refer to this post for list of useful Administrator Tool commands Below table describes about each property : channel Determines the multicast channel over which messages sent to this topic are braodcast. global Allows destinations to participate in routing. exclusive Set for only queues, the server sends all messages on that queue to one consumer. export Messages published by a client to a topic to be exported to the external systems with configured transport. import Messages published by an external system to be received by a EMS destination. Ex: import = "RV1,RV2" expiration Message expiration value. Ex: expiration = 10 [msec|sec|min|hour|day] flowControl Max pending messages size for the destination. Ex: flowControl = 10 [KB|MB|GB], If it exceeds then it slows the process but doesn't throw an error. maxbytes Maximum size that the queue can store. EX : maxbytes = 10 [KB|MB|GB], If it exceeds then it throws an error. maxmsgs Maximum number of messages that can be waiting in a queue. If it exceeds then it throws an error. overflowPolicy To change the effect of exceeding the message capacity established by either maxbytes or maxmsgs. Ex : overflowPolicy = default|discardOld|rejectIncoming prefetch The message consumer automatically fetches messages from the server. Ex: prefetch = 4, Default prefetch values, for queues=5, Topics=64 maxRedelivery The number of attempts the server should make to deliver a message sent to a queue. redeliveryDelay The EMS server waits the specified interval before returning an unacknowledged message to the queue. secure It instructs the EMS server to check the user permissions. sender_name Server may include the sender's username for messages sent to this destination. sender_name_enforced Messages sent to destination must include the sender's username. store Determines where messages sent to destination are stored. trace To trace the messages sent on destination. Ex : trace = [body] -- it includes message body along with msg sequence, msg ID and msg size.

---