TIBCO EMS STEP -7 :EMS Message Properties

-

EMS Message Properties
Ø  TIBCO-specific property names begin with JMS_TIBCO.
Ø  Client programs may use the TIBCO-specific properties to access EMS features, but not for communicating application-specific information among client programs.
§  JMS_TIBCO_CM_PUBLISHER is used for Correspondent name of an RVCM sender for messages imported from TIBCO Rendezvous.
§  JMS_TIBCO_CM_SEQUENCE Sequence number of an RVCM message imported from TIBCO Rendezvous.
§  JMS_TIBCO_COMPRESS Allows messages to be compressed for more efficient storage.
§  JMS_TIBCO_DISABLE_SENDER Specifies that the user name of the message sender should not be included in the message, if possible.
§  JMS_TIBCO_IMPORTED Set by the server when the message has been imported from TIBCO FTL, Rendezvous,or SmartSockets.
§  JMS_TIBCO_MSG_EXT Extends the functionality of the MapMessage and StreamMessage body types to include submessages or arrays.
§  JMS_TIBCO_MSG_TRACE Specifies the message should be traced from producer to consumer.
§  JMS_TIBCO_PRESERVE_UNDELIVERED Specifies the message is to be placed on the undelivered message queue if the message must be removed.
§  JMS_TIBCO_SENDER Contains the user name of the message sender.
§  JMS_TIBCO_SS_SENDER When the EMS server imports a message from TIBCO SmartSockets, it sets this property to the SmartSockets sender header field (in SmartSockets syntax).
Ø  Undelivered Message Queue : If a message expires or has exceeded the value specified by the maxRedelivery property on a queue, the server checks the message’s JMS_TIBCO_PRESERVE_UNDELIVERED property. If this property is set to true, the server moves the message to the undelivered message queue, $sys.undelivered otherwise the message will be deleted by the server.
Ø  This undelivered message($sys.undelivered) queue is a system queue that is always present and cannot be deleted.
For using undelivered message queue, application that sends/publishes the message must set the boolean JMS_TIBCO_PRESERVE_UNDELIVERED
property to true before sending or publishing the message.
Ø  We can only set the undelivered property on individual messages.
Ø  There is no way to set the undelivered message queue as an option at the per-topic or per-queue level.
Ø  $sys.undelivered ignores the global destination property setting.
Ø  Messages in the undelivered message queue are not routed to other servers.

Comments

Post a Comment

Popular posts from this blog

TIBCO EMS FAQ -5

-
131) What happens if the message expires/exceeded the value specified by maxredelivery property on queue? If the jms_preserve_undelivered property is set to true, then it moves he message to undelivered message queue, if set to false, the message is deleted by the server. 132) What are the wild cards that we use in ems?how do they work for queues and topics? *,> We can subscribe to wildcard topics, but cant publish to them. Where as in case of queues we can’t either send /receive. 133) Are bridges transitive? No 134) Tell me about flow control on destinations? Sometimes the producer may send messages faster than the consumers can receive them. So, the message capacity on the server will be exhausted. So we use flow control. Flow control can be specified on destinations. 135) Tell me about flow control on bridges and routes? Flow control has to be specified on both sides of bridges where as on routes it operates differently on sender side and receiver side. 136) Nam...
Read more

TIBCO EMS FAQ -4

-
101) What are the permissions that you can grant to users to access topics? a. Subscribe b. Publish c. Durable d. Use durable 102) What is the difference between Queues and Topics? Queue • Guaranteed Service • Only the Target gets the message (One message per Consumer) • Uses Peer-to-Peer Mode to deliver messages • Blocking • Load Balancing is possible Topic • Reliable Service • Everyone active gets the message (One message may Consumers) • Uses Pub / Sub mode to deliver messages • Non-Blocking • Load Balancing is not possible. 103) What is the use of secured queues and topics? Setting ‘secure’ property to queues/topics can restrict unauthorized users from publishing/sending and subscribing/receiving the messages. 104) What are acknowledgement modes and where do you set them and what is the applicability of each mode? Ans:The acknowledge mode for incoming messages. Can be one of the following: • Auto — the message is automatically acknowledged when it is re...
Read more

TIBCO BW FAQ -2

-
31) What happens if you use check point activity first and confirm next? Ans)In the case of confirmable messages , you must consider the consequences of performing a checkpoint before or after a Confirm activity. If the checkpoint is taken before the Confirm activity, then a crash occurs after a checkpoint but before a confirm, the original message is resent. In this case, the restarted process can no longer send the confirmation. However, a new process is started to handle the resent message, and you can implement your process to handle the restarted and new processes appropriately. If the checkpoint is taken after a Confirm activity, there is potential for a crash to occur after the Confirm but before the checkpoint. In this case, the message is confirmed and therefore not redelivered. The process instance is not restarted, because the crash occurred before the checkpoint. You must consider the type of processing your process definition performs to determine when a checkpoint i...
Read more