We added some improvements to IdentityIQ 7.3 to make sure that your tasks and requests are not lost at sea.
Problems can surface in many different ways: a network failure makes your database server temporarily unavailable; or, one of your SailPoint hosts crashes and is replaced with another; or maybe your database server goes down and it takes a while for the backup to take over. IdentityIQ 7.3 can now better navigate these kinds of incidents without causing head-scratching situations to show up later.
Abandon a sinking database
Failed database connections are now better detected and acted upon. We fail faster when unrecoverable database problems are seen. Tasks/requests will abandon the database, fail, and wait to be rescued or properly disposed of later.
Search and Rescue
A temporarily-down database will prevent IdentityIQ from properly updating the completion state of tasks/requests. This is akin to the task/request being tossed overboard, but everyone believes it’s still at its post. So, we have introduced a new service (the Reanimator!) that can search and rescue (and restart) any task or request which appears in the database to be running, but in reality, really isn’t.
Search and Recovery
The Reanimator service can also ceremoniously mark a recovered task/request as completed (failed status) if it does not support restart.
This is especially useful for tasks — because a dead task will prevent the task from running again until its TaskResult is properly marked as completed.
Keeping a journal
Some of the long-running requests (aggregations and certifications) have been given the gift of a journal. The requests can now remember what they have accomplished, just in case disaster strikes, such as a host crash. If this occurs, the request will be automatically rescued and restarted on another host. Upon restart, the request can now consult its journal to skip re-doing the time-consuming work it had previously done and focus only on what remains to be done.
Managing your fleet
The new Environment Monitoring tool gives you a quick way to see the health of your hosts and applications, and to manage the services running per host. This is useful to keep your fleet of hosts running efficiently, and to be able to respond quickly to a storm.
These are just some of the improvements we added to 7.3 to help your IdentityIQ implementation to be even more reliable and efficient – when faced with the unpredictable and rough seas of your real world.