Planning the Remedy Single Sign-On Server deployment

Use the topics in this section when you plan for the Remedy SSO Server deployment. You must install the Remedy SSO Server before installing or upgrading the TrueSight Presentation Server. You must be aware of the following general information before you proceed to deploy the Remedy SSO server:

• Remedy SSO must be installed and configured to work with the Presentation Server.
• Remedy SSO can be installed on the same or different host machines as the Presentation Server.
• Remedy SSO can be installed as a standalone instance or in a high-availability environment to work with the Presentation Server.
• A single instance of Remedy SSO can support one or more Presentation Servers.
• An existing Remedy SSO Server version 9.1.03.001 configured with other BMC products, can be configured to work the Presentation Server. 
• If you are using an earlier version of Remedy SSO, for example, 9.1.00, you must upgrade your Remedy SSO to 9.1.03.001 before installing or upgrading your Presentation Server.
• For proper authorization, make sure that the cookie domain used for Remedy SSO and the domain value for the Presentation Server both belong to the same network domain or one of its parent domains as the cookie domain. For example, if xyz.com is the cookie domain of Remedy SSO, then tspshost.abc.xyz.com could be the domain name for the Presentation Server.
• After installing the Remedy SSO server and before upgrading the Presentation Server from an earlier version, you must migrate the local users and local user groups for each tenant that are existing on Atrium SSO to Remedy SSO. Migration scripts are provided for this purpose.
• As there are two methods to install the Remedy SSO, review the deployment options for installing Remedy SSO carefully before proceeding to choose one.
• Review the preinstallation requirements mentioned in this document before installing Remedy SSO.

Where to go from here

Deployment options for Remedy SSO with TrueSight Operations Management