This section discusses the following topics.
When using UMP stores or UMQ queues, UM objects such as sources, receivers, and/or contexts must register with the stores or queues, at which time they acquire registration IDs. You can use Session IDs to manage these registration IDs.
A UMP Session ID allows stores to identify an application's sources and receivers by automatically assigning them registration IDs. With session IDs, you do not need to directly assign registration IDs. You assign a UMP session ID by first setting option use_ump_session_ids to True, then assigning the session ID with the setClientID() method, or by setting the client_id option. Note that with this option enabled, UM ignores attempts to maintain registration IDs directly.
When using this option, we recommend that you call the setClientID() function after creating a Connection rather than setting the client_id option, to ensure that each created connection has a unique client identifier .
For more information about UMP registration IDs and session IDs, see Registration Identifiers, and more specifically, Managing RegIDs with Session IDs.
You can use UMQ Session IDs to manage context registration IDs and receiver assignment IDs. For expanded information on UMQ Session IDs, see Queue Session IDs.
In configurations where a queue must always send messages, in order, to a specific assigned receiver, use UMQ Session IDs, as described in the next paragraphs. This ensures that if a receiver fails, the queue retains messages for that receiver until it recovers.
To configure this scenario, perform the following steps:
Set option message-reassignment-timeout (see Options for a Topic's ume-attributes Element) for the queue to a value of 0.
Set option umq_session_id to a unique value. Do not replicate this value elsewhere, even for sending applications.
Copyright (c) 2004 - 2014 Informatica Corporation. All rights reserved.