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 Portal server
The Tivoli Enterprise Portal Server cannot be configured to fail over to a standby hub. If the Tivoli Enterprise Portal Server is connected to the standby hub before it takes over as the acting hub, the portal server will need to be recycled in order to reflect data changes. Portal clients do not need to be reconfigured. Portal clients automatically reconnect to the portal server when the portal server is reconfigured and restarted.
You can configure an alias name for the portal server on your DNS server. If you do so, the portal server connects over an alias to the hub instead of by system name or IP address. By using an alias name, you can switch the Tivoli Enterprise Portal Server by changing the destination for the alias, rather than reconfiguring the Tivoli Enterprise Portal Server. After a recycle, the Tivoli Enterprise Portal Server switch is in effect.
The alias must be set on your DNS Server. The following steps show how the alias can be set on the DNS server:
Physical System Name IP-Address ALIAS-Name physicalsystem1.zurich.com 192.168.1.1 HUB-prod.zurich.com physicalsystem2.zurich.com 192.168.1.2These steps will allow the ALIAS Name to be moved on either System 1 or 2.
The dashboard data provider component of the portal server has a default provider ID (itm.<Hub TEMS name>). The provider ID is sent to the Dashboard Application Services Hub to uniquely identify the data provider connection. This ID also serves as the domain name to define domain-specific authorization policies. If you use the dashboard data provider component to provide monitoring data for display in the Dashboard Application Services Hub Server, then you must configure a domain override for the dashboard data provider when hot standby is used. This configuration ensures the connection between the dashboard server and the portal server and any domain-specific authorization policies are not required to change when the acting Hub changes. The domain override changes the provider ID and domain name for authorization policies to itm.<domain override value>. Specify the domain override when you configure your portal server and enable the dashboard data provider. If you modify the domain override after you configure a connection in your Dashboard Application Services Hub Server to the dashboard data provider, then you must delete the connection and add it again. See the ITM Administrator's Guide for details on how to configure a dashboard data provider connection.
Also, if you create any domain-specific authorization policies, then you must delete the permissions that specify the previous domain name and create new permissions that specify the new domain name when you change the domain override value. See the ITM Command Reference for details on the tivcmd CLI commands that are used to create and work with authorization policies.
Until the portal server is reconfigured to connect to the acting hub, the dashboard data provider component of the portal server cannot retrieve monitoring data for display in the Dashboard Application Services Hub.
Parent topic:
Use hot standby