BMC TrueSight Presentation Server "consumes events and performance data from the data providers to provide a consolidated set of views for monitoring". The diagram shows how it fits in with other BMC TrueSight Operations Management components.
|PresentationServer||Unix, Windows||File, Package||Instance based|
The patterns discovers Presentation Server deployed on both Unix and Windows platforms .
The trigger process is given a simple identification mapping:
The pattern attempts to find the installation root from the trigger process arguments and then use that to find file version.txt . Version information can be obtained from this file.
If the pattern cannot find version.txt, it tries to parse ProductRegistry.xml using product key productTrueSightPServer
The pattern also looks for the version information in the package which matches the following regular expression:
The PresentationServer pattern triggers on the key JAVA process.
The PresentationServer pattern creates an instance-based Software Instance with the key based on configuration directory,type and host key.
The image below is an example of software context view of the PresentationServer and related software:
The pattern creates following relationships:
A client/server link is created between BMC Atrium SSO and Presentation server. Presentation server is the client in this link.
A client/server link is created with the client components of TrueSight (BMC TrueSight Infrastructure Manager, BMC TrueSight Application Visibility Manager Portal and BMC TrueSight IT Data Analytics Server) where Presentation Server is the server.
Subject Matter Expert input will be welcome on any other potential approaches not discussed to improving product versioning coverage and depth of PresentationServer model.
There are no known open issues with this pattern.