Installing the Presentation Server in the standalone mode using the wizard

Where you are in the Installation process

You can install the Presentation Server using one of these settings:

• Typical: Installs the Presentation Server using the default settings for the installation directory and the Tomcat Apache Server, Elasticsearch, and Event Ingress ports.
• Custom: Allows you to customize these settings. 

To perform a typical installation of the TrueSight Presentation Server in the wizard-based mode

1. 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

2. Extract the downloaded files to a temporary location outside the following location to avoid any file sharing conflicts:

   • (Windows) C:\Program Files
   • (Linux) /opt

3. (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.

   Excerpt named installupgradereq was not found in document xwiki:IT-Operations-Management.Operations-Management.BMC-TrueSight-Operations-Management.TSOMD113.Planning.Planning-the-Presentation-Server-deployment.System-requirements-for-Presentation-Server.WebHome.

   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.

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

5. Review the welcome page, and click Next.

6. Read the license agreement, agree to the terms, and click Next. 
7. Select the Typical installation type. 

8. 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.

9. 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.

10. 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.

11. Preview the details, and verify the configurations.
12. 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.

13. 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
14. Click Done to exit the installation program.

15. 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.

16. 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

17. (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 

18. 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

19. (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:

    1. Navigate to the following location:
       • (Windows) TrueSightPServer\truesightpserver\bin
       • (Linux) TrueSightPServer/truesightpserver/bin
    2. Run the tssh properties set csrfFilter false command.
    3. Run the tssh properties reload command.
20. (Optional) Do this only if you have installed Remedy SSO using the Remedy Installer:
    1. Log into the Remedy SSO console as an Admin user.
    2. From the Realm tab, click the Edit Realm icon for the "*" (asterisk) realm.
    3. From the Authentication tab, if the Authentication Type is set to AR, change it to Local.
    4. Click Save.

21. Go back to the Presentation Server and do the following:

    Define the Presentation Server URL using the following format, and launch the application in a browser:

    • (Windows) http(s)://<TSPS_FQDN>
    • (Linux) http(s)://<TSPS_FQDN>:<tomcat_port>

22. Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.

    The TrueSight console opens.

    Your installation is complete.

To perform a custom installation of the TrueSight Presentation Server in the wizard-based mode

1. 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
2. Extract the downloaded files to a temporary location outside the following location to avoid any file sharing conflicts:
   • (Windows) C:\Program Files
   • (Linux) /opt
3. (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
   
   NoteEnsure 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.Excerpt named installupgradereq was not found in document xwiki:IT-Operations-Management.Operations-Management.BMC-TrueSight-Operations-Management.TSOMD113.Planning.Planning-the-Presentation-Server-deployment.System-requirements-for-Presentation-Server.WebHome.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.
4. Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.
5. Review the welcome page, and click Next.
6. Read the license agreement, agree to the terms, and click Next. 

7. Select the Custom installation type, and click Next.

8. 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.

9. 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.
10. Disable the high-availability configuration settings. 

11. 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.

    
    

    

12. 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.
13. 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.
14. Preview the details, and verify the configurations.
15. 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.
16. 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
17. Click Done to exit the installation program.
18. Verify that the following environment variable points to the TrueSight Presentation Server installation path:
    • (Windows) %TRUESIGHTPSERVER_HOME%
    • (Linux) $TRUESIGHTPSERVER_HOME
19. 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
20. 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
21. (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.

       ExampleIf 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

    NoteIf 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:

    1. Navigate to the following location:
       • (Windows) TrueSightPServer\truesightpserver\bin
       • (Linux) TrueSightPServer/truesightpserver/bin
    2. Run the tssh properties set csrfFilter false command.
    3. Run the tssh properties reload command.
22. Define the Presentation Server URL using the following format, and launch the application in a browser:
    • (Windows) http(s)://<TSPS_FQDN>
    • (Linux) http(s)://<TSPS_FQDN>:<tomcat_port>
23. Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.The TrueSight console opens.Your installation is complete.

Troubleshooting installation issues

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

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.