Programming Guides › Programming Guide for Java › Event Listener API › Event Listener API Overview › Use Case Examples

Use Case Examples

The following are examples of how you can use the Event Listener API:

Add a user to Microsoft Exchange (specific event listener)

When a user is successfully added to the admin role Exchange Users, CA IdentityMinder calls the method after() in an event listener associated with the event AssignAdminRoleEvent. The implementation of the after() method uses an Exchange API to add the user to the Exchange system. The information required to access the Exchange server (SERVER_NAME, ADMIN_ID, ADMIN_PASSWORD, and so on) is included in the user-defined properties of the CA IdentityMinder environment. CA IdentityMinder environment properties are passed to the init() method of the EventListenerAdapter.

Create a rule for group assignments (specific event listener)

When a user is created, CA IdentityMinder calls the after() method in an event listener associated with the event CreateUserEvent. The implementation of the after() method evaluates user attributes such as Job Title, Security Level, and Department to assign the user to one or more groups. For each group assignment, the implementation generates the secondary event AddToGroupEvent. This secondary event can be subject to workflow approvals and auditing.

Update an RDBMS with user data (class-level event listener)

Suppose that user information such as user ID, user name, email address, and group membership is stored in an RDBMS. Whenever any user-level event occurs (CreateUserEvent, ModifyUserEvent, and so on), the user’s record in the RDBMS must be updated. After the event is executed, CA IdentityMinder calls the method after() in an event listener associated with user events. The implementation of this method retrieves the RDBMS connectivity parameters from the CA IdentityMinder environment properties passed into the init() method, and then updates the user record in the RDBMS.

Post events to a JMS queue (all event listener)

After any event is successfully executed, CA IdentityMinder calls the method after() in an event listener associated with all events. This event listener writes all events to a specific Java Message Service (JMS) queue. The Java Naming and Directory Interface (JNDI) name for the queue and the information in the jndi.properties file is configurable through the properties of the CA IdentityMinder environment. The after() method implementation uses the JNDI information to post a simple object message to the queue.