timemsd connects to Rendezvous daemons in the same way as any other Rendezvous client would. Transport definitions (in the file
transports.conf) configure the behavior of these connections. You must properly configure these transports.
In order to limit the number of pending messages in Rendezvous queues, a transport property allows you to set a queue limit policy, as you would for TIBCO Rendezvous client applications. When the queue limit for the transport is reached, the Rendezvous library discards a set number of messages. The default policy is TIBRVQUEUE_DISCARD_NONE, which means that no message is ever discarded. Setting
TIBRVQUEUE_DISCARD_FIRST or
TIBRVQUEUE_DISCARD_LAST allows you to specify the maximum number of Rendezvous messages that can be pending in the queue before the discard policy that you have selected is applied. When the limit is reached, the number of messages discarded is based on the discard amount value.
transports.conf contains zero or more transport definitions. Each definition begins with the name of a transport, surrounded by square brackets. Subsequent lines set the parameters of the transport.
|
|
|
|
|
|
|
|
|
|
When absent, the default value is an rvd process on the local host computer. When transporting messages between EMS and Rendezvous, the rvd process must be configured to run on the same host as the EMS daemon ( tibemsd).
To connect to a non-default daemon, supply hostname:protocol:port. You may omit any of the three parts. The default hostname is the local host computer. The default protocol is tcp. The default port is 7500.
|
|
|
|
|
|
|
|
|
true or false. If true, operations that update the ledger do not return until changes are written to the storage medium.
|
|
true or false. If true, this transport server requests unacknowledged messages sent from other RVCM senders while this transport was unavailable.
|
|
|
|
true or false. If true, tibemsd allows RVCM listeners to register for certified delivery only if they are configured in advance with the EMS server (either in tibrvcm.conf or using the create rvcmlistener command). That is, tibemsd ignores registration requests from non-configured listeners.
If false (the default), tibemsd allows any RVCM listener to register.
|
|
|
EMS sending clients can set the JMSDeliveryMode header field for each message. However, Rendezvous clients cannot set this header. Instead, these two parameters determine the delivery modes for all topic messages and queue messages that tibemsd imports on this transport.
|
|
When true, tibemsd includes JMS header fields in exported messages.
When false, tibemsd suppresses JMS header fields in exported messages.
|
|
When true, tibemsd includes JMS properties in exported messages.
When false, tibemsd suppresses JMS properties in exported messages.
|
|
policy: max_msgs: qty_discard
where policy is one of the queue limit policies described below, max_msgs is the maximum number of messages permitted in the queue before discard, and qty_discard is the number of messages that the EMS server discards when max_msgs is reached.
•
|
TIBRVQUEUE_DISCARD_NONE — do not discard messages. Use this policy when the queue has no limit on the number of messages it can contain.
|
•
|
TIBRVQUEUE_DISCARD_FIRST — discard the first message in the queue. The first message in the queue is the oldest message, which if not discarded would be the next message dispatched from the queue.
|
•
|
TIBRVQUEUE_DISCARD_LAST — discard the last message in the queue. The last message is the most recent message received into the queue.
|
If the rv_queue_policy is not present, the default queue limit policy is TIBRVQUEUE_DISCARD_NONE.
|
|
|
These examples from transports.conf illustrate the syntax of transport definitions.
In the following two examples, RVCM03 is an RVCM transport which does not define a queue limit policy, but references the RV transport
RV03, which
does have a queue limit policy. If Rendezvous messages are published to a subject that in EMS has the destination property
import=RVCM03, no Rendezvous message will ever be discarded because each transport uses its own queue. Only messages that are imported directly through the
RV03 transport will potentially be discarded, should the queue limit of 10000 messages be reached.