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

JMS Messages and Performance

For any event, there are three to five states that require JMS messages for state transition:

• BEGIN
• PENDING (only under Workflow control)
• APPROVED or REJECTED
• EXECUTING
• COMPLETED or INVALID

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

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

These actions may impact the amount of time it takes CA IdentityMinder to process a task.

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