TIBCO EMS STEP-5 :Destination Features

-

Ø  EMS Destination Features :
o   Set a secure mode for access control at the queue or topic level, so that some destinations may require permission and others may not.
o   Set threshold limits for the amount of memory used by the EMS server to store messages for a topic or a queue and fine-tune the server’s response to when the threshold is exceeded.
o   Route messages sent to destinations to other servers.
o   Create bridges between destinations of the same or different types to create a hybrid messaging model for your application. This can be useful if your application requires that you send the same message to both a topic and a queue.
o   Control the flow of messages to a destination. This is useful when message producers send messages much faster than message consumers can receive them. For more information on flow control.
o   Exchange messages with other message services, such as TIBCO FTL, TIBCO Rendezvous, and TIBCO Smart Sockets. Queues can receive messages from any of these services. Topics can either receive or send messages.
o   Set queues to be exclusive or non-exclusive. Only one receiver can receive msg from an exclusive queue. More than one receiver can receive msg from non-exclusive queues.
o   Specify a redelivery policy for queues. When messages must be redelivered, you can specify a property on the queue that determines the maximum number of times a message should be redelivered.
o   Trace and log all messages passing through a destination
o   Include the user name of the message producer in the message.
o   Administrator operations can use wildcards in destination names. The wildcard destination name is the parent, and any names that match the wildcard destination name inherit the properties of the parent.
o   Use the store property to cause messages sent to a destination to be written to a store file. Set the destination store to store=$sys.failsafe to direct the
o   Server to write messages to the file synchronously and guarantee that messages are not lost under any circumstances.
o   Specify that a consumer is to receive batches of messages in the background to improve performance. Alternatively, you can specify that queue receivers are to only receive one message at a time.

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