OVNPM 1.5.2 - Performance Monitor User and Installation Guide

HP Performance Monitor: Overview 8
1-5 HP Performance Monitor Components
From the architectural point of view, Performance Monitor architecture can be grouped into the following
categories:
• Components on the HP NonStop Host
• Components on the Windows Workstation
1-5-1 HP Performance Monitor Components on the HP NonStop Server
• Collect Manager: Basic Collectors collect the information from the Measure subsystem and send it to the
Collect Manager. One Basic Collector is present per CPU. The Collect Manager aggregates the collected
data, builds new counters/metrics as per the Measure counters, and sends them to the Database Reader.
• Database Reader: It reads the data from the Collect Manager and in turn respond with data to the TCP
Transport Server on the basis of the request.
• TCP Transport Server: This server receives the queries from the Performance Monitor Transport service on
the front-end environment and passes the same to the Database Reader. The TCP Transport Server
component is also responsible for receiving the responses from the Database Reader and forwarding it
back to the Performance Monitor Transport service on the PC through a TCP/IP link.
NOTE: The TCP Transport Server should not be confused with the TCPIP Transport Process ($ztc(nn))
which is the system component.
NOTE: Performance Monitor uses the OVNPM HP NonStop Server components. For details on the
OVNPM HP NonStop Server components, refer to OVNPM Server Management Guide.
1-5-2 HP Performance Monitor Components on Windows Workstation
• PM Transport: This is a windows service that reads the configuration information of the NonStop Server
using a .cfg file and starts transferring the static information corresponding to the given configuration to the
.ic and .dbd files on the client machine. Once the static information is transferred successfully, it starts
sending the performance data to the flat files.
PM Transport service acts as a communication layer to transfer the performance data from the NonStop
Server to a proprietary flat file database on the Windows client computers.
NOTE: The static information (domain, their instances and metric details) is stored in the database to
assist in further data logging, analysis and stat calculation.
• Flat DB: This database contains the proprietary Windows file system based flat files that maintain the
records of the following database:
• Insight Data Files: These are the short-term data files with a granularity of a minimum of 30 seconds or
15 seconds, based on the collect interval. One Insight data file is created per day.
• Report Data Files: These present the current system activity in a tabular format. The data files contain the
most consuming processes detected during a collect interval. One Report data file is created per day.