Implementation Guide › Optimizing CA IdentityMinder › Runtime Components Tuning › JMS Settings › How JMS Messages Drive Event Transitions

How JMS Messages Drive Event Transitions

CA IdentityMinder uses JMS messages to drive an event’s state transitions. The following procedure describes the steps involved:

1. A user submits a task.
2. The task generates one or more events.
3. When an event is ready for processing, CA IdentityMinder sets the event's state to BEGIN and the event is persisted in the task persistence database.
4. CA IdentityMinder creates a JMS message containing the event ID and posts that message to the Event Message Queue.
5. Upon receiving the message, JMS then invokes an instance of the Event Message Driven Bean, which is an implementation of the Event Controller.
6. The Event Controller uses the event ID in the message to retrieve the event from the task persistence database, and executes the actions for the event’s current state.
7. Upon completion of that state, the event is set to the next state, persisted in the task persistence database, and a new JMS message is posted for processing the next state.

   This cycle continues until the event has completed its state machine.