Performing the Remedy SSO installation for high-availability with the TrueSight installer
Remedy Single Sign-On high-availability (HA) environment is implemented as a redundant system with session failover. In this model, if a node fails, the single sign-on load is transitioned to the remaining servers with minimal interruption.
The Remedy SSO Admin UI requires sticky session/Session Persistence in an HA environment. Usually, this is accomplished by enabling sticky session/Session Persistence on the load balancer. Different load balancers have different configurations to enable a sticky session/Session Persistence. Refer to the specific load balancer documentation or ask the vendor for detais about the configuration.
Note that when sticky session/Session Persistence is not enabled for the Remedy SSO Admin UI, the admin user behind the firewall can use a specific Remedy SSO server hostname to access admin UI instead of using the load balancer URL.
To install Remedy SSO in the high-availability mode with the TrueSight installer
While running the installation, the database type specified must be PostgreSQL External. Also, while configuring user accounts for managing PostgreSQL database operations, you need to create a new user (Create New User option on the installer).
While running the installation, the database settings must be the same as the settings used by the primary node. Also, while configuring user accounts for managing PostgreSQL database operations, you need to specify an existing user (Use Existing User option on the installer) and provide details of the user created while installing Remedy SSO on the primary node.
Where to go from here
To configure the Remedy SSO settings, see Configuring the general settings in the Remedy SSO server.