Preparing to install Remedy SSO with the TrueSight installer
- There is no TrueSight installer for Remedy SSO available for version 11.3.02. It is available for versions 11.0.00 and 11.3.01 only. You can choose to install using the TrueSight installer for Remedy SSO version 11.3.01 and then upgrade to any of the supported versions of the Remedy SSO server using the Remedy SSO installer.
- Alternatively, you can directly install any of the supported versions of the Remedy SSO server using the Remedy SSO installer. For installing Remedy SSO using the Remedy installer, see Installing.
- If you have installed and configured TrueSight installer for Remedy SSO (consolidated installer) version 11.0 or 11.3.01 and plan to upgrade to Remedy SSO to 18.11 or later, ensure that you have performed the steps mentioned in Best practices before upgrading Remedy SSO section in the Preparing to upgrade Remedy Single Sign-On topic. For upgrading Remedy SSO using the Remedy installer, see Upgrading.
Complete the pre-installation tasks for Remedy SSO
Ensure that the target computer meets the for Remedy SSO.
- Review the Known and Corrected issues documentation for the Remedy SSO server version that you are planning to install. You can see
- Review the issues section for any installation-related issues.
- Plan to host Remedy SSO on the same network domain or one of the parent domains on which you plan to install other TrueSight products to avoid any access-related issues.
Ensure that you have the following privileges to install:
- (Windows) You can install Remedy SSO as an administrator or as a non-administrator user. The non-administrator user must be a part of the Administrators group.
(Linux) You can install Remedy SSO as a non-root user only. To be able to perform the installation, a non-root user needs the following permissions:
- Read, write, and execute permissions for Remedy SSO installation directory and /tmp directory.
- Read and write permissions for the /opt/bmc directory.
The ProductRegistry.xml file is created in the /opt/bmc directory. Therefore, the /opt/bmc directory requires read and write permissions. If the bmc directory does not exist, create it with read and write permissions.
Ensure that the target computer meets the following port requirements for the PostgreSQL database and the Tomcat server:
PostgreSQL configuration details
The default port used during the installation is 5438. You can choose to use the database packaged with the TrueSight installer for Remedy SSO or use an external instance of the database. If you plan to use the PostgreSQL-External option:
- Ensure that the database details such as Host name (FQDN), port number, database name, and administrator credentials (superuser) are ready before you install.
Ensure that the external PostgreSQL database is accessible from the host computer on which you want to install Remedy SSO. To do this:
- Log in to the host computer where PostgreSQL is installed.
- Edit the pg_hba.conf file to update the Remedy SSO host name. The file can be found at:
- (PostgreSQL on Windows) data\pg_hba.conf
- (PostgreSQL on Linux) data/pg_hba.conf
- (PostgreSQL on Linux) Restart the PostgreSQL server.
Tomcat Port numbers
The Remedy SSO server uses the HTTP or HTTPS protocol configured on the Tomcat server. The ports configured on the Tomcat server must be accessible from the host computers on which you want to install TrueSight products. The default ports used during installation are:
- (Windows) HTTP: 88 or HTTPS: 448
- (Linux) HTTP: 8088 or HTTPS: 8048
- (Linux) Ensure that the system default locale is set to UTF-8.
Remedy SSO latest patches and hot fixes
Always check for the latest hotfix or patch released for Remedy SSO. It is recommended to apply the latest hotfix or patch on top of the corresponding version of the Remedy SSO server. For example, apply RSSO_1808_2018NOV23_CU_ALL cumulative hot fix on top of Remedy SSO v18.08. For the list of available Remedy SSO patches, contact BMC Customer Support.
Configure the Terminal Server options in Windows
On Windows, to run the installation utility through a Terminal Services connection or a remote desktop session, configure the Terminal Server options that pertain to temporary folders.
You must configure the Terminal Server options only once on a host computer. You do not have to configure the options if you reinstall a TrueSight product on the same host computer.
Do the following:
- On the host computer, open the Local Group Policy Editor by selecting Start > Run, and type gpedit.msc.
- Expand the following folder: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders.
- Double-click the following options to set them to Enabled:
- Do not delete temp folder upon exit
- Do not use temporary folders per session
- On the host computer, open the Registry Editor by selecting Start > Run and typing regedit.
- Expand the following folder: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
- Set the value for PerSessionTempDir and DeleteTempDirsOnExit to 0.
- Restart the computer.
You can revert these changes after you complete the installation process. You might need to restart the computer.
Where to go from here
If you are installing the product, perform the other preinstallation tasks listed in the Preparing to install the TrueSight Operations Management solution page.