Job Management Partner 1/Performance Management User's Guide

[Contents][Glossary][Index][Back][Next]


Preface

This manual describes methods of operating JP1/Performance Management, how to manage a system when linking with other systems, and troubleshooting. In this manual, Job Management Partner 1 is abbreviated to JP1.

Intended readers

This manual is intended for readers with an interest in operating a system that uses JP1/Performance Management. It also assumes that the reader is familiar with the system being monitored.

For details on how to collect performance data when using JP1/Performance Management - Agent and JP1/Performance Management - Remote Monitor, refer to the manuals for each of these products.

Organization of this manual

This manual is organized into the following parts. Note that this manual contains information common to all the operating systems that this product supports. If there are differences relating to specific operating systems, we note these differences in the text.

PART 1: Operation
PART 1 describes how to operate JP1/Performance Management.

PART 2: System Linkage
PART 2 describes how to configure and operate JP1/Performance Management when you use it in a cluster system or link it with other systems.

PART 3: Troubleshooting
PART 3 describes how to detect errors with JP1/Performance Management and what action you should take when a problem occurs.

Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers).

For Job Management Partner 1/Performance Management:

For Job Management Partner 1:

Differences between versions

For JP1 Version 9 JP1/Performance Management, the manual contents of the old edition JP1 Version 8 Job Management Partner 1/Performance Management System Configuration and User's Guide (3020-3-K61-40(E)) have now been divided into the following two manuals.

The following table describes the correspondence between the Version 8 JP1 manual (Job Management Partner 1/Performance Management System Configuration and User's Guide (3020-3-K61-40(E))) and this manual (Job Management Partner 1/Performance Management User's Guide (3020-3-R32(E))):

JP1 Version 8 Job Management Partner 1/Performance Management System Configuration and User's Guide (3020-3-K61-40(E)) JP1 Version 9 Job Management Partner 1/Performance Management User's Guide (3020-3-R32(E))
PART 1: Overview Moved to the Job Management Partner 1/Performance Management Planning and Configuration Guide (3020-3-R31(E)).
1. Overview of Performance Management
2. Using Performance Management
PART 2: Design
3. Design of Operation Monitoring Systems that Use Performance Management
4. Performance Management Functions
PART 3: Configuration
5. Installation and Setup (in Windows)
6. Installation and Setup (in UNIX)
PART 4: Operation PART 1: Operation
7. Starting and Stopping Performance Management 1. Starting and Stopping Performance Management
8. Managing User Accounts 2. Managing User Accounts
9. Monitoring Agents 3. Monitoring Agents
10. Managing Operation Monitoring Data 4. Managing Operation Monitoring Data
11. Creation of Reports for Operation Analysis 5. Creation of Reports for Operation Analysis
12 Operation Monitoring with Alarms 6. Operation Monitoring with Alarms
13. Displaying Events 7. Displaying Events
14. Backing Up and Restoring Data 8. Backing Up and Restoring Data
PART 5: System Linkage PART 2: System Linkage
15. Construction and Operation with a Cluster System 9. Construction and Operation with a Cluster System
16. Operation Monitoring Linked with the Integrated Management Product JP1/IM 10. Linking with the Integrated Management Product JP1/IM for Operation Monitoring
17. Linking with Network Node Manager (NNM) for Operation Monitoring 11. Linking with Network Node Manager (NNM) for Operation Monitoring
18. Linking with ODBC-Complaint Application Programs for Operation Analysis 12. Linking with ODBC-Compliant Application Programs for Operation Analysis
PART 6: Troubleshooting PART 3: Troubleshooting
19. Detecting Problems within Performance Management 13. Detecting Problems within Performance Management
20. Error Handling Procedures 14. Error Handling Procedures
Appendix A. Limits Moved to the Job Management Partner 1/Performance Management Planning and Configuration Guide (3020-3-R31(E)).
Appendix B. Naming Rules
Appendix C. System Estimates
Appendix D. Kernel Parameter List
Appendix E. Migration Steps and Notes on Migration
Appendix F. Version Compatibility
Appendix G. Outputting Action Log Data
Appendix H. Health Check Agent
Appendix I. Version Changes Appendix A. Version Changes
Appendix J. Glossary Appendix B. Glossary

Conventions: Abbreviations

This manual uses the following abbreviations for product names:

Abbreviation Full name or meaning
AIX AIX 5L V5.3
AIX V6.1
HP-UX HP-UX 11i V2 (IPF)
HP-UX 11i V3 (IPF)
Internet Explorer Microsoft(R) Internet Explorer(R)
Windows(R) Internet Explorer(R)
IPF Itanium(R) Processor Family
JP1/IM JP1/IM - Manager Job Management Partner 1/Integrated Management - Manager
JP1/IM - View Job Management Partner 1/Integrated Management - View
JP1/NETM/DM Job Management Partner 1/NETM/DM Client
Job Management Partner 1/NETM/DM Manager
Job Management Partner 1/NETM/DM SubManager
Linux Linux (IPF) Linux 5 Advanced Platform (IPF) Red Hat Enterprise Linux(R) 5 Advanced Platform (IPF)
Linux 5 (IPF) Red Hat Enterprise Linux(R) 5 (IPF)
Linux AS 4 (IPF) Red Hat Enterprise Linux(R) AS 4 (IPF)
Linux (x64) Linux 5 Advanced Platform (AMD/Intel 64) Red Hat Enterprise Linux(R) 5 Advanced Platform (AMD/Intel 64)
Linux 5 (AMD/Intel 64) Red Hat Enterprise Linux(R) 5 (AMD/Intel 64)
Linux AS 4 (AMD64 & Intel EM64T) Red Hat Enterprise Linux(R) AS 4 (AMD64 & Intel EM64T)
Linux ES 4 (AMD64 & Intel EM64T) Red Hat Enterprise Linux(R) ES 4 (AMD64 & Intel EM64T)
Linux (x86) Linux 5 Advanced Platform (x86) Red Hat Enterprise Linux(R) 5 Advanced Platform (x86)
Linux 5 (x86) Red Hat Enterprise Linux(R) 5 (x86)
Linux AS 4 (x86) Red Hat Enterprise Linux(R) AS 4 (x86)
Linux ES 4 (x86) Red Hat Enterprise Linux(R) ES 4 (x86)
MSCS Microsoft(R) Cluster Service
NNM HP NNM HP Network Node Manager Software version 6 or earlier
HP Network Node Manager Starter Edition Software version 7.5 or earlier
Performance Management Job Management Partner 1/Performance Management
PFM - Agent PFM - Agent for Enterprise Applications Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications
PFM - Agent for Job Management Job Management Partner 1/Performance Management - Agent Option for Job Management
PFM - Agent for Microsoft SQL Server Job Management Partner 1/Performance Management - Agent Option for Microsoft(R) SQL Server
PFM - Agent for Oracle Job Management Partner 1/Performance Management - Agent Option for Oracle
PFM - Agent for Platform PFM - Agent for Platform (UNIX) Job Management Partner 1/Performance Management - Agent Option for Platform (for UNIX systems)
PFM - Agent for Platform (Windows) Job Management Partner 1/Performance Management - Agent Option for Platform (for Windows systems)
PFM - Agent for Service Response Job Management Partner 1/Performance Management - Agent Option for Service Response
PFM - Agent for Virtual Machine Job Management Partner 1/Performance Management - Agent Option for Virtual Machine
PFM - Base Job Management Partner 1/Performance Management - Base
PFM - Manager Job Management Partner 1/Performance Management - Manager
PFM - RM PFM - RM for Microsoft SQL Server Job Management Partner 1/Performance Management - Remote Monitor for Microsoft(R) SQL Server
PFM - RM for Oracle Job Management Partner 1/Performance Management - Remote Monitor for Oracle
PFM - RM for Platform Job Management Partner 1/Performance Management - Remote Monitor for Platform
PFM - Web Console Job Management Partner 1/Performance Management - Web Console
Solaris Solaris 9 Solaris 9 (SPARC)
Solaris 10 Solaris 10 (SPARC)
Solaris 10 (x64)
Solaris 10 (x86)
Windows Server 2003 Windows Server 2003 (x64) or 2003 (x64) Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Windows Server 2003 (x86) or 2003 (x86) Microsoft(R) Windows Server(R) 2003, Enterprise Edition
Microsoft(R) Windows Server(R) 2003, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Windows Server 2008 Windows Server 2008 Enterprise Microsoft(R) Windows Server(R) 2008 Enterprise
Microsoft(R) Windows Server(R) 2008 Enterprise without Hyper-V(TM)
Windows Server 2008 Standard Microsoft(R) Windows Server(R) 2008 Standard
Microsoft(R) Windows Server(R) 2008 Standard without Hyper-V(TM)
WSFC Windows Server(R) Failover Cluster

This manual also uses the following abbreviations:

Abbreviation Full name
CPU Central Processing Unit
CSV Comma Separated Values
DB DataBase
DDE Dynamic Data Exchange
DNS Domain Name System
FQDN Fully Qualified Domain Name
GMT Greenwich Mean Time
GUI Graphical User Interface
HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
IP Internet Protocol
LAN Local Area Network
MIB Management Information Base
NAT Network Address Translation
NFS Network File System
ODBC Open DataBase Connectivity
OS Operating System
PQL Program Query Language
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
TCP Transmission Control Protocol
UAC User Account Control
URL Uniform Resource Locator
XML eXtensible Markup Language

Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

Conventions: Fonts and symbols

Font and symbol conventions are classified as:

These conventions are described below.

General font conventions

The following table lists the general font conventions:

Font Convention
Bold Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following:
  • From the File menu, choose Open.
  • Click the Cancel button.
  • In the Enter name entry box, type your name.
Italics Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:
  • Write the command as follows:
    copy source-file target-file
  • Do not delete the configuration file.
Code font A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
  • At the prompt, enter dir.
  • Use the send command to send mail.
  • The following message is displayed:
The password is incorrect.

Examples of coding and messages appear as follows (although there might be some exceptions, such as when coding is included in a diagram):

MakeDatabase
...
StoreDatabase temp DB32

In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.

Conventions in syntax explanations

Syntax definitions appear as follows:

StoreDatabase [temp|perm] (database-name ...)

The following table lists the conventions used in syntax explanations:

Example font or symbol Convention
StoreDatabase Code-font characters must be entered exactly as shown.
database-name This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.
SD Bold code-font characters indicate the abbreviation for a command.
perm Underlined characters indicate the default value.
[ ] Square brackets enclose an item or set of items whose specification is optional.
| (vertical bar) A vertical bar separates items in a list, and means "OR".
For example, A|B|C means one of A or B or C.
... An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary.
() Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.
{} Curly brackets enclose a list of items, and indicate that one (and only one) of the items in the list must be used. A vertical bar (|) separates the items in the list.
For example, {A|B|C} means that one of A or B or C must be used.

Conventions for mathematical expressions

This manual uses the following symbols in mathematical expressions:

Symbol Meaning
x Multiplication sign
/ Division sign

Conventions: Format of product names, service IDs, and service keys in this manual

In Performance Management of version 09-00 or later, enabling the product name display functionality allows the service IDs and service keys to be displayed as the product name. The following table lists the displayed examples of service IDs and service keys for PFM - Agent for Platform (Windows) when the product name display functionality is enabled.

Identifier Product name display functionality
Disabled Enabled
Service ID TS1 host-name host-name<Windows>(Store)
TA1 host-name host-name<Windows>
Service key agtt Windows

This manual generally uses the format when the product name display functionality is assumed to be enabled.

Note that the product name display functionality can be enabled when the following conditions are satisfied:

Conventions: KB, MB, GB and TB

This manual uses the following conventions:

Conventions: Meaning of "bookmark"

In this manual, bookmark is generally used when there is no need to distinguish bookmark and combination bookmark. Combination bookmark is used only for describing original functionalities of combination bookmarks.

Conventions: Meaning of "directory" and "folder"

This manual uses the term directory wherever possible to refer to what Windows calls a folder and what UNIX calls a directory.

Conventions: Meaning of Performance Management "installation directory"

This manual uses the expression installation folder for Windows Performance Management, and installation directory for UNIX Performance Management.

The default installation folder for Windows Performance Management is as follows:

Performance Management installation folder except for PFM - Web Console:

- For programs other than Windows Server 2003 (x64) and Windows Server 2008 (64 bit)
system-drive:\Program Files\Hitachi\jp1pc\

- For Windows Server 2003 (x64) and Windows Server 2008 (64 bit)
system-drive:\Program Files (x86)\Hitachi\jp1pc\

PFM - Web Console installation folder:

- For programs other than Windows Server 2003 (x64) and Windows Server 2008 (64 bit)
system-drive:\Program Files\Hitachi\jp1pcWebCon\

- For Windows Server 2003 (x64) and Windows Server 2008 (64 bit)
system-drive:\Program Files (x86)\Hitachi\jp1pcWebCon\

The default installation directory for UNIX Performance Management is as follows:

Performance Management installation directory except for PFM - Web Console:
/opt/jp1pc/

PFM - Web Console installation directory:
/opt/jp1pcwebcon/

Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

Proper use of JP1/Performance Management manuals

Manuals for JP1/Performance Management are divided into following manuals. Check the description below and refer to the appropriate manual depending on your purpose.

Manual name Description
Job Management Partner 1/Performance Management Planning and Configuration Guide Functionalities, and set up or configuration method
Job Management Partner 1/Performance Management User's Guide Operation method
Job Management Partner 1/Performance Management Reference Windows, commands, and messages

NNM products supported by Performance Management

Performance Management supports the linkage with the following products:

This manual generally uses NNM to indicate the above products, and NNM linkage for functionalities for linking with these products.

Note that Performance Management does not support the linkage with the following product:

[Contents][Back][Next]


[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.