Continuous Update Exception Handling

CA IdentityMinder Integration Guide › Integration Concepts › Continuous Update › Continuous Update Exception Handling

Continuous Update Exception Handling

If issues occur between CA IdentityMinder and CA GovernanceMinder while they are integrated, CA IdentityMinder processes the notification queue accordingly so that the queue does not become too large. The following table lists the possible exceptions and how CA IdentityMinder handles the notification queue in each scenario.

Exception Source	CA IdentityMinder Action
Network issues such as the following: network down server down invalid port invalid credentials	CA IdentityMinder returns all notifications back to the queue. CA IdentityMinder tests the connection to CA GovernanceMinder during the next cycle and resends the batch if the network connection is back up.
CA GovernanceMinder universe deleted	CA IdentityMinder deletes the CA GovernanceMinder connection object for the environment and stop queuing notifications.
CA IdentityMinder environment deleted	CA IdentityMinder flushes the queue of all notifications for the environment.
CA GovernanceMinder can not queue notifications, for example, if the JMS queue is down.	CA IdentityMinder retries to send the batch of notifications on the next cycle, as many times as the specified retry limit. When CA IdentityMinder reaches the retry limit, the entire batch of notifications are deleted from the queue.
CA GovernanceMinder internal server exception, for example, out of memory.	CA IdentityMinder returns all notifications back to the queue. During the next cycle, CA IdentityMinder retries to send the batch. If an exception occurs again, CA IdentityMinder removes the entire batch from the queue.