Preface
This manual describes the features of JP1/Performance Management, and the methods for designing and configuring a system.
- Organization of this preface
■ Intended readers
This manual describes JP1/Performance Management. It is intended for the following readers:
-
Users who are interested in gaining a basic understanding of JP1/Performance Management functionality before they deploy an operation monitoring system
-
Users who are interested in designing and building an operation monitoring system
This manual assumes that the reader is knowledgeable about the operation of the monitored system.
For details about how to use JP1/Performance Management - Agent or JP1/Performance Management - Remote Monitor to collect performance data, the reader is recommended to read this manual together with the applicable JP1/Performance Management - Agent manual or the JP1/Performance Management - Remote Monitor manual.
■ 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: Overview
-
PART 1 provides an overview and some operation examples of JP1/Performance Management.
- PART 2: Design
-
PART 2 explains the main design issues to consider when JP1/Performance Management is used to build an operation monitoring system. It also explains the functions provided by JP1/Performance Management.
- PART 3: Configuration
-
PART 3 gives details on how to configure JP1/Performance Management and how to change the configurations.
■ Conventions: Fonts and symbols
The following table explains the text formatting conventions used in this manual:
Text formatting |
Convention |
---|---|
Bold |
Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:
|
Italic |
Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:
Italic characters are also used for emphasis. For example:
|
Monospace |
Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:
|
The following table explains the symbols used in this manual:
Symbol |
Convention |
---|---|
| |
In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example: A|B|C means A, or B, or C. |
{ } |
In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example: {A|B|C} means only one of A, or B, or C. |
[ ] |
In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example: [A] means that you can specify A or nothing. [B|C] means that you can specify B, or C, or nothing. |
... |
In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted. In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example: A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary. |
() |
Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable. |
■ 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:
-
Version 1.00 (or 1.0) is written as 01-00.
-
Version 2.05 is written as 02-05.
-
Version 2.50 (or 2.5) is written as 02-50.
-
Version 12.25 is written as 12-25.
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.