Implementation Guide › Optimizing CA Identity Manager › Runtime Components Tuning › JMS Settings › JMS Messages and Performance

JMS Messages and Performance

For any event, there are four states that require JMS messages for state transition:

• BEGIN
• APPROVED
• EXECUTING
• COMPLETED

To process a single event, the following actions take place:

• Four posts to the Events Message Queue
• Four invocations of the Message Driven Bean
• Eight connections to the task persistence database (one read action and one write action per state)

Theses actions may impact the amount of time it takes CA Identity Manager to process a task.

To ensure best performance during state transitions, tune the JMS resources in the application server that hosts CA Identity Manager so that adequate JMS resources are available.