Installing Remedy SSO in the high-availability mode using the TrueSight installer wizard
Where you are in the Installation process
Step | Task |
---|---|
1 | Complete the planning activities |
2 | Prepare for TrueSight Operations Management installation |
3 | Install Remedy Single Sign-On — Phase A (You are here) |
Install Remedy Single Sign-On — Phase B | |
4 | Install TrueSight Presentation Server |
5 | Install TrueSight Infrastructure Management (If licensed) |
6 | Install TrueSight App Visibility Manager (If licensed) |
7 | Install Real End User Experience Monitoring Software Edition (If licensed) |
8 | Install TrueSight IT Data Analytics (If licensed) |
9 | Complete the post-installation activities |
To install Remedy SSO using the wizard-based TrueSight installer in the high-availability mode
Remedy Single Sign-On high-availability environment is implemented as a redundant system with session failover. If the primary node fails, the load is transitioned to the secondary node with minimal interruption.
In a high-availability (HA) environment, multiple instances of the Remedy Single Sign-On (Remedy SSO) web application are deployed to form a cluster. Usually, a load balancer is used as a front end to the cluster, giving the external applications the appearance of a single server. The load balancer distributes requests among Remedy SSO nodes. However, there is no requirement for a sticky session, because requests can be handled by any instance.
You need to perform the following tasks to install Remedy SSO in a high-availability mode:Step A: Install Remedy SSO on the primary computer
Do the following:
Log in to the host computer on which you want to install Remedy SSO, and delete all the files from the temporary directory:
- (Windows) %temp%
(Linux) /tmp
Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:
(Windows)C:\Program Files
(Linux) /opt
Run the installer:
(Windows) As an administrator or as a non-administrator user, run setup.exe from Windows\Disk1
(Linux) As a non-root user, run ./setup.bin from Linux/Disk1
- (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately:
export DISPLAY=<IP address of the host computer>:0.0
- Review the welcome page, and click Next.
- Read the license agreement, agree to the terms, and click Next.
Review disk space requirements. If required, you can change the default installation directory, and click Next:
(Windows) C:\Program Files\BMC Software\TrueSightRSSO
(Linux) /opt/bmc/TrueSightRSSO
Select PostgreSQL - External database type to use an existing PostgreSQL database instance.
Note
- Ensure that the PostgreSQL database is installed on a separate host computer that is different from the host computers on which you plan to install the primary and secondary Remedy SSO servers.
- Primary and secondary Remedy SSO servers must be able to access the host computer on which the PostgreSQL database is installed.
- Type the database details such as host name, database name, and port number of the existing PostgreSQL database, and click Next.
- Select Create New User to create a new database user to manage Remedy SSO operations.
Type the database admin and user name details, type the respective passwords, and confirm them.
You will need to provide these database user details while installing Remedy SSO on the secondary node.
Type the Tomcat port details that you want to use to communicate with Remedy SSO. You can retain the following default port values or type new values. Click Next:
- (Windows) HTTP: 88 and HTTPS: 448
- (Linux) HTTP: 8088 and HTTPS: 8048
By default, the installer configures Remedy Single Sign-On in HTTPS. If you want to use HTTP, you must manually configure it anytime as a post-installation activity .
Configure the cookie domain and Server FQDN details, and click Next.
This is the cookie domain that you want to use to access Remedy SSO. It must be same as the network domain of host computer on which you are installing Remedy SSO or one of its parent domains. For example: If the host computer on which you want to install Remedy SSO belongs to apps.bmc.com, then your cookie domain must be bmc.com.
- Preview the details, and verify the configurations.
- Click Install to start the installation. A local installation may take up to 15 minutes.
After the installation is complete, the Installation Summary page is displayed. Click View log to view the installation log details on the screen. From the log view, you can expand and view the log messages.
Note:
BMC Recommends that you also open the remedysso_install_log.txt log file and verify if there are warnings and errors that need to be fixed. Contact BMC Support for Remedy SSO to fix any unresolved errors or warnings.
- (Windows)<installationDirectory>\rsso\RemedySSO\logs\
(Linux) <installationDirectory>/rsso/RemedySSO/logs
- Click Done to exit the installation program.
Verify that the following environment variable points to the Remedy SSO installation path:
(Windows) %TRUESIGHTRSSO_HOME%
(Linux) $TRUESIGHTRSSO_HOME
On Windows, do the following to verify the path :
- Open a New Admin Command Prompt
- Type
echo %TRUESIGHTRSSO_HOME%
(Alternatively) On Windows, you can navigate to System > Advanced System Settings > Environment Variables > System Variables lower panel to verify the path
You can either construct the Remedy SSO URL or locate the URL in the log file:
- To construct the URL, use the format: http(s)://<rsso_servername_FQDN>:<tomcat_port>/rsso
- To locate the URL:
- Open the truesightrsso_install_log.txt log file from:
- (Windows)<installationDirectory>\rsso\logs\
(Linux) <installationDirectory>/rsso/logs
Search for the LOG EVENT that has the product URL as shown in the following example:
(Windows)
LOG EVENT {Description=[PRODUCT URL],Detail=[product url: https://HostA.bmc.com:448/rsso]}
(Linux)
LOG EVENT {Description=[PRODUCT URL],Detail=[product url: https://HostA.bmc.com:8048/rsso]}
- Open the truesightrsso_install_log.txt log file from:
Launch the Remedy SSO URL in a browser, and log in to the Remedy SSO console. The user name and password are case sensitive. Use the following default Admin credentials:
User name: Admin
Password: RSSO#Admin#
Change the password for the Admin user. Click Admin > Change Password.
Change password
Use the same password when you change the password for the Secondary computer.
Log out of the Remedy SSO console, and log in with the new Admin credentials.
Your installation is complete if you are a Windows user.
(Linux) Configure the Remedy SSO service to restart automatically each time the Remedy SSO server is restarted:
- Log in to the host computer as a root user.
From the command line, go to <installationDirectory>/rsso/bin, and run the following command:
./rsso service register <nonRootUserName><nonRootUserName> refers to the name of the non-root user that you used for installing Remedy SSO.
Step B: Install Remedy SSO on the secondary computer
Do the following:
Log in to the host computer on which you want to install Remedy SSO, and delete all the files from the temporary directory:
- (Windows) %temp%
(Linux) /tmp
Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:
(Windows)C:\Program Files
(Linux) /opt
Run the installer:
(Windows) As an administrator or as a non-administrator user, run setup.exe from Windows\Disk1
(Linux) As a non-root user, run ./setup.bin from Linux/Disk1
- (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately:
export DISPLAY=<IP address of the host computer>:0.0
- Review the welcome page, and click Next.
- Read the license agreement, agree to the terms, and click Next.
Review disk space requirements. If required, you can change the default installation directory, and click Next:
(Windows) C:\Program Files\BMC Software\TrueSightRSSO
(Linux) /opt/bmc/TrueSightRSSO
Select PostgreSQL - External database type to use an existing PostgreSQL database instance.
- Ensure that the PostgreSQL database is installed on a separate host computer that is different from the host computers on which you plan to install the primary and secondary Remedy SSO servers.
- Primary and secondary Remedy SSO servers must be able to access the host computer on which the PostgreSQL database is installed.
Type the database details such as host name, database name, and port number of the existing PostgreSQL database that you used while installing on the primary node, and click Next.
- Select Use Existing User to use an existing database user to manage Remedy SSO operations.
- Type the database user name and password that you created while installing Remedy SSO on the primary node, and click Next.
Type the Tomcat port details that you want to use to communicate with Remedy SSO. You can retain the following default port values or type new values. Click Next:
- (Windows) HTTP: 88 and HTTPS: 448
- (Linux) HTTP: 8088 and HTTPS: 8048
By default, the installer configures Remedy Single Sign-On in HTTPS. If you want to use HTTP, you must manually configure it anytime as a post-installation activity .
Configure the cookie domain and Server FQDN details, and click Next.
This is the cookie domain that you want to use to access Remedy SSO. It must be same as the network domain of host computer on which you are installing Remedy SSO or one of its parent domains. For example: If the host computer on which you want to install Remedy SSO belongs to apps.bmc.com, then your cookie domain must be bmc.com.
- Preview the details, and verify the configurations.
- Click Install to start the installation. A local installation may take up to 15 minutes.
After the installation is complete, the Installation Summary page is displayed. Click View log to view the installation log details on the screen. From the log view, you can expand and view the log messages.
Note:
BMC Recommends that you also open the remedysso_install_log.txt log file and verify if there are warnings and errors that need to be fixed. Contact BMC Support for Remedy SSO to fix any unresolved errors or warnings.
- (Windows)<installationDirectory>\rsso\RemedySSO\logs\
(Linux) <installationDirectory>/rsso/RemedySSO/logs
- Click Done to exit the installation program.
Verify that the following environment variable points to the Remedy SSO installation path:
(Windows) %TRUESIGHTRSSO_HOME%
(Linux) $TRUESIGHTRSSO_HOME
On Windows, do the following to verify the path :
- Open a New Admin Command Prompt
- Type
echo %TRUESIGHTRSSO_HOME%
(Alternatively) On Windows, you can navigate to System > Advanced System Settings > Environment Variables > System Variables lower panel to verify the path
You can either construct the Remedy SSO URL or locate the URL in the log file:
- To construct the URL, use the format: http(s)://<rsso_servername_FQDN>:<tomcat_port>/rsso
- To locate the URL:
- Open the truesightrsso_install_log.txt log file from:
- (Windows)<installationDirectory>\rsso\logs\
(Linux) <installationDirectory>/rsso/logs
Search for the LOG EVENT that has the product URL as shown in the following example:
(Windows)
LOG EVENT {Description=[PRODUCT URL],Detail=[product url: https://HostA.bmc.com:448/rsso]}
(Linux)
LOG EVENT {Description=[PRODUCT URL],Detail=[product url: https://HostA.bmc.com:8048/rsso]}
- Open the truesightrsso_install_log.txt log file from:
Launch the Remedy SSO URL in a browser, and log in to the Remedy SSO console. The user name and password are case sensitive. Use the following default Admin credentials:
User name: Admin
Password: RSSO#Admin#
Change password
This password must match the password you specified for the Primary computer.
- Change the password for the Admin user. Click Admin > Change Password.
Log out of the Remedy SSO console, and log in with the new Admin credentials.
Your installation is complete if you are a Windows user.
(Linux) Configure the Remedy SSO service to restart automatically each time the Remedy SSO server is restarted:
- Log in to the host computer as a root user.
From the command line, go to <installationDirectory>/rsso/bin, and run the following command:
./rsso service register <nonRootUserName><nonRootUserName> refers to the name of the non-root user that you used for installing Remedy SSO.
Step C: Set up and configure the load balancer details
Set up the load balancer on a host computer other than the primary and secondary Remedy SSO host computers. Refer to the specific load balancer documentation or ask the vendor for details about the configuration.
Troubleshooting installation issues
If you face issues during installation, see Troubleshooting the Remedy Single Sign-On server deployment.
Next step in the Installation process
Step 3 Phase B — Now that you have successfully installed Remedy SSO, you must set up the Remedy SSO server.
Comments
Please clarify step #22, it states "Your installation is complete if you are a Windows user." What if you are Linux user?
Hi Cassie Derrick,
Added the steps for Linux. You will see the change with our next doc publishing.
[just dropping this in as a comment to make it visible to other users. I have already provided it as feedback on the page itself]
There needs to be a statement at the very beginning of the installation process stating that a functioning PostgreSQL DB configuration should already have been built. Casually mentioning this at Step 8 is a bit late. Additionally, I'd have thought that anyone wishing to install RSSO in HA mode would [probably be expecting to have an equally resilient backend DB. So strictly speaking Step 1 of installing "RSSO in HA Mode" should read "build an HA instance of PostgreSQL"
Hi John Conroy,
It is mentioned in the preparing topic. See Preparing to install Remedy SSO with the TrueSight installer (PostgreSQL configuration details section.)
Log in or register to comment.