Introduction
The upgrade of TrueSight Presentation Server to version 11.3.03 while Monitoring Studio X Component is already installed and configured in your environment will prevent the proper loading of the Monitoring Studio X Component in TrueSight:
- The TrueSight interface no longer shows links to Monitoring Studio X
- The Component page no longer lists Monitoring Studio X
Problem
The problem is that the upgrade script inappropriately adds entries in the /opt/bmc/TrueSightPServer/truesightpserver/conf/custom/csr.conf configuration file, that override the Monitoring Studio X Component’s default entries in /opt/bmc/TrueSightPServer/truesightpserver/conf/services/csr.conf.
Solution
To fix the problem, edit the /opt/bmc/TrueSightPServer/truesightpserver/conf/services/csr.conf and search for these 2 lines:
vm.args.classpath.282="${truesight.home}/lib/studio-rest-gateway.jar"
vm.args.classpath.283="${truesight.home}/lib/studio-tsps-core.jar"
Note: The numbers may vary depending on your environment.
Replace the entry numbers (282 and 283 in the above example) with numbers that are not listed in either this file (./conf/services/csr.conf) and ./conf/custom/csr.conf. In a typical setup, replacing 282 and 283 with 287 and 288 will work:
vm.args.classpath.287="${truesight.home}/lib/studio-rest-gateway.jar"
vm.args.classpath.288="${truesight.home}/lib/studio-tsps-core.jar"
Then restart TrueSight Presentation Server with the below commands:
$ ./tssh server stop
$ ./tssh server start
Everything should work as expected after the restart and a refresh the TrueSight interface in your browser.
Related Topics
- Monitoring Studio X: HTTP Proxy Authentication Fails When Using Java 8 Update 111 or Later
- Monitoring Studio X Unexpectedly Hangs or Consumes High CPU When Running a JRE Higher Than 8
- Embedding a File in a Monitoring Studio X Template
- How to display the HTTP Status parameter in Monitoring Studio X
- KMs Report "Collection Hub is not started. Cannot send the query"