For many MIM operation options, there is a corresponding LBT-RM operation option. For more information on how MIM operation options interact and for illustrations, please see the introduction to the transport LBT-RM operation options section.
Note that the LBT-RM rate controller also governs MIM transmission rates. Hence there is no separate option for setting MIM transmission rate.
See also Multicast Immediate Messaging for more information about this feature.
Callback function (and associated event queue and client data pointer) called when a topic-less immediate message is received for which there is no receiver. A value of NULL for the callback prevents the callback from being called.
Callback function (and associated event queue and client data pointer) that is called when an immediate message is received for a topic for which there is no receiver. A value of NULL for the callback prevents the callback from being called.
For multicast immediate message receivers only. See transport_lbtrm_activity_timeout for description. However, multicast immediate message channels do not deliver an EOS indication.
The interval between activity checks of a Multicast Immediate Messaging delivery controller. Multiple MIM delivery controllers may exist to accommodate multiple messages from a single MIM sender received across more than one UM Gateway. These multiple delivery controllers allow for duplicate message detection.
The maximum time that a Multicast Immediate Messaging delivery controller may be quiescent before it is deleted. MIM delivery controllers may be created to accommodate multiple messages from a single MIM sender received across more than one UM Gateway. These multiple delivery controllers allow for duplicate message detection.
For multicast immediate messages with ordered delivery, this controls the size of the hash table used to hold data.
The maximum timeout between when the first message of an implicitly batched immediate message is queued until the batch is sent. A message will not stay in the queue longer than this value before being sent in the worse case.
The minimum length of an implicitly batched multicast immediate message. When the total length of the implicitly batched messages reaches or exceeds this value, the batch is sent.
For multicast immediate messages only. Indicates whether or not the MIM source should have its data delivered in order. The default value also guarantees fragmentation and reassembly of large messages. Changing this option from the default value results in large messages being delivered as individual fragments of less than 8K each, requiring the application to reassemble them. See also Ordered Delivery for more information about large message fragmentation and reassembly.
For multicast immediate message senders only. See transport_lbtrm_sm_maximum_interval for description.
For multicast immediate message senders only. See transport_lbtrm_sm_minimum_interval for description.
For multicast immediate message receivers only. Determines the increment by which the sequence number window is moved when detecting the receipt of duplicate multicast immediate messages. Must be a multiple of 8 and an even divisor of mim_sqn_window_size.
For multicast immediate message receivers only. Determines the window size used to detect the receipt of duplicate multicast immediate messages. Must be a multiple of 8.
The timeout after a multicast immediate message is sent before the internal source is deleted and cleaned up.
For multicast immediate message senders only. See transport_lbtrm_tgsz for description.
Callback function (and associated client data pointer) that is called when a MIM receiver has unrecoverable loss. This callback is called directly in line and does not use the event queue. Therefore the callback function used should not block or it will block the context thread processing. A value of NULL for the callback turns off the callback being called.
Copyright (c) 2004 - 2014 Informatica Corporation. All rights reserved.