Information On Various JMS Queues Used By OIM
(Doc ID 1107963.1)
Last updated on AUGUST 10, 2021
Identity Manager Information in this document applies to any platform.
Checked for Relevance 20-Apr-2012
OIM versions prior to 9.1 used single JMS queue named xlQueue for all the asynchronous operation like user requests (self registration and approval), reconciliation, attestation and auditing. Because all the process was using single JMS queue, every above said operations depends on one another. For example when reconciliation was running the queue xlQueue is filled with messages for reconciliation and request processing needs to wait till all the reconciliation was done. This was creating inter dependency between the modules of the application.
From OIM version 9.1 onwards separate JMS queues for each asynchronous functionality were introduced. This FAQ describes the purpose of each queue.
Questions and Answers
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!