Various JMS Queues Used By OIM

OIM versions prior to 9.1 were using a 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 were using a single JMS queue, every aforementioned operations used to depend on each other. 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.

 

Below are the details of the JMS queues used by OIM:

 

xlQueue

This queue is used to handle request (self registration and approval) related operations.

 

xlReconQueue

This queue is used to handle Reconciliation.

 

xlAuditQueue

This queue is used to handle Auditing.

 

xlAttestationQueue

This queue is used to handle Attestation.

 

xlProcessQueue

This queue is for future usage.

 

xlErrorQueue

This is the queue where the messages will end up after being tried 5 times.
For example, if the recon messages picked up by ReconMDBs fail during processing, they are tried for 5 times to process. If they still fail then the messages will be sent to this error queue.