Performance Monitor. User and Installation Guide. Part number:

Transcription

1 Performance Monitor User and Installation Guide Part number: Fourth edition: 02/2015

2 Legal notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty: A copy of the specific warranty terms applicable to your Hewlett-Packard product can be obtained from your local Sales and Service Office. Restricted Rights Legend: All rights are reserved. No part of this document may be copied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this material is subject to change without notice. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR for other agencies. HEWLETT-PACKARD COMPANY United States of America Copyright Notices: Copyright Hewlett-Packard Company, all rights reserved. Reproduction, adaptation, or translation of this material without prior written permission is prohibited, except as allowed under the copyright laws. Part Number: Fourth edition: 02/2015 Printing History The printing date and part number of the manual indicate the edition of the manual. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The part number of the manual will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details.

3 Contents Preface Before you Begin... 5 Who Should Read This Guide... 5 Goals of Documentation... 5 Organization Performance Monitor: Overview 1-1 What is Performance Monitor? Feature Benefits Performance Monitor Architecture Performance Monitor Components Performance Monitor Components on the HP NonStop Server Performance Monitor Components on Windows Workstation Installing Performance Monitor 2-1 Prerequisites Database Installation System Requirements Installing Performance Monitor on Windows Overview Installing Performance Monitor Database Post Database Installation Tasks Installing Performance Monitor Application Server Post Installation Steps Upgrading Performance Monitor Getting Started 3-1 Starting Performance Monitor on HP NonStop Server Starting Performance Monitor on Windows Starting Generic Configuration Client Stopping Performance Monitor on Windows Stopping Performance Monitor on HP NonStop Server Working with Generic Configuration Client 4-1 Adding a New Configuration Modifying an Existing Configuration Deleting an Existing Configuration Additional Performance Monitor Configuration Parameters Editing Summary Flag for Domains and Metrics Editing Description for Domains and Metrics Uninstalling Performance Monitor 5-1 Uninstalling Performance Monitor Application Server Uninstalling Performance Monitor Database Performance Monitor Database Schema 6-1 Overview Tables of Database Schema Configuration Tables Metric Data Tables Stat Data Tables... 40

4 Figures Figure 1-1 Performance Monitor Architecture... 8 Figure 2-1 Performance Monitor Application Server Message Box Figure 2-2 Performance Monitor Application Server Setup Welcome Page Figure 2-3 Application Server Setup License Agreement Page Figure 2-4 Application Server Setup Setup Type Page Figure 2-5 Application Server Setup Choose Destination Location Page Figure 2-6 Application Server Setup Choose Destination Location Page Figure 2-7 Application Server Setup Choose Destination Location Page Figure 2-8 Application Server Setup SQL Server Page Figure 2-9 Application Server Setup Check Setup Information Page Figure 2-10 Application Server Setup Host Configuration Page Figure 2-11 Application Server Setup Host Configuration Page Figure 2-12 Additional Host Configurations confirmation box Figure 2-13 Application Server Setup Message Box Figure 2-14 Application Server Setup Setup Completed Page Figure 2-15 Generic Configuration Client Figure 2-16 Metric Summary Detail Dialog Box Figure 4-1 Generic Configuration Client Figure 4-2 Configuration Parameters Figure 4-3 Performance Monitor Message Box Figure 4-4 New Configuration Added Figure 4-5 Configuration Settings Dialog Box Figure 4-6 Performance Monitor Confirmation Box Figure 4-7 Configuration Uninstalled Successfully Message Box Figure 4-8 Metric Summary Detail Dialog Box Figure 4-9 Changes Updated Successfully Message Box Figure 4-10 Domain/Metric Description Update Form Dialog Box Figure 4-11 Domain/Metric Description Update Form Dialog Box Figure 4-12 Changes Updated Successfully Message Box Figure 5-1 Application Server Uninstallation Information Box Figure 5-2 Application Server Uninstallation Confirmation Box Figure 5-3 Application Server Uninstallation Message Box Figure 6-1 Relationship Model of the Performance Monitor Database Components Tables Table 2-1 HOSTTIMEINFO Table 4-1 Generic Configuration Client Parameters Table 6-1 NodeConfig Table 6-2 Domain Map Table 6-3 Domain Table 6-4 Metric Map Table 6-5 Metric Table 6-6 Instance Table 6-7 TrendSummaryMap Table 6-8 Trend Configuration Table 6-9 Domain APPLIDEF Table 6-10 Stat Table Schema... 40

5 Preface The Performance Monitor (PM) is used to track and monitor the activities occurring on the HP NonStop Servers. It can be used to assist you with the planning of upgrades, tracking of processes that need to be optimized, monitoring results of tuning and configuration scenarios, and the understanding of a workload and its effect on resource usage to identify bottlenecks in the NonStop Environments. Bottlenecks can virtually occur anywhere and on any element of the environment. It may be caused by the malfunctioning of resources, systems lacking enough resources or a program that dominates a particular resource. Performance Monitor helps in tracking these bottlenecks and allows you to take the appropriate proactive actions. Before you Begin Before reading the documentation, you are expected to have a basic understanding of the Windows Operating System, as well as the HP NonStop environment. Who Should Read This Guide The target audiences for the Performance Monitor User and Installation Guide are the people working in the systems operation/support groups and performance/capacity planning analysts, responsible for using Performance Monitor for managing the HP NonStop environment. Goals of Documentation After reading this guide, you should know the following. Performance Monitor and its Components. Features and benefits of Performance Monitor. Performance Monitor architecture and the information flow between Performance Monitor and the HP NonStop environment. Procedure to install and uninstall Performance Monitor. Introduction to the Performance Monitor Client and its working. Database Schema of Performance Monitor. Organization The guide is organized as follows: S. No. Chapter Name Description Chapter 1. Performance Monitor: Overview Introduces Performance Monitor and its components. It also surveys the main features of Performance Monitor and highlights the advantages this software offers. Chapter 2. Installing Performance Monitor Specifies the prerequisites and the steps required to install the Performance Monitor. Chapter 3. Getting Started This section provides steps on how to start and stop various Performance Monitor components. Chapter 4. Generic Configuration Client Provides information about the Generic Configuration Client and its various parameters. The chapter also provides information about how to create and maintain configurations using the tool. Chapter 5. Uninstalling Performance Monitor Specifies the steps required to uninstall Performance Monitor. Chapter 6. Performance Monitor Database Schema Describes the Database Schema and the relationship between its various components. Preface 5

6 1 Performance Monitor: Overview This chapter explains what is Performance Monitor and the features and benefits that this software offers. 1-1 What is Performance Monitor? 1-2 Feature The Performance Monitor (PM) tool delivers easy-to-use performance monitoring and tracking for the HP NonStop environment. Built to manage environments of all sizes, Performance Monitor scales with the rapid growth of your environment and expands with your monitoring needs. It provides a highly flexible solution that allows the measurement of your service level standards and planning for future business needs. The mission for Performance Monitor is to deliver 100% availability of all HP NonStop resources and to keep a close eye on the performance of devices, servers and applications in your infrastructure. Real-Time Supervision: Monitors and analyzes real-time, in-depth performance metrics on the HP NonStop Server and pinpoints production problems that have just occurred, before service degradation occurs. Detects Network Bottlenecks: Performance monitor detects network bottlenecks, and identifies resources in short supply. In-Depth Analysis: It enables the system support to investigate production anomalies and eliminate recurring incidents by pinpointing their causes. It also enables advanced monitoring for correlated events, sustained conditions, and complex combinations of states. Trend Analysis: Performance Monitor maintains statistics from yearly level down to five minute levels to assist high level management in DSS and permits high level management to gain control over change and optimize the return on investment. Identifying Server Performance Problems: Performance Monitor provides advanced features for analyzing Server performance. Performance Monitor counters can be used to figure out exactly how well the server is performing and which of the server s components are acting as a bottleneck. Smart Capacity Planning: Performance Monitor provides enterprise capacity planning by automatically capturing historical performance metrics. With Performance Monitor, you can make sure that resources are in place to handle an increasing number of requests as the number of users or interactions increase. Resource Workloads: Performance Monitor enables you to understand and plan for the effects of the workloads on resources. Easy Integration: Performance Monitor can be easily integrated with any web browser for data visualization and performance reporting. Easy Do-it-Yourself Installation: Gets you up and running in no time with Performance Monitor s do-ityourself installation and deployment. User Management: Provides thorough User management by providing detailed User and Task operation log records. Is Also Able To Monitors the optimum utilization of network resources and devices Monitors critical events Provides large-scaled network manageability Export the reports flexibly and conveniently Identifies busiest Process information Enables Load Balancing activities Performance Monitor: Overview 6

7 1-3 Benefits Following are the benefits of Performance Monitor. Increased Service Availability: It brings information critical to managing Service Level Agreements on the HP NonStop system. System availability and performance will be improved, as monitoring will highlight potential breaches in Service Level Agreements. Enhanced Productivity: The consolidate view can be used to enhance the overall productivity of the business. Managers and administrators can access graphical views from anywhere anytime that helps them to keep a close eye on their production environment. Enhanced Performance Monitoring: Performance Monitor stores near real-time performance data that includes numerous metrics on various types of objects at a minimum 15 second interval. This information can be used for web-based data visualization. Resource Management: It provides discovery of NonStop Server resources for their management. Resources such as CPU, DISK, Controllers, and Processes can be monitored for their availability as well as resource consumption. Failure in any of the defined resource components is presented immediately. Historical Trend Analysis and Capacity Planning: The Performance Monitor can be used to generate the trend data which can be retrieved to perform the trend analysis and plan future needs. Improved Event Management: It has the ability to detect performance exception conditions on the basis of either Application and/or System performance metrics in the database. Daily Production Control: It allows the continuous improvement of production quality and an increase in service levels. It also assists in system tuning for continuous improvement in availability and response times. Performance Monitor: Overview 7

8 1-4 Performance Monitor Architecture The following figures show the consolidated Performance Monitor data flow between the HP NonStop environment and the Windows environment. Figure 1-1 Performance Monitor Architecture Performance Monitor: Overview 8

9 1-5 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 Performance Monitor Components on the HP NonStop Server The Performance Monitor components on the HP NonStop include: Collect Manager: The 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 Manager: The Database Manger provides the data feed for opened views and dashboards in Display Agent. It saves the collect data, calculates and saves the interval aggregation for Insight and Trend, monitors the thresholds, and manages Insight and Report retention period. TCP Transport Server: The TCP Transport 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 Performance Monitor Components on Windows Workstation PM Transport: PM Transport 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: The Flat DB contains the proprietary Windows file system based flat files that maintain the records of the following database: Insight Data Files: The Insight Data files 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: The Report Data files 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. PM Logger: The PM Logger service is responsible for reading the Flat file database and logging the performance data in the SQL Database. The performance data includes predefined metrics related to domains like cpubusy%, FreeMemory, page-fault. Summarization Service: Summary Broker service is a SQL Broker Service that calculates the statistics, for example, MIN, MAX, AVG, over samples of 5 minutes, one hour, daily, weekly, monthly and yearly, for the performance data.pm Logger Service reads the summary detail parameters from the pmlogger.ini file and insert them into the summarization configuration tables (database tables).these parameters are further used by Summary broker service to summarize the performance data. Summarized trend data over various intervals can be used for Trend Analysis and Capacity planning. Performance Monitor: Overview 9

10 2 Installing Performance Monitor This chapter provides information on how to install Performance Monitor on Windows environment. 2-1 Prerequisites 1. Before starting the installation, it is recommended that you exit from any other Windows programs that are running. 2. Microsoft SQL Server 2008/2012 or above is a must to install Performance Monitor Database and Performance Monitor Application Server. 3. Microsoft.NET framework 4.0 should be installed before installing the Application Server. 4. Windows Server 2008/20012 (64 Bit) Operating Systems are supported. 5. MS SQL Server Agent must be running where the MS SQL server is installed for data retention and index fragmentation jobs. 6. Service broker must be enabled in MS SQL Server 2008/2012 for data summarization. 7. Before installing Performance Monitor you should have the following information. a. SQL Server Name and Authentication Type b. For SQL Server Mixed mode authentication type, you need the SQL Server Login ID and password. This login ID must have Database Creator role, Database owner and Public Access rights for the SQL Server Performance Monitor database. c. For Window authentication type, create an SQL Login ID which is same as the Windows Login ID. The DB user must have the DB Owner rights on the SQL Server Performance Monitor. This user is required to have Database Creator rights also in case the Performance Monitor Database is required to be created by the installation program in default locations with default configurations. NOTE: The Database Creator role is only required if the database does not already exist. d. SQL Server TCP/IP port where Microsoft SQL Server is listening. The default port is The same port should be used for Performance Monitor Database and Application Server installation. If the SQL Server is listening on a port other than the default port, enter the SQL Server name in the <SQLServer_Name>,<Port_Number> format while installing Performance Monitor Application Server and Database. e. In case of Windows Authentication, the user ID which is being used for installing the Application Server, must have Logon as a service rights before 8. Backend environment of OVNPM or above must be up and running before installing Performance Monitor Database and Performance Monitor Application Server. The command sv_status must be used to get the TCP Transport Server port used. Use the SCF to obtains the host addresses of the TCPIP Transport Process $ztc(nn) used by the TCP Transport Server. 9. In case you do not have System Administrative rights on the SQL Server login ID, the SQL login ID should have database owner and public access rights of InsightCollectDB before installing Performance Monitor Application Server. 10. In case you do not have System Administrative rights on the SQL Server, the login ID used to create the database must have Database Creator role allocated before installing InsightCollectDB Database. If you have already created the InsightCollectDB Database and you do not want to give Database Creator rights to appropriate SQL user, the SQL Login ID must have database owner and Public Access rights on the InsightCollectDB Database before installing the Database Database Installation System Requirements The database system s hardware requirement will depend on your database configuration. The information provided in this section is based on a sample scenario done while doing performance benchmarking of the Performance Monitor product. Intel Xenon Processor 3GHz Memory 2 GB (Minimum) (Recommended 4GB or Above) Disk Space 120 GB Installing Performance Monitor 10

11 The system requirements listed above are recommended for the following sample scenario. Number of objects(instances) for which insight/report collection is done for the retention period (3 days) ~ 2000 Average number of metrics per domain ~ 20 Insight/Report Data Collection interval Number of objects(instances) for which the default trend summarization is generated 15 seconds ~ 1000 Number of concurrent users logged on to DV ~ 20 Default out of the box summarization retention scheme: Five minute summary with retention period Hourly summary with retention period Daily summary with retention period Weekly summary with retention period Monthly summary with retention period Yearly summary with retention period 5 Days 7 Days 40 Days 300 Days 400 Days 900 Days Installing Performance Monitor 11

12 2-2 Installing Performance Monitor on Windows Overview Installing Performance Monitor involves installing the following components in the same sequence. 1. Performance Monitor Database: This involves installing the Performance Monitor database, remotely or locally. 2. Performance Monitor Application Server: This involves installing the Performance Monitor Application Server Installing Performance Monitor Database To install the Performance Monitor Database, perform the following steps. 1. In the SQL Server Management Studio, execute the Step1-InsightCollectDB.sql script. The PM database will be created in the name of INSIGHTCOLLECTDB. 2. Now execute the Step2-UpdateMetricDescription.sql script, to update the metric descriptions in the database Post Database Installation Tasks To configure OnDemandDataRetention for any table on demand, use the following parameters. Name of the SQL Procedure: OnDemandDataRetention Parameter List Tablename: The name if the table that is intended for retention retentionperiod: The retention period to be considered in Number of days batchsize: The Size of the batch for each delete execution Manual Query to execute the Procedure on SQL Management Studio: OnDemandDataRetention tablename,retentionperiod,batchsize If user wants he can create a SQL job and schedule the same statement in the SQL Job. IMPORTANT: The Microsoft SQL Server user must have the sysadmin server role in order to create the stored procedures and jobs. Installing Performance Monitor 12

13 2-2-4 Installing Performance Monitor Application Server To install Performance Monitor Application Server, perform the following steps. 1. Double-click the PerformanceMonitor_ApplicationServerInstallation.exe to start the installation process. The InstallShield prepares the Setup program for use and the Performance Monitor Application Server message box is displayed. Figure 2-1 Performance Monitor Application Server Message Box 2. Before installing Performance Monitor Application Server make sure that the Performance Monitor Database is installed on the network. If it is installed on the network, click the OK button to continue. The Performance Monitor Application Server Setup Welcome page is displayed. Figure 2-2 Performance Monitor Application Server Setup Welcome Page Installing Performance Monitor 13

14 3. Click the Next button. The License Agreement page is displayed. Figure 2-3 Application Server Setup License Agreement Page 4. Review the software license agreement and click the Yes button. The Setup Type page is displayed. Figure 2-4 Application Server Setup Setup Type Page 5. On the Setup Type page, select the type of setup required. You can select any of the following options. Complete: Select this option to install full functionality of the software. If you select this option, all the Performance Monitor components are selected for installation. Custom: Select this option to install to select the Performance Monitor components to be installed. This option is recommended for advanced users. Most users are recommended to use the Complete setup type 6. The page also displays the default path were the Performance Monitor Application Server will be installed. To select a path other than that specified, use the Browse button. Installing Performance Monitor 14

15 7. Click the Next button to continue. The Choose Destination Location page is displayed. Figure 2-5 Application Server Setup Choose Destination Location Page 8. Select the location where the configuration files folder for PM Transport and PM Logger will be created. This folder should have write/file creation permissions for the user who uses the Configuration Client to modify configuration information. You can also browse for the cfg folder using the Browse button. 9. Click the Next button. The Choose Destination Location Log Files page is displayed. Figure 2-6 Application Server Setup Choose Destination Location Page 10. Select the Performance Monitor Log file folder location. This folder should have write/file creation/deletion permissions to the user under whose credentials the services are started. You can browse for the log folder using the Browse button. Installing Performance Monitor 15

16 11. Click the Next button. The Choose Destination Location Data Files page is displayed. Figure 2-7 Application Server Setup Choose Destination Location Page 12. Select the location where Performance Monitor Data folder will be created. This folder should have write/file creation/deletion permissions to the user under whose credentials the PM Transport service is started. You can browse for the data folder using the Browse button. 13. Click the Next button. The SQL Server page is displayed. Figure 2-8 Application Server Setup SQL Server Page 14. Select the Database Server where the Performance Monitor Database (InsightCollectDB) exists using the Database Server field. You can also browse for the Database Server using the Browse button. The default port used by the SQL Server is In case the SQL Server is listening on a port other than the default port, specify the information in the <SQL Server>,<Port Number>format. 15. After selecting the Database Server, select the authentication type: Windows authentication or SQL Server authentication, using the corresponding radio buttons. Specify the Login ID and the Password if you select the SQL Server authentication method. Installing Performance Monitor 16

17 16. Click the Next button. The Check Setup Information page s displayed with the current settings, which have been selected so far. Figure 2-9 Application Server Setup Check Setup Information Page 17. In case you want to change any of the settings, you can do so by going back to the particular page before you start copying the program files. NOTE: You should check the location of the directory where Performance Monitor Application Server is to be installed. In case the location has to be changed after installation, you will have to reinstall the software. 18. Click the Next button to continue with the Setup process. The program begins copying files to the directory specified. The Host Configuration page is displayed. Figure 2-10 Application Server Setup Host Configuration Page Installing Performance Monitor 17

18 19. Enter the Configuration Name and IP Address /Host Name in the respective fields and click the Next button to continue. The Host Configuration page is displayed again. Figure 2-11 Application Server Setup Host Configuration Page 20. Enter the HP NonStop Node Name and Port number in the corresponding fields and click the Next button to continue. The Additional Host Configurations confirmation box is displayed. Figure 2-12 Additional Host Configurations confirmation box 21. To add more configurations click the Yes button. To continue without adding more nodes, click the No button. NOTE: By default the Transaction Data Retention Period is set to 7 days. This value can be modified after the installation, if required. The Application Server Setup message box is displayed, prompting you to execute the UpdateSummaryFlag.sql script at the C:\Program Files (x86)\ovnpm\performance Monitor\Common location once the installation and configuration is complete. Figure 2-13 Application Server Setup Message Box Installing Performance Monitor 18

19 The Setup Completed page is displayed. Figure 2-14 Application Server Setup Setup Completed Page 22. Click the Finish button to complete the Setup process. NOTE: Once PM Transport and PM Logger Service start, Execute SQL Scripts generated by PM Logger at C:\Program Files (x86)\ovnpm\performance Monitor\cfg on the Performance Monitor Database (INSIGHTCOLLECTDB) Updating the HOSTTIMEINFO Table The InsightCollectDBDatabase has the HOSTTIMEINFO table that contains information for the offsets of each HP NonStop node from UTC in minutes through different time ranges around the year taking into account the Daylight Savings Time information. You need to make changes in the table according to your requirements. The example below displays the records in the HOSTTIMEINFO table for year 2007, 2008 and 2009 for NODE1. Let s consider that NODE1 is in the Pacific Time zone and they have DST applied. Table 2-1 HOSTTIMEINFO NodeName TimeRangeBegin TimeRangeEnd OffsetFromGmt \NODE :00: :59: \NODE :00: :59: \NODE :00: :59: \NODE :00: :59: Where NODE1 is the host name and time will depend upon where the host server reside. From March 11th 2007 till November 4th 2007 the local time on the node \NODE1 will have an offset of -420 minutes from UTC. During DST (summer months), clocks are turned forward an hour, effectively moving an hour of daylight from the morning to the evening. In the United States, clocks change at 2:00 a.m. local time. In spring, clocks spring forward from 1:59 a.m. to 3:00 a.m.; in fall, clocks fall back from 1:59 a.m. to 1:00 a.m. In EU, clocks change at 1:00 a.m. Universal Time. In spring, clocks spring forward from 12:59 a.m. to 2:00 a.m.; in fall, clocks fall back from 1:59 a.m. to 1:00 a.m. NOTE: Refer to DST changes in other countries around the globe. Installing Performance Monitor 19

20 2-3 Post Installation Steps Perform the following steps once you have installed PM Application Server and Database. 1. Start the Performance Monitor Services. For this, click Start Programs HP OVNPM Performance Monitor Application Server Start Performance Monitor Services. 2. Execute the database scripts generated by PM Logger at cfg folder at C:\Program Files (x86)\ovnpm\performance Monitor\cfg for adding new domains and metrics to the INSIGHTCOLLECTDB. 3. To enable Summarization, open the Generic Configuration Client, select the Configuration name, and select the Edit Summary Flag option from the Configuration menu. Figure 2-15 Generic Configuration Client Installing Performance Monitor 20

21 4. In the displayed Metric Summary Detail dialog box, select the Select Summary Flag for all metrics checkbox and click the Save button. Figure 2-16 Metric Summary Detail Dialog Box 5. Execute the Step2-UpdateMetricDescription.sql on the INSIGHTCOLLECTDB provided with the package. Installing Performance Monitor 21

22 2-4 Upgrading Performance Monitor This section explains the procedure to upgrade from a previous version of Performance Monitor. 1. Stop the Performance Monitor services using the Start Programs HP OVNPM Performance Monitor Application Server Stop Performance Monitor Services. 2. Take a backup of the Performance Monitor database on the Microsoft SQL Server. 3. Manually delete the sp_dba_defragindexes stored procedure from the Master database. 4. To upgrade the Performance Monitor Database (InsightCollectDB), run the Step1- InsightCollectDB_Upgrade_1.2.3.sql upgrade script. 5. To upgrade the Performance Monitor Application Server, run the PerformanceMonitor_ApplicationServerInstallation.exe, and proceed as per the InstallShield Wizard. 6. Update the HOSTTIMEINFO table in the InsightCollectDB in case a new configuration is added. 7. Run Step2-UpdateMetricDescription.sql to upgrade the metric description. 8. Start the Performance Monitor services using the Start Programs HP OVNPM Performance Monitor Application Server Start Performance Monitor Services. NOTE: Once PM Transport and PM Logger Service start, execute the SQL Scripts generated by PM Logger at C:\Program Files (x86)\esq\opennet\performance Monitor\cfg on the Performance Monitor Database (INSIGHTCOLLECTDB), and update Summarization as explained in the Post Installation Steps section. Installing Performance Monitor 22

23 3 Getting Started This chapter details the steps for starting and checking status of various Performance Monitor components. 3-1 Starting Performance Monitor on HP NonStop Server Performance Monitor uses the OVNPM HP NonStop components. For details on how to start and stop OVNPM Server components, refer to the OVNPM Server Guide. 3-2 Starting Performance Monitor on Windows Start the Performance Monitor Application Server services using the Start Programs HP OVNPM Performance Monitor Application Server Start Performance Monitor services option. 3-3 Starting Generic Configuration Client Use the Start Programs HP OVNPM Performance Monitor Application Server Generic Configuration Client option to access the Generic Configuration Client. 3-4 Stopping Performance Monitor on Windows Stop the Performance Monitor Application Server services using the Start Programs HP OVNPM Performance Monitor Application Server Start Performance Monitor services option. 3-5 Stopping Performance Monitor on HP NonStop Server Performance Monitor uses the OVNPM HP NonStop components. For details on how to stop OVNPM Server components, refer to the OVNPM Server Management Guide. Getting Started 23

24 4 Working with Generic Configuration Client The Generic Configuration Client is an interface, which enables you to edit configuration settings of the Performance Monitor Application Server components. Click Start Programs HP OVNPM Performance Monitor Application Server Generic Configuration Client option to access the Generic Configuration Client. Figure 4-1 Generic Configuration Client You can perform the following tasks using the Generic Configuration Client. 1. Add a New Configuration 2. Edit an Existing Configuration 3. Delete a Configuration 4. Edit Summary Flag for Domains and Metrics 5. Edit Description for Domains and Metrics Working with Generic Configuration Client 24

25 4-1 Adding a New Configuration Perform the following steps to add a new configuration: 1. Click Start Programs HP OVNPM Performance Monitor Application Server Generic Configuration Client option. Right-click Generic Configuration Client, and select the Run as Administrator option from the context menu. The Performance Monitor Generic Configuration Client dialog box is displayed. 2. In the Generic Configuration Client, select the New option from the Configuration drop-down menu. The various configuration parameters are displayed along with the default values in the Performance Monitor dialog box. Figure 4-2 Configuration Parameters 3. Enter the values in the respective configuration parameters, as described in the following table. Table 4-1 Generic Configuration Client Parameters Configuration Parameter Description Default Value Name Host Name Host Address Specifies the Configuration Name Specifies the HP NonStop Node Name Specifies the Host Address Port Specifies the Port number 0 Windows Authentication Enable Data Source Name Specifies that the PM Logger service uses Windows Authentication Mode to connect to the database. It can take the following values: True False Specifies the ODBC Data Source Name False Working with Generic Configuration Client 25

26 Table 4-1 Generic Configuration Client Parameters Configuration Parameter Description Default Value SQL Auth. Username SQL Auth. Password DB Connection Check Interval (secs) Insight Data Collection Enabled Report Data Collection Enabled Data Recovery Enabled Maximum Data Recovery Interval (hours) Maximum Insight Data Retention (days) Data Logging to DB with UTC Timestamp Enabled Five Minute Stat Calculation Enabled Hourly Stat Calculation Enabled Daily Stat Calculation Enabled Monthly Stat Calculation Enabled Yearly Stat Calculation Enabled Specifies the User ID that will be used to connect to Performance database on the SQL Server in case SQL Mixed Mode authentication is used. This is to be left blank in case the Windows Authentication is used. Specifies the password for the login that will be used to connect to Performance database on SQL Server in case SQL Mixed Mode Authentication is used. This is to be left blank in case Windows Authentication mode is used. Specifies the time interval for checking the Database connection Enables Insight data Collection of performance data. It can take the following values: True False It is NOT recommended to turn this off using the False value. Enables Report data Collection of performance data. It can take the following values: True False NOTE: It is NOT recommended to turn this off using the False value. Decides whether to recover lost data or not in case the PM Logger service was not running for certain time duration. It can take the following values: True False In case data recovery is enabled, this parameter specifies the maximum time interval PM Logger will fetch the data for from the flat file database. If the last data collection time is more than this interval, there will be no recovery and collection of live data will start. Specifies the number of days for which the data is to be retained in the SQL Server data tables. Decides whether the data is to be logged with a UTC timestamp or Node LCT timestamp in the SQL Database. Enables the calculation of summarization data at five minute intervals. It can take the following values: True False Enables the calculation of summarization data at each hour. It can take the following values: True False Enables the calculation of daily stat intervals at the end of each day. It can take the following values: True False Enables the calculation of monthly stat intervals at the end of the month. It can take the following values: True False Enables the calculation of yearly stat intervals at the end of the year. It can take the following values: True False 0 False False False 0 0 False False False False False False Working with Generic Configuration Client 26

27 Table 4-1 Generic Configuration Client Parameters Configuration Parameter Description Default Value Weekly Stat Calculation Enabled Enables the calculation of weekly stat intervals at the end of the week. You can also configure the week end as per your business needs. It can take the following values: True False False 4. Click the Save button to save the settings. NOTE: The HOSTTIMEINFO table in the InsightCollectDB should be updated in case a new configuration is added. 5. The Performance Monitor message box is displayed with the information that the configuration has been installed successfully. Figure 4-3 Performance Monitor Message Box 6. Click the OK button. The newly created configuration is displayed in the list, as shown in the following figure. Figure 4-4 New Configuration Added Working with Generic Configuration Client 27

28 4-2 Modifying an Existing Configuration To modify an existing configuration, perform the following steps. 1. Click Start Programs HP OVNPM Performance Monitor Application Server Generic Configuration Client option. Right-click Generic Configuration Client, and select the Run as Administrator option from the context menu. The Performance Monitor Generic Configuration Client dialog box is displayed. 2. From the Generic Configuration Client, select a configuration to be modified. 3. Select the Edit/View option from the Configuration menu. The Configuration Settings dialog box is displayed. Figure 4-5 Configuration Settings Dialog Box 4. Make the necessary changes and click the Save button. Working with Generic Configuration Client 28

29 4-3 Deleting an Existing Configuration To delete an existing configuration, perform the following steps. 1. From the Generic Configuration Client, select a configuration to be modified. 2. Select the Delete option from the Configuration menu. The Deletion Confirmation dialog box is displayed. Figure 4-6 Performance Monitor Confirmation Box 3. Click the Yes button to confirm the deletion of the selected configuration. The Configuration Uninstalled successfully message box is displayed. Figure 4-7 Configuration Uninstalled Successfully Message Box 4. Click the OK button to complete the procedure. 4-4 Additional Performance Monitor Configuration Parameters The following Data retention parameters can be configured for each configuration added in. Configuration Parameter retention report ci retention insight ci Description Specifies the data retention period for Report Data files. The default value is 7 days. Specifies the data retention period for Insight Data files. The default value is 7 days. Working with Generic Configuration Client 29

30 4-5 Editing Summary Flag for Domains and Metrics The Generic Configuration Client enables the user to update the summary flag of any metric/domain. To edit summary flag for domains and metrics, perform the following steps. 1. From the Generic Configuration Client, select a configuration, for which you want to edit summary flags. 2. Select the Edit Summary Flag option from the Configuration menu. The Metric Summary Detail dialog box is displayed. Figure 4-8 Metric Summary Detail Dialog Box 3. To add summary flag for a metric, select the metric, and select the corresponding check box from the Summary Flag column. To select flags for all metrics, select the Select Summary Flag For All Metrics check box. 4. Click the Save button to save your changes. The Changes Updated Successfully message box is displayed. Figure 4-9 Changes Updated Successfully Message Box Working with Generic Configuration Client 30

31 4-6 Editing Description for Domains and Metrics When you install Performance monitor, and start the services, the default Domain and Metric descriptions are not automatically loaded. For this execute the UpdateMetricDescription.sql script provided in the package. Once the default descriptions are loaded, you can edit them through the Generic Configuration Client. To update the description of any Domain and Metric, perform the following steps. 1. From the Generic Configuration Client, select a configuration for which you want to edit the descriptions. 2. Select the Edit Description option from the Configuration menu. The Domain/Metric Description Update Form dialog box is displayed with a list of default descriptions. Figure 4-10 Domain/Metric Description Update Form Dialog Box Working with Generic Configuration Client 31

32 3. From the Select Type drop-down list, select Domain or Metric option, and add the details in the corresponding Description column, as shown in the following figure. Figure 4-11 Domain/Metric Description Update Form Dialog Box 4. Click the Save button to save your changes. The Changes Updated Successfully message box is displayed. Figure 4-12 Changes Updated Successfully Message Box Working with Generic Configuration Client 32

33 5 Uninstalling Performance Monitor This chapter provides instructions on how to uninstall Performance Monitor from the workstation. Uninstalling Performance Monitor on Windows involves uninstalling the following components in the specified sequence. 1. Performance Monitor Application Server 2. Performance Monitor Database 5-1 Uninstalling Performance Monitor Application Server Follow the steps given below to uninstall the Performance Monitor Application Server components from the workstation. 1. Click Start Programs HP OVNPM Performance Monitor Application Server Uninstall Application Server option to start the uninstallation process. The Performance Monitor Application Server information box is displayed with the information that all the Performance Monitor Application Server components running on the system need to be closed. Figure 5-1 Application Server Uninstallation Information Box 2. Click the OK button to continue. The Performance Monitor Application Server Installation confirmation box is displayed asking confirmation for removing the application and its features. Figure 5-2 Application Server Uninstallation Confirmation Box 3. Click the Yes button to continue. The Performance Monitor Application Server Uninstallation message box is displayed. Figure 5-3 Application Server Uninstallation Message Box 4. Click the OK button to complete the process. Uninstalling Performance Monitor 33

34 5-2 Uninstalling Performance Monitor Database To uninstall the Performance Monitor Database components, perform the following steps. Remove the following items manually from the database INSIGHTCOLLECTDB database Jobs (DataRetention_Job and InsightCollect DB_IndexDefrag_Daily_Job) NOTE: It is recommended to restart the computer after complete uninstallation. Uninstalling Performance Monitor 34

35 6 Performance Monitor Database Schema This chapter provides an overview of Performance Monitor database schema, its various components and the relationship model. 6-1 Overview Database schema is the physical layout or the graphical depiction of the database structure. It illustrates the relationship between the various components of the database. Figure 6-1 Relationship Model of the Performance Monitor Database Components Apart from showing the backend information using Domain, Matrices and instances, this database schema also shows the Stat Calculation Schema. Performance Monitor Database Schema 35

36 6-2 Tables of Database Schema The Database schema consists of the following tables: Configuration Tables Metric Data Tables Stat Data Tables Configuration Tables PM Logger collects the HP NonStop configuration information using the Configuration files. These configuration parameters are used to connect to the database. The NonStop Server consists of certain predefined active entities like domains, metrics and instances. The Information in these entities is termed as static information and the tables being used to maintain static information inside InsightCollectDB are called Configuration Tables. Table 6-1 NodeConfig Column Name Data Type Description NodeID Integer Specifies the Node ID NSKConfigId Integer Specifies the NSK Configuration ID NodeName Varchar(30) Specifies the Node Name ConfigName Varchar(30) Specifies the Configuration Name LastCollectTS Datetime Specifies the Last Collected Performance data time stamp LastTix Integer Specifies the last collected Tix Number GMTCollection Integer Specifies whether the data logged to the database is logged with a UTC timestamp or not.this is entirely dependent on the entries in the HOSTTIMEINFO table for the corresponding configuration. RetentionPeriod Integer Specifies the time period in days for which data needs to be retained in the performance data tables. Table 6-2 Domain Map Column Name Data Type Description NodeID Integer Specifies the Node ID DomainId Integer Specifies the Domain ID NSKDomainId Integer Specifies the NSK Domain ID InsightFlag Bit Specifies whether the Insight Performance data will be collected or not TrendFlag Bit Specifies whether the Trend Performance data will be collected or not ReportFlag Bit Specifies whether the Report Performance data will be collected or not Table 6-3 Domain Column Name Data Type Description DomainName Varchar(30) Specifies the Domain Name DomainID Integer Specifies the Domain ID Table 6-4 Metric Map Column Name Data Type Description NodeId Integer Specifies the Node ID MetricId Integer Specifies the Metric ID NSKMetricId Integer Specifies the NSK Metric ID InsightFlag Bit Specifies whether the Insight Performance data will be collected or not Performance Monitor Database Schema 36

37 Table 6-3 Domain Column Name Data Type Description TrendFlag Bit Specifies whether the Trend Performance data will be collected or not ReportFlag Bit Specifies whether the Report Performance data will be collected or not Table 6-5 Metric Column Name Data Type Description DomainID Integer Specifies the Domain ID MetricId Integer Specifies the Metric ID MetricName Varchar(50) Specifies the name of the Metric Type Char(20) Specifies the data type of collected performance metric value. Table 6-6 Instance Column Name Data Type Description NodeId Integer Specifies the Node ID DomainID Integer Specifies the Domain ID InstanceId Integer Specifies the Instance ID InstanceName Varchar(50) Specifies the name of the Instance NSKInstanceId Integer Specifies the NSK Instance ID InsightFlag Bit Specifies whether the Insight Performance data will be collected or not TrendFlag Bit Specifies whether the Trend Performance data will be collected or not ReportFlag Bit Specifies whether the Report Performance data will be collected or not Table 6-7 TrendSummaryMap Column Name Data Type Description ConfigId Integer Specifies the Configuration ID TrendTableId Integer Specifies the ID of Trend type LastSummaryTix Integer Specifies Tix number upto which Last summarization is completed SummaryState Char(20) Specifies whether the summary is active or not SummaryStatus Char(20) Specifies whether the last summarization process was completed or not LastSummaryTime Integer Mentions the time stamp of the last summarization Table 6-8 Trend Configuration Column Name Data Type Description TrendTableId Integer Specifies the ID of Trend type TrendTableName Varchar(50) Specifies the Name of Trend Table in which the summarized data will be stored TrendInterval Integer The trend data interval in minutes InputTable Char(30) Name of table whose data will be used in the summarization process. InputTableType Char(30) Type of table whose data will be used in the summarization process. RetentionPeriod Integer Specifies the time period in days for which the data needs to be retained. Performance Monitor Database Schema 37