Service status

The ISIM server tracks its ability to make remote connections and send provisioning requests to adapters on a per service basis. This ability is reflected in the Status for each service on the Manage Services panel. On this panel, we can also search for services with a specific status.

The value options in the Status list contain status values for each service.

All	Status values for all services.
Alive	Services that are functioning with no known issues.
Failed	Services that encountered a problem. For example: a connection test might fail, or a request was not completed on an endpoint because of a problem with making a remote connection.
Attempting recovery	Services that encountered a problem and for which the server is attempting to process a previously blocked request.
Locked	Services that are locked because a reconciliation process is running.
Unknown	Services that never attempted a connection test or received and processed a request.

Each status value other than Alive provides an icon that links to more detailed information about the state of the service. For example, if the server cannot complete a request due to a network or authentication problem, it marks the service as Failed. Until the service recovers from the Failed status, provisioning requests cannot be processed. The failing request and any additional account requests are blocked until the problem with the service is corrected. Clicking the Failed icon retrieves details about the failure, including the time of the first failure, detailed reason for the failure, and number of blocked requests.

The system periodically checks Failed services and attempts to recover the blocked requests. If the problem with the service is corrected, blocked requests can be completed due to this periodic check. The default time interval for the periodic recovery check is 10 minutes.

Restart blocked requests

Retry Blocked Requests provides an option to immediately restart the blocked requests from the Manage Services panel. This action tests a service to see whether the problem is corrected. If the test is successful, it restarts any blocked requests for a failed service. Failures are returned to the user interface so that all configuration problems with the service can be corrected. When the recovery process is started for a service, the service is placed in Attempting recovery status until all blocked requests are restarted. During this time, new requests can proceed normally. Provisioning requests can also be blocked during reconciliation with the locking feature enabled. In this case, the service status shows Locked until the reconciliation completes. At that time, the service status is updated to Attempting recovery until any blocked requests are processed. When all blocked requests are restarted, the service returns to the Alive status.

Retry Blocked Requests is controlled by a task in the view definitions defined in...

Set System Security > Manage Views

To restart the blocked requests of a service immediately, select...

Manage Services > Service Name > service > Retry Blocked Requests

Parent topic: Services administration