If issues occur between CA Identity Manager and CA Identity Governance while they are integrated, CA Identity Manager processes the notification queue accordingly so that the queue does not become too large. The following table lists the possible exceptions and how CA Identity Manager handles the notification queue in each scenario.
|
Exception Source |
CA Identity Manager Action |
|---|---|
|
Network issues such as the following:
|
CA Identity Manager returns all notifications back to the queue. CA Identity Manager tests the connection to CA Identity Governance during the next cycle and resends the batch if the network connection is back up. |
|
CA Identity Governance universe deleted |
CA Identity Manager deletes the CA Identity Governance connection object for the environment and stop queuing notifications. |
|
CA Identity Manager environment deleted |
CA Identity Manager flushes the queue of all notifications for the environment. |
|
CA Identity Governance can not queue notifications, for example, if the JMS queue is down. |
CA Identity Manager retries to send the batch of notifications on the next cycle, as many times as the specified retry limit. When CA Identity Manager reaches the retry limit, the entire batch of notifications are deleted from the queue. |
|
CA Identity Governance internal server exception, for example, out of memory. |
CA Identity Manager returns all notifications back to the queue. During the next cycle, CA Identity Manager retries to send the batch. If an exception occurs again, CA Identity Manager removes the entire batch from the queue. |
|
Copyright © 2014 CA.
All rights reserved.
|
|