IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > The hot standby option > Use hot standby
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Enterprise Automation Server
The Tivoli Enterprise Automation Server supports hot standby when it is co-located with a Hub monitoring server that is configured for hot standby. The Tivoli Enterprise Automation Server must be co-located with each Hub monitoring server that is configured for hot standby. When the automation server is configured in a Hot Standby environment, the Registry Services component of Jazz for Service Management must be at version 1.1.0.1 (or later). The Tivoli Enterprise Automation Server does not support hot standby failover independent of the hub monitoring server.
The Tivoli Enterprise Automation Server queries the hot standby role of the Hub that it is co-located with, and assumes a corresponding operational role. When the co-located hub is the acting hub, the Tivoli Enterprise Automation Server is fully operational: it can register resources, and respond to client requests for resource metrics. When the co-located hub is the standby hub, the Tivoli Enterprise Automation Server also assumes a standby role: it does not register resources, and it redirects client requests for resource metrics to the Tivoli Enterprise Automation Server that is co-located with the acting hub. Client requests are redirected with an HTTP 301 status code, and include the URL of the resource at the Tivoli Enterprise Automation Server that is co-located with the acting hub. If client redirection is not possible, an HTTP 404 status code is returned. After a hub failover, the automation server co-located with the acting hub sends a request to Registry Services to update resource URLs to point to the acting automation server. This resource URL remapping minimizes client request redirects and resolves the condition that the automation server for the standby hub is not available to perform a redirect.
Parent topic:
Use hot standby