Performing Remedy Single Sign-On installation for high-availability
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. Perform the following procedure to install Remedy SSO in a HA mode:
Starting from version 9.1.03.001, the Remedy SSO Admin UI does not need sticky sessions to function in an HA environment.
For earlier versions, the Remedy SSO Admin UI requires sticky session/Session Persistence in an HA environment. 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 high-availability mode
Before you install or upgrade Remedy SSO in an HA environment and if you choose to configure/use PostgreSQL, download PostgreSQL from their official site, and then install and configure it. When you run the Remedy SSO installer, select the external database option and not the embedded one.
- Ensure that Remedy SSO is installed successfully on the primary node as outlined in .
Unzip the Remedy SSO files on the additional node.
- Run the installation program.
Click Next to confirm the database settings. The database settings should be same as the settings used by the primary node.
In the window to assign database users, select the Use Existing User option.
When you add nodes, select the Use Existing User option and enter credentials that are used by the primary node.
- Complete the rest of the installation steps.
Where to go from here
To configure the Remedy SSO settings, see Configuring the general settings in the Remedy Single Sign-On server.