Hosts

This tab displays all of the hosts associated with an IdentityIQ instance.

Click on a name in the Host Name column to show all ServerStatistics captured for the selected host, grouped by Snapshots. The snapshots can be cycled using the previous/next arrows, or selected by name using the drop-down list.

Use the action buttons in the Host Action column to configure or delete hosts. The Host Setting dialog enables you to specify the services running on each host and configure host monitoring.

Deleting a host will remove all associated server statistics, as well as the Server object. The host will no longer appear in the list of hosts after deletion. However, if the underlying server is still running, the host will reappear the next time its heartbeat service runs. All configuration settings for a re-generated host will use defaults for the its list of services, and for the monitoring service configuration.

For hosts running on Unix operating systems, there is an option, openfilecount, to display the number of open files to avoid running out of file handles. This count is on the operation system, not the application server. This column can only be enabled manually from the UI Configuration object on the debug pages.

This enables a specific host to enable/disable services. The one exception is the Request Service. The Request Service cannot be fully shut down. The Host, if service shutdown, still processes requests that have been specifically targeted to that host, but will not pick up generic requests (un-targeted requests).

The Reanimator service helps manage “hung” tasks. An un-partitioned task can sometimes fail without properly updating the state of the TaskResult. This can leave the task in a “hung” state, appearing to still be running even though it isn’t. The most common cause for this kind of issue is a temporary loss of connection to the database, or a brief database server failure. However, the Reanimator service performs the task of resetting requests or tasks regardless of the underlying reason.

When a task has hung, the Reanimator service resets the task or request so that it can resume. The service can also help with the termination of a task or request that is not configured to resume upon being orphaned or failing. If the task or request is not configured to resume, then when the service detects a task in a hung state, it automatically marks it as terminated.

If you are using Email Task Alerts in any of your task definitions, be aware that when a task hangs and is restarted by the reanimator service, email task alert notifications may not be sent.

The Reanimator service runs by default on all hosts. Although it is unlikely that you would need to switch it off, it is possible to do so – for example, if you have a dedicated UI host, you might not need this service running there. To disable the Reanimator service on a specific host:

  1. On the Hosts tab, click the gear icon beside the specific host on which you want to disable the service.

  2. On the Services tab of the Host Configuration dialog, use the slider to switch off the Reanimator service.

The Application Monitoring does not adhere to the restore defaults.

The Configuration tab enables host specific monitoring configuration. This enables you to override the global defaults for Polling Interval and Statistics Retention, and to enable and disable given retained statistics.

Click Use Default Settings to clear all host specific overrides revert back to the global defaults.

The Configuration tab also allows selecting Applications in which to monitor health. When selected, the Application is contacted each time the monitoring service runs, and the health check status is recorded.