Performing the Presentation Server installation

You can use this procedure to install the TrueSight Presentation Server with the installation wizard, or you can perform a silent installation

You can install the TrueSight Presentation Server by performing a typical installation or a custom installation. typical installation is recommended for installing the TrueSight Presentation Server with the default settings. If you want to change the default settings used for the product installation, then you need to perform a custom installation.

The following sections are included:


Before you begin

Complete the following items:

  • Ensure that the computer on which you are installing the product adheres to the hardware, operating system, platform, and software requirements listed in System requirements.
  • Ensure that the computer on which you are installing the product adheres to the requirements described in Preparing for the Presentation Server installation.
  • Complete or review the information in the installation worksheet for the TrueSight Presentation Server. The default values used during the installation process are entered in the installation worksheet.
  • Ensure that you downloaded the installation files for TrueSight Presentation Server and extracted the contents of the zipped distribution file to an appropriate directory on the computer where the TrueSight Presentation Server will be installed.

Permissions required for a non-root user on Linux

On Linux computers, you can install the TrueSight Presentation Server only as a non-root user. However, the root user must provide the read, write, and execute permissions to the non-root user for the following directories: 

  • Directory that contains all the installation files
  • Destination directory
  • /tmp and /var/tmp directories
  • /etc directory
  • /opt/bmc directory

Encryption settings

The TrueSight Presentation Server uses 256-bit SSL encryption, by default. Due to import regulations in some countries, AES 256-bit encryption is not allowed. You select the appropriate encryption key size when you invoke the installer; otherwise, the installer uses the default 256-bit SSL encryption.

In a command line, navigate to the Disk1 folder in the installation file structure and enter the following command to change the encryption key size:

  • (Windows) setup.exe –J BMC_TS_KEY_SZ=<128/256>

  • (Linux) ./setup.bin –J BMC_TS_KEY_SZ=<128/256>

    128 is AES 128-bit encryption key
    256 is AES 256-bit encryption key

To perform a typical installation of the TrueSight Presentation Server

A typical installation is recommended for installing the TrueSight Presentation Server with the default settings. 

Note

During a typical installation, the TrueSight Presentation Server is installed in the following default directory:

  • (Windows) \BMC Software\TrueSightPServer

  • (Linux) /opt/bmc/TrueSightPServer

 

  1. Launch the installation wizard:
    • (Windows) As an administrator user, navigate to Windows\Disk1 and double-click install.cmd.

    • (Linux) As a non-root user, navigate to Linux/Disk1 and run install.sh.

      Note

      Ensure that you have set the DISPLAY environment variable.

  2. On the Welcome page, click Next.
  3. On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and click Next
    If you do not agree to the terms of the license agreement, the installation process will not continue.
  4. On the Installation Type page, select Typical Install
  5. On the Listening Address Configuration page, confirm the Fully Qualified Domain Name (FQDN) of your localhost. 
  6. This Fully Qualified Domain Name (FQDN) is detected by the installer. You can enter an alternative, local FQDN, but this field cannot be empty to continue with the installation. Other TrueSight components use the FQDN to connect with the TrueSight Presentation Server.
    Make sure that you do not manually enter any IP address in the FQDN field. 

    Important

    The TrueSight Presentation Server domain should be same as the cookie domain configured on the Remedy Single Sign-On server.

  7. On the database installation credentials page, enter a unique name for the user and set a password for the PostgreSQL database, and then click Next
    The Installer creates a new database user using this username and password.

    Notes

    • The database username and password cannot exceed 30 characters.
    • On Windows systems, if you do not use the default database port number, only use port numbers between 1 and 65535.
    • On Linux systems, if you do not use the default database port number, only use port numbers between 1024 and 65535.
  8. On the BMC Remedy Single Sign-On Server Settings page, enter the following details for the Remedy Single Sign-On server and then click Next.

    • Enter the Fully Qualified Domain Name (FQDN) of the Remedy Single Sign-On server installed on the system. 
    • Use the port number of the Remedy Single Sign-On server installed on the system. The default port number is 448 for HTTPS and 88 for HTTP.
    • Enter the Remedy Single Sign-On server super user password. The Single Sign-On super username is Admin.
    • Select a protocol. The options are: HTTPS or HTTP. By default HTTPS is selected.

    The Port and Protocol details mentioned here are related only to the Tomcat details configured on the Remedy SSO server.

    If your Remedy Single Sign-On server has a private certificate, you must import the certificate into the TrueSight Presentation Server. To import the certificate, select Yes and browse to the path where you have stored the certificate.

  9. Review the installation details.

    • If any of the details need to be changed, click Previous to view previous screens and change the relevant details.
    • If the details are correct, click Install.

  10. (Optional) On the Installation Summary page, you can click View Log to view the installation logs, or go to:

    • (Windows) Default directory: \Temp\truesightpserver_install_log.txt

    • (Linux) Default directory: /tmp/truesightpserver_install_log.txt

  11. Click Done to exit the installation wizard.

Note

If the installation fails, you must uninstall what has already been installed before rerunning the installation wizard. For more information about the uninstallation process, see Performing the Presentation Server uninstallation.

To perform a custom installation of the TrueSight Presentation Server

  1. Launch the installation wizard:
    • (Windows) Navigate to Windows\Disk1 and double-click install.cmd.

    • (Linux) As a non-root user, navigate to Linux/Disk1 and run install.sh.

      Note

      Ensure that you have set the DISPLAY environment variable.

  2. On the Welcome page, click Next.
  3. On the Installation Type page, select the installation type as Custom Install

  4. On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and click Next
    If you do not agree to the terms of the license agreement, the installation process will not continue.
  5. On the Directory Selection page, the system displays the available space on the current drive and the amount of space required. The Destination Directory box displays the default path for the installation directory.
    Retain the default directory or click Browse to select a directory, and click Next.

    Ensure that the path for the installation directory does not exceed 125 characters and the directory is empty.

    • (Windows) Default directory: \BMC Software\TrueSightPServer

    • (Linux) Default directory: /opt/bmc/TrueSightPServer

  6. On the Listening Address Configuration page, confirm the Fully Qualified Domain Name (FQDN) of your localhost. 
    This
     Fully Qualified Domain Name (FQDN) is detected by the installer. You can enter an alternative, local FQDN, but this field cannot be empty to continue with the installation. Other TrueSight components use the FQDN to connect with the TrueSight Presentation Server. 

    Important

    The TrueSight Presentation Server domain should be same as the cookie domain configured on the Remedy Single Sign-On server.

  7. On the TrueSight Presentation Server High Availability page, select Enabled to enter the required details; otherwise, select Disabled and click Next.

  8. (Optional) If you enabled the High Availability option, Select Primary Server or upload a configuration for the Secondary Server and then click Next

    FieldDescription

    Primary Server

    Note: If you do not use the default High Availability port numbers, only use port numbers between 1024 and 65535.

    Server Pair Name

    Elasticsearch cluster name for one node (server), or more nodes, that holds all of the data, and provides federated indexing and search capabilities across all nodes.

    The default value for the cluster name is "truesight". You can change this name to reflect the logical group name of the cluster.

    Cache Replication PortPort number for the primary server cache replication. The default port is 7800.
    Control PortPort number for the primary server control. The 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.

    Important

    The TrueSight Presentation Server domain should be same as the cookie domain configured on the Remedy Single Sign-On server.

    Secondary Server Database Port

    Port number for the secondary server database port. The default port is 5432.

    Note

    Ensure that you use the same database port number for both the primary and secondary servers.

    Secondary Cache Replication PortPort number for the secondary server cache replication. The default port is 7800.
    Secondary Control PortPort number for the secondary server control. The default port is 8800.
    Secondary Server
    High Availability Configuration File

    Path to upload the HA configuration file. The ha-shared.conf file is generated in the <Primary Server installation directory>\truesightpserver\conf directory. Copy this file from the primary server host to the secondary server host. Enter or browse to the file path.

    Note

    If you have imported the Single Sign-On SSL certificate during the primary server installation, you must copy this certificate in the same file path of the HA configuration file. When you do this, the certificate is imported automatically during the secondary server installation.


     

    Any event raised in the TrueSight Presentation Server is set in the Primary Server. The Secondary Server maintains a constantly updated cache memory of the TrueSight Presentation Server activity.

  9. On the TrueSight Presentation Server Port Settings page, use the default settings for the Tomcat Apache Server, Elasticsearch, and Event Ingress ports and then click Next
    You can enter different port settings, but confirm that the new ports are available. 

    Notes

    • On Windows systems, if you do not use the default port numbers, only use port numbers between 1 and 65535.
    • On Linux systems, if you do not use the default port numbers, only use port numbers between 1024 and 65535.
  10. On the database installation credentials page, enter a unique name for the user and set a password for the PostgreSQL database, and then click Next
    The installer creates a new database user using this username and password. 

    Notes

    • The database username and password cannot exceed 30 characters.
    • On Windows systems, if you do not use the default database port number, only use port numbers between 1 and 65535.
    • On Linux systems, if you do not use the default database port number, only use port numbers between 1024 and 65535.
  11. On the Remedy Single Sign-On Server Settings page, enter the following details for the Remedy Single Sign-On server and then click Next

    • Enter the Fully Qualified Domain Name (FQDN) of the Remedy Single Sign-On server installed on the system. 
    • Use the port number of the Remedy Single Sign-On server installed on the system. The default port number is 448 for HTTPS and 88 for HTTP.
    • Enter the Remedy Single Sign-On server super user password. The Single Sign-On super username is Admin.
    • Select a protocol. It is either HTTPS or HTTP. By default HTTPS is selected.

      The Port and Protocol details mentioned here are related only to the Tomcat details configured on the Remedy SSO server.

      If your Single Sign-On server has the custom CA certificate, you must import the certificate in the TrueSight Presentation Server. To import the certificate, select Yes and browse to the path where you have stored the certificate.

  12. Review the installation details.

    • If any of the details need to be changed, click Previous to view previous screens and change the relevant details.
    • If the details are correct, click Install.

  13. (Optional) On the Installation Summary page, you can click View Log to view the installation logs, or go to:

    • (Windows) Default directory: \Temp\truesightpserver_install_log.txt

    • (Linux) Default directory: /tmp/truesightpserver_install_log.txt.

  14. Click Done to exit the installation wizard.

Note

If you restart a TrueSight Presentation Server Linux host without registering the BMCTSPSSvc service, the processes do not come up and you need to start the TrueSight Presentation Server manually.


Post-installation tasks

Perform the following tasks after installing the TrueSight Presentation Server:

  • After installing the component products, you must identify data providers as components in the TrueSight Presentation Server. This connection enables the TrueSight Presentation Server to receive data from its component parts. You can connect components as you add them, or when you finish adding all components.
  • (Linux) Register the TrueSight Presentation Server service for non-root users:
    1. Log in as a root user on the computer on which the TrueSight Presentation Server is installed.
    2. From the <installedDirectory>/truesightpserver/bin directory, run the following command to register the service:
      ./tssh service register <nonrootUserName>
    3. (SUSE Linux Enterprise Server only) In addition, run the following command:
      chkconfig --add BMCTSPSSvc

      The BMCTSPSSvc service is located at /etc/init.d

    4. Ensure that you have read and write permissions for the installedDirectory\truesightpserver\logs\tssh.log file before you run the following commands.
    5. Check whether the service is registered by running the following command:
      service BMCTSPSSvc status
    6. To start and stop the service, run the following commands:
      service BMCTSPSSvc start
      service BMCTSPSSvc stop 
  • (Optional) On a multi-tenant TrueSight Presentation Server environment, you must enable the msp-deployment parameter. To enable, do the following:

    1. Navigate to the folder based on the operating system on which you installed the TrueSight Presentation Server:

      - (Windows) <Install_Directory>\truesightpserver\modules\tomcat\webapps\ROOT\WEB-INF\classes
      - (Linux) <Install_Directory>/truesightpserver/modules/tomcat/webapps/ROOT/WEB-INF/classes

    2. Open the rsso-agent.properties file.
    3. Uncomment the msp-deployment=true parameter and save.
    4. Navigate to the folder.

      - (Windows) <install_Directory>\truesightpserver\bin
      - (Linux) <install_Directory>/truesightpserver/bin

    5. Run the following commands to restart the TrueSight Presentation Server:
      tssh server stop
      tssh server start

    Notes

    • The msp-deployment=true parameter is commented by default after installing or upgrading a single tenant TrueSight Presentation Server.
    • The msp-deployment=true parameter is enabled by default after upgrading an existing multi-tenant TrueSight Presentation Server.
    • The msp-deployment=true parameter must be uncommented (enabled) after installing a multi-tenant TrueSight Presentation Server.

  • Role-based user access to the features and components that compose TrueSight Operations Management is enabled by persona-based authorization profiles. Each authorization profile is associated with one or more Remedy Single Sign-On Server realms and comprises user groups, roles and permissions, and objects. These authorization profiles determine the features and objects that users can access and monitor. You can use the default authorization profiles as is, or you can modify their attributes. If necessary, you can also create authorization profiles.
  • If you have installed the TrueSight Presentation Server in the high-availability mode, you can configure aliases and hosts to access the TrueSight Presentation Server. For more information, see Configuring the Presentation Server for high availability.

  • 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 file
    • #vm.args.system.18 in the installedDirectory\truesightpserver\conf\custom\idxsrv.conf file
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. James Banks

    I have followed the procedure to "manually copy the TSIMAdmin and the TSIMAgent folders" to "the Presentation Server." It is not clear where "the installation files" should "be visible in the TrueSight console." Opening the "Launch Downloads Console" menu from the Managed Devices launches the Downloads page (https://TSIM/jsp/proactive_downloads.jsp) of the TrueSight Infrastructure Management Server. While the files can be downloaded from the TSIM Console, I do not see the downloads for the Administration Console or the Integration Services available from within the TrueSight Presentation Server console.

    Nov 10, 2017 12:51
  2. Juergen Dannerbauer

    When integrating the Presentation Server with standard RSSO (non prepackaged truesight rsso installer) and you get a blank page after logging in (e.g. with the admin user) you have to remove/comment the following section in File "TrueSightPServer\truesightpserver\modules\tomcat\conf\web.xml":

    Before edit:

    CSRFHeaderRefererCheckFilter com.bmc.truesight.secure.csrf.CSRFHeaderRefererCheckFilter CSRFHeaderRefererCheckFilter /*

    After Edit:

    Please update documentation

    Jan 11, 2018 01:19
    1. Mukta Kirloskar

      Hello Juergen,

      Thank you for your comment. I am working with the team to update the document. I will let you know as soon as the document is updated.

      Regards,

      Mukta

      Jan 12, 2018 12:34
  3. Ali Khoshkar

    in-page link at top does not work, under "typical" or "custom" installation. clicking does nothing

    Jun 22, 2018 02:00
    1. Harihara Subramanian
      Jul 03, 2018 02:19
  4. Ali Khoshkar

    service BMCTSPSSvc start/stop is correct way to stop and start service... its referenced correctly in one area in this page and incorrectly below it as tssh server stop

    Jun 22, 2018 03:27
    1. Harihara Subramanian

      Hi Ali Khoshkar,

      BMCTSPSSvc is applicable only on Linux hosts. For Windows hosts, you need to start or stop the service from MSDTC service window.

      However, TSSH CLI command is applicable for both platforms, it is common, and invokes the services command internally.

      Sasi kishore Karnam and chandrashekara_S@bmc.com - FYA.

      Thanks,

      Hari

      Jul 04, 2018 07:10
      1. Ali Khoshkar

        On my Linux box (followed all your instructions for fresh deployment) TSSH CLI command was not working for me. Only BMCTSPSSvc. Perhaps you need to register the environment variable first (which is a missing step)

        Jul 04, 2018 08:55