Installing the Presentation Server in the high-availability mode using the 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
4	Install TrueSight Presentation Server — Phase A (You are here)
4	(Optional) Configure TrueSight Presentation Server for disaster recovery — Phase B
5	Install Infrastructure Management (If licensed)
6	Install 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 the TrueSight Presentation Server in the high-availability mode using the wizard-based installer

You need to perform the following tasks to install TrueSight Presentation Server in a high-availability environment.

Step A: Install TrueSight Presentation Server on the primary computer

Log in to the host computer (as a root user if you are using Linux) on which you want to install Presentation Server, and delete all the files from the temporary directory:
- (Windows) %temp%
- (Linux) /tmp
Extract the downloaded files to a temporary location outside the following location to avoid any file sharing conflicts:
- (Windows) C:\Program Files
- (Linux) /opt
(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
Note
Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. However, in a test environment, you can skip the system requirements validation and run the installer by using the -J MINIMAL=true argument.
- Total RAM (in MB): 32,000
- Available RAM (in MB): 25,000
- Total swap space / page file (in MB): 8,000
- Available swap space / page file (in MB): 8,000
By default, the TrueSight Presentation Server uses 256-bit encryption. However, AES 256-bit encryption is not allowed in some countries due to import regulations. You can change the default encryption key size when you invoke the installer.

Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.

Environment type	Command
Production environment with the default encryption setting	(Windows) `install.cmd` (Linux - as a non-root user) `./install.sh`
Production environment with user-specified encryption setting	(Windows) `install.cmd` `–J BMC_TS_KEY_SZ=<128/256>` (Linux - as a non-root user) `./install.sh –J BMC_TS_KEY_SZ=<128/256>`
Test environment with the default encryption setting	(Windows) `install.cmd` `-J MINIMAL=true` (Linux - as a non-root user) `./install.sh` `-J MINIMAL=true`
Test environment with user-specified encryption setting	(Windows) `install.cmd` `–J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true` (Linux - as a non-root user) `./install.sh` `–J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true`

Review the welcome page, and click Next.
Read the license agreement, agree to the terms, and click Next.
Select the Custom installation type, and click Next.
Review the disk space requirements. The default installation directory is:
- (Windows) C:\Program Files\BMC Software\TrueSightPServer
- (Linux) /opt/bmc/TrueSightPServer
You can change the default directory, if required, and click Next.
The installer detects the FQDN of the host computer and populates the FQDN field automatically. Ensure that the FQDN is accessible by the other TrueSight components in your environment.
If you modify the FQDN:
- Do not manually type any IP address in the FQDN field.
- Do not leave this field empty.
- Ensure that the host computer belongs to the same network domain as that of Remedy Single Sign-On (Remedy SSO) cookie domain.
Confirm this, and click Next.

Select Enabled > Primary Server, provide the following details and click Next.

Field	Description
If you plan to change the default high availability port numbers, use port numbers between 1024 and 65535 only.
Server Pair Name	Elasticsearch cluster name for one or more nodes that hold all the data and provide federated indexing and search capabilities across all nodes. You can change this name to reflect the logical group name of the cluster. Default is truesight.
Cache Replication Port	Default port is 7800.
Control Port	Default port is 8800.
Secondary Server FQDN	Fully Qualified Domain Name for the secondary server host. The Secondary Server maintains a constantly updated cache memory of the TrueSight Presentation Server activity. Ensure that the FQDN is accessible by the other TrueSight components in your environment. Note The TrueSight Presentation Server domain should be same as the cookie domain configured on the Remedy Single Sign-On server.
Secondary Server Database Port	Default port is 5432.
Secondary Cache Replication Port	Default port is 7800.
Secondary Control Port	Default port is 8800.

Retain the following default values for Tomcat Apache Server, Elasticsearch, and Event Ingress ports, or type new values, and click Next.
- Tomcat port: HTTPS: 443, HTTP: 80
- Elasticsearch ports: REST: 9200, Java/Node Client: 9300
- Event Ingress port: 1900
If you want to change these default port numbers, use numbers between:
- (Windows) 1 and 65535.
- (Linux) 1024 and 65535.
Type the PostgreSQL database details such as the user name, password, and port number. Click Next.
- The database username and password must not exceed 30 characters.
- If you want to change the default port number (5432), use port numbers only between:
  - (Windows) 1 and 65535
  - (Linux) 1024 and 65535
The Installer creates a new database user using these values.
Provide the following details for Remedy SSO, and click Next:
Note: If you have configured a Load Balancer for Remedy SSO, you must type the corresponding load balancer details.
1. Type the FQDN of the host computer on which you have installed Remedy SSO or the load balancer URL.
2. Type the tomcat port number that you have configured while installing Remedy SSO or the load balancer port number. The default port number for Remedy SSO is:
  - (Windows) HTTPS: 448 and HTTP: 88
  - (Linux) HTTPS: 8048 and HTTP: 8088
3. Type the Remedy SSO server superuser password. The Remedy SSO superuser name is Admin.
4. Select HTTP or HTTPS depending on the Remedy SSO configuration . By default, Remedy SSO is configured in the HTTPS mode.
5. Select Yes or No to import the Remedy SSO private certificate. If you select:
  - Yes: Specify the directory where the Remedy SSO private certificate is stored.
  - No: You can import the Remedy SSO certificate after the installation is completed. For details, see Applying Remedy Single Sign-On Server private certificate to the TrueSight Presentation Server.
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. You can also navigate to the following default location of logs:
- (Windows) \Temp\truesightpserver_install_log.txt
- (Linux) /tmp/truesightpserver_install_log.txt
Click Done to exit the installation program.
Verify that the following environment variable points to the TrueSight Presentation Server installation path:
- (Windows) %TRUESIGHTPSERVER_HOME%
- (Linux) $TRUESIGHTPSERVER_HOME
Note: (Optional) After the installation is complete, you can revoke the write permission on the /opt directory.
Verify the TrueSight Presentation Server status:
- (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run tssh server status command.
- (Linux) Navigate to the TrueSightPServer/truesightpserver/bin directory, and run ./tssh server status command.
A list of Presentation Server processes are displayed as shown in the following example.
Process status ================================ Core Server Running (13176) Index Server Running (11028) Database Server Running (6052)
If errors occur when you run the tssh server status command, restart the Presentation Server by running the following command:
- (Windows) tssh server start
- (Linux) ./tssh server start
(Linux only) Register the BMCTSPSSvc.service service by performing the following steps:
Note: The systemd service BMCTSPSSvc.service is supported only from version 11.3.04. For more information on this service, see Starting and stopping the TrueSight Operations Management components.
1. As a root user, run the tssh service register <Non-RootUserName>. This command registers the BMCTSPSSvc.service service under the /etc/systemd/system folder.
2. (SUSE Linux Enterprise Server only) Run the chkconfig --add BMCTSPSSvc.service command.
If you restart the TrueSight Presentation Server host without registering the BMCTSPSSvc service, the processes do not come up and you will need to start the TrueSight Presentation Server manually.
Verify whether the service is registered with the following steps:
1. Ensure that you have read and write permissions for the installedDirectory\truesightpserver\logs\tssh.log file.
2. Running the systemctl status BMCTSPSSvc.service command.
To start and stop the service, run the following commands:
- systemctl start BMCTSPSSvc.service
- systemctl stop BMCTSPSSvc.service
In an IPv6 environment, comment the following properties and restart the TrueSight Presentation Server:
- #vm.args.system.26 in the installedDirectory\truesightpserver\conf\custom\csr.conf and installedDirectory\truesightpserver\conf\services\csr.conf files
- #vm.args.system.18 in the installedDirectory\truesightpserver\conf\custom\idxsrv.conf and installedDirectory\truesightpserver\conf\services\idxsrv.conf files
(Applicable only if you plan to connect to the TrueSight Presentation Server with an alias name) The TrueSight Presentation Server validates all incoming requests to prevent Cross-Site Forgery (CSRF) attacks. If you plan to connect to the TrueSight Presentation Server with an alias or a proxy name, you must configure all hosts, aliases, or proxies for CSRF validation. Unless you do this, you cannot access TrueSight Presentation Server even if the installation completed successfully.
Run the following commands to enable the CSRF filter for the alias names set:
1. Navigate to the following location:
  - (Windows) TrueSightPServer\truesightpserver\bin
  - (Linux)TrueSightPServer/truesightpserver/bin
2. Run the tssh properties set tspsProxyHosts <alias1>,<alias2>,<alias3> command.
  Example
  
  If you have set a single alias name for the TrueSight Presentation Server host:
  tssh properties set tspsProxyHosts HostHouston
  If you have set multiple alias names for the TrueSight Presentation Server host:
  tssh properties set tspsProxyHosts HostHouston,HostLondon,HostPune
3. Run the tssh properties reload command.
To disable the CSRF filter
Note

If implementing the CSRF validation degrades the performance of the UI, you can disable the CSRF filter. However, BMC strongly discourages this action.
Run the following commands:
Navigate to the following location:
(Windows) TrueSightPServer\truesightpserver\bin
(Linux) TrueSightPServer/truesightpserver/bin
Run the tssh properties set csrfFilter false command.
Run the tssh properties reload command.
Copy the ha-shared.conf file from the <Primary Server installation directory>\truesightpserver\conf directory to an appropriate location on the secondary server. You will need to upload this file while installing TrueSight Presentation Server on the secondary computer.

Step B: InstallTrueSight Presentation Server on the secondary computer

Ensure that the Presentation Server is up and running on the primary computer.
Log in to the host computer (as a root user if you are using Linux) on which you want to install Presentation Server, and delete all the files from the temporary directory:
- (Windows) %temp%
- (Linux) /tmp
Extract the downloaded files to a temporary location outside the following location to avoid any file sharing conflicts:
- (Windows) C:\Program Files
- (Linux) /opt
(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
Note
Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. However, in a test environment, you can skip the system requirements validation and run the installer by using the -J MINIMAL=true argument.
- Total RAM (in MB): 32,000
- Available RAM (in MB): 25,000
- Total swap space / page file (in MB): 8,000
- Available swap space / page file (in MB): 8,000
By default, the TrueSight Presentation Server uses 256-bit encryption. However, AES 256-bit encryption is not allowed in some countries due to import regulations. You can change the default encryption key size when you invoke the installer.

Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.

Environment type	Command
Production environment with the default encryption setting	(Windows) `install.cmd` (Linux - as a non-root user) `./install.sh`
Production environment with user-specified encryption setting	(Windows) `install.cmd` `–J BMC_TS_KEY_SZ=<128/256>` (Linux - as a non-root user) `./install.sh –J BMC_TS_KEY_SZ=<128/256>`
Test environment with the default encryption setting	(Windows) `install.cmd` `-J MINIMAL=true` (Linux - as a non-root user) `./install.sh` `-J MINIMAL=true`
Test environment with user-specified encryption setting	(Windows) `install.cmd` `–J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true` (Linux - as a non-root user) `./install.sh` `–J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true`

Review the welcome page, and click Next.
Read the license agreement, agree to the terms, and click Next.
Select the Custom installation type, and click Next.
Review the disk space requirements. The default installation directory is:
- (Windows) C:\Program Files\BMC Software\TrueSightPServer
- (Linux) /opt/bmc/TrueSightPServer
You can change the default directory, if required, and click Next.
The installer detects the FQDN of the host computer and populates the FQDN field automatically. Ensure that the FQDN is accessible by the other TrueSight components in your environment.
If you modify the FQDN:
- Do not manually type any IP address in the FQDN field.
- Do not leave this field empty.
- Ensure that the host computer belongs to the same network domain as that of Remedy Single Sign-On (Remedy SSO) cookie domain.
Confirm this, and click Next.
Select Enabled > Secondary Server. Upload the ha-shared.conf file that you copied from the primary server.
Retain the following default values for Tomcat Apache Server, Elasticsearch, and Event Ingress ports, or type new values, and click Next.
- Tomcat port: HTTPS: 443, HTTP: 80
- Elasticsearch ports: REST: 9200, Java/Node Client: 9300
- Event Ingress port: 1900
If you want to change these default port numbers, use numbers between:
- (Windows) 1 and 65535.
- (Linux) 1024 and 65535.
Type the PostgreSQL database details such as the user name, password, and port number. Click Next.
- The database username and password must not exceed 30 characters.
- If you want to change the default port number (5432), use port numbers only between:
  - (Windows) 1 and 65535
  - (Linux) 1024 and 65535
The Installer creates a new database user using these values.
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. You can also navigate to the following default location of logs:
- (Windows) \Temp\truesightpserver_install_log.txt
- (Linux) /tmp/truesightpserver_install_log.txt
Click Done to exit the installation program.
Verify that the following environment variable points to the TrueSight Presentation Server installation path:
- (Windows) %TRUESIGHTPSERVER_HOME%
- (Linux) $TRUESIGHTPSERVER_HOME
Note: (Optional) After the installation is complete, you can revoke the write permission on the /opt directory.
Run the following command to verify the TrueSight Presentation Server status:
- (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run tssh server status command.
- (Linux) Navigate to the TrueSightPServer/truesightpserver/bin directory, and run ./tssh server status command.
A list of Presentation Server processes are displayed as shown in the following example:
Process status ================================ Core Server Running (13176) Index Server Running (11028) Database Server Running (6052)
If errors occur when you run tssh server status command, restart the Presentation Server by running the following command:
- (Windows) tssh server start
- (Linux) ./tssh server start
(Linux only) Register the BMCTSPSSvc.service service by performing the following steps:
Note: The systemd service BMCTSPSSvc.service is supported only from version 11.3.04. For more information on this service, see Starting and stopping the TrueSight Operations Management components.
1. As a root user, run the tssh service register <Non-RootUserName>. This command registers the BMCTSPSSvc.service service under the /etc/systemd/system folder.
2. (SUSE Linux Enterprise Server only) Run the chkconfig --add BMCTSPSSvc.service command.
If you restart the TrueSight Presentation Server host without registering the BMCTSPSSvc service, the processes do not come up and you will need to start the TrueSight Presentation Server manually.
Verify whether the service is registered with the following steps:
1. Ensure that you have read and write permissions for the installedDirectory\truesightpserver\logs\tssh.log file.
2. Running the systemctl status BMCTSPSSvc.service command.
To start and stop the service, run the following commands:
- systemctl start BMCTSPSSvc.service
- systemctl stop BMCTSPSSvc.service
In an IPv6 environment, comment the following properties and restart the TrueSight Presentation Server:
- #vm.args.system.26 in the installedDirectory\truesightpserver\conf\custom\csr.conf and installedDirectory\truesightpserver\conf\services\csr.conf files
- #vm.args.system.18 in the installedDirectory\truesightpserver\conf\custom\idxsrv.conf and installedDirectory\truesightpserver\conf\services\idxsrv.conf files
Verify the TrueSight Presentation Server HA installation by logging on to the primary and secondary computers.
The URL format is: http(s)://<TSPS_FQDN>:<tomcat_port>
- On the primary computer: You must be able to view the application without any errors.
- On the secondary computer: You must be able to see the following message:
  You accessed a system that is in standby mode. Contact you system administrator for assistance.

Note

The system requirements are validated every time you restart the host computer or product services. If the system requirements are not met, the product services are not started. To force-start the product services, see Starting and stopping the TrueSight Operations Management components. Open link

Step C: Set up and configure the load balancer details

Set up the load balancer on a computer other than the primary and secondary computers.

Then, configure the load balancer name on the primary computer.

To configure the load balancer name

On the primary computer, navigate to the following location:
- (Windows) TrueSightPServer\truesightpserver\bin
- (Linux) TrueSightPServer/truesightpserver/bin
Run the tssh properties set loadbalancername <loadbalancername> command.
Run the tssh properties reload command.
Run the following command to verify the high-availability deployment status:
tssh ha status

Now that you have set up the Load Balancer, your TrueSight Presentation Server HA deployment is complete.

Troubleshooting installation issues

If you face issues during installation, see Troubleshooting the Presentation Server deployment. Open link

Next step in the Installation process

Now that you have successfully installed the Presentation Server, do one of the following:

(Optional) Configure disaster recovery. For instructions, see Configuring the Presentation Server in the standalone and disaster recovery mode.
Install the other TrueSight components as per your license entitlements. For instructions, see Installation process.