Installing the Presentation Server in the standalone 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) |
| (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 |
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
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=trueargument.- 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)
setup.exe(Linux - as a non-root user)
./setup.binProduction environment with user-specified encryption setting (Windows)
setup.exe –J BMC_TS_KEY_SZ=<128/256>(Linux - as a non-root user)
./setup.bin –J BMC_TS_KEY_SZ=<128/256>Test environment with the default encryption setting (Windows)
setup.exe-J MINIMAL=true(Linux - as a non-root user)
./setup.bin-J MINIMAL=trueTest environment with user-specified encryption setting (Windows)
setup.exe–J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true(Linux - as a non-root user)
./setup.bin–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 Typical installation type.
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.
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.
- Type the FQDN of the host computer on which you have installed Remedy SSO or the load balancer URL.
- 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
- Type the Remedy SSO server superuser password. The Remedy SSO superuser name is Admin.
Select HTTP or HTTPS depending on the Remedy SSO configuration . By default, Remedy SSO is configured in the HTTPS mode.
- 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
Verify the TrueSight Presentation Server status:
- (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run
tssh server statuscommand. - (Linux) Navigate to the TrueSightPServer/truesightpserver/bin directory, and run
./tssh server statuscommand.
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 statuscommand, restart the Presentation Server by running the following command:(Windows)
tssh server start- (Linux)
./tssh server start
- (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run
(Linux only) Register the
BMCTSPSSvcservice by performing the following steps:- As a root user, run the
tssh service register <Non-RootUserName>. This command registers theBMCTSPSSvcservice under the /etc/init.d folder. - (SUSE Linux Enterprise Server only) Run the chkconfig --add BMCTSPSSvc command.
If you restart the TrueSight Presentation Server host without registering the
BMCTSPSSvcservice, 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:
- Ensure that you have read and write permissions for the installedDirectory\truesightpserver\logs\tssh.log file.
- Running the
service BMCTSPSSvc statuscommand.
To start and stop the service, run the following commands:
service BMCTSPSSvc startservice BMCTSPSSvc stop
- As a root user, run the
In an IPv6 environment, comment the following properties and restart the TrueSight Presentation Server:
#vm.args.system.26in the installedDirectory\truesightpserver\conf\custom\csr.conf and installedDirectory\truesightpserver\conf\services\csr.conf files#vm.args.system.18in 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:
- Navigate to the following location:
- (Windows) TrueSightPServer\truesightpserver\bin
- (Linux)TrueSightPServer/truesightpserver/bin
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 HostHoustonIf you have set multiple alias names for the TrueSight Presentation Server host:
tssh properties set tspsProxyHosts HostHouston,HostLondon,HostPune- Run the
tssh properties reloadcommand.
- Navigate to the following location:
(Optional) Do this only if you have installed Remedy SSO using the Remedy Installer:
- Log into the Remedy SSO console as an Admin user.
- From the Realm tab, click the Edit Realm icon for the "*" (asterisk) realm.
- From the Authentication tab, if the Authentication Type is set to AR, change it to Local.
Click Save.
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>
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
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=trueargument.- 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)
setup.exe(Linux - as a non-root user)
./setup.binProduction environment with user-specified encryption setting (Windows)
setup.exe –J BMC_TS_KEY_SZ=<128/256>(Linux - as a non-root user)
./setup.bin –J BMC_TS_KEY_SZ=<128/256>Test environment with the default encryption setting (Windows)
setup.exe-J MINIMAL=true(Linux - as a non-root user)
./setup.bin-J MINIMAL=trueTest environment with user-specified encryption setting (Windows)
setup.exe–J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true(Linux - as a non-root user)
./setup.bin–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.
Disable the high-availability configuration settings.
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.
- Type the FQDN of the host computer on which you have installed Remedy SSO or the load balancer URL.
- 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
- Type the Remedy SSO server superuser password. The Remedy SSO superuser name is Admin.
Select HTTP or HTTPS depending on the Remedy SSO configuration . By default, Remedy SSO is configured in the HTTPS mode.
- 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
Verify the TrueSight Presentation Server status:
- (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run
tssh server statuscommand. - (Linux) Navigate to the TrueSightPServer/truesightpserver/bin directory, and run
./tssh server statuscommand.
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 statuscommand, restart the Presentation Server by running the following command:(Windows)
tssh server start- (Linux)
./tssh server start
- (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run
In an IPv6 environment, comment the following properties and restart the TrueSight Presentation Server:
#vm.args.system.26in the installedDirectory\truesightpserver\conf\custom\csr.conf and installedDirectory\truesightpserver\conf\services\csr.conf files#vm.args.system.18in 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:
- Navigate to the following location:
- (Windows) TrueSightPServer\truesightpserver\bin
- (Linux)TrueSightPServer/truesightpserver/bin
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 HostHoustonIf you have set multiple alias names for the TrueSight Presentation Server host:
tssh properties set tspsProxyHosts HostHouston,HostLondon,HostPune- Run the
tssh properties reloadcommand.
- Navigate to the following location:
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>
Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.
The TrueSight console opens.
Your installation is complete.
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.
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.
Comments
step 23(wizard). what happens to get the default out of the box groups and roles into the rsso server?(not truesight rsso) I see no steps for that process so at step 23 you get a not authorized to login for admin. If there is a process to import that data for the truesight realm we need to know that step. Just saying because we are currently on a long support call and support is trying to figure this out so we can move on with the install process.
Hi Anthony Valuikas,
The default user credentials are created at the time of installation of TrueSight Presentation Server. There is no additional step required to create it.
Have you run a migration script from Atrium SSO to Remedy SSO? In that case, your admin user credentials may have changed. Please refer to this topic: Migrating internal user data from Atrium Single Sign-On to Remedy Single Sign-On
Please let us know if you need any further help or give us additional details.
Step 13: Why am I unable to set Tomcat ports for HTTP and HTTPS to 80 and 443 in a Linux environment?
Because you have to be root in order to use any ports lower than 1024. TSPS is installed as a non-root user. We generally use 8080 and 8043.
Of course, that makes sense. Thanks Ellen. Is there a way to change the port designations after installation?
You can't change them to root privileged ports after install. It won't allow the product to start. What is the purpose of changing the ports post install?
I'd prefer TSPS run on reserved HTTP/HTTPS ports 80 and 443.
Hi Ellen Coleman,
Do you have any response to share with David Taggart?
@David Taggart, This is not a BMC restriction this is an operating system restriction. Google: How to open TCP/UDP port 80/443 by a non-root account? There are a couple of methods you will need to check with your Linux Admins and Security team to see if either are allowed in your environment.
Dony, Ellen, thank you both for the feedback. Sometimes a problem is so simple it just stares you in the face. Of course a non-root account can't bind to a privileged port! Thanks, I'll discuss work-arounds with my team.
Log in or register to comment.