Preface

■ Intended readers

This manual is intended for:

• Those who wish to design or set up an operation monitoring system.

• Those who wish to define conditions for collecting performance data

• Those who wish to define reports and alarms

• Those who wish to monitor a system with reference to collected performance data

• Those who wish to plan strategies for improving the system based on the monitoring results

This manual assumes that the reader is familiar with the system being monitored.

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

To Page Top

■ Organization of this manual

This manual is organized into the chapters listed below. This manual is intended for use with multiple operating systems (OS). When there are differences in functionality between operating systems, this manual provides a separate description for each OS.

1. Performance Management windows

Chapter 1 describes the JP1/Performance Management - Web Console window that is displayed using a Web browser.

2. PFM - Web Console Window Displayed on the Integrated Operation Viewer of JP1/IM2

Chapter 2 describes the JP1/Performance Management - Web Console window displayed on the Integrated Operation Viewer of JP1/Integrated Management 2 when linkage is established with JP1/Integrated Management 2.

3. Commands

Chapter 3 describes the JP1/Performance Management commands.

4. Definition Files

Chapter 4 describes the JP1/Performance Management definition files.

5. JP1/PFM Plug-in Functions Available on JP1/IM2

Chapter 5 describes the JP1/PFM plug-in functions available on JP1/IM2.

6. Log Information Output by Performance Management

Chapter 6 describes the log information that is output by JP1/Performance Management and its output formats.

7. Messages

Chapter 7 describes the messages output by JP1/Performance Management - Manager and JP1/Performance Management - Web Console in terms of their formats and their output destinations. It provides a list of the messages output to syslog and the Windows event log, and it describes and explains the messages individually.

To Page Top

■ Conventions: Diagrams

This manual uses the following conventions in diagrams:

To Page Top

■ 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: From the File menu, choose Open. Click the Cancel button. In the Enter name entry box, type your name.
Italic	Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example: Write the command as follows: copy source-file target-file The following message appears: A file was not found. (file = file-name) Italic characters are also used for emphasis. For example: Do not delete the configuration file.
Monospace	Monospace characters indicate 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.

The following table explains the symbols used in this manual:

Symbol	Convention
-	The hyphen is used as an option delimiter. An option may consist of the following: • One or more alphanumeric characters • One or more alphanumeric characters and arguments. Note that an option can be included within an argument. When an option or a space is included in an argument, it may be necessary to enclose the entire argument in single (') or double (") quotation marks.
|	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.

To Page Top

■ 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.

To Page Top