Preface

This manual describes the functionality and records of JP1/Performance Management - Agent Option for Service Response.

Organization of this preface

Intended readers
Organization of this manual
Conventions: Fonts and symbols
Conventions: Version numbers

■ Intended readers

This manual describes JP1/Performance Management. The manual is intended for the following readers:

Users who wish to design or construct an operation monitoring system.
Users who wish to collect internet service performance data.
Users who wish to define conditions for collecting performance data.
Users who wish to define reports and alarms.
Users who wish to use collected performance data to monitor a system.
Users who wish to consider or take actions for a system based on monitoring results.

Readers of this manual must be familiar with the system being monitored and Internet service protocols, and must have a basic knowledge of the operating systems.

For details about how to design and run systems that use JP1/Performance Management, also see the following manuals:

JP1/Performance Management Planning and Configuration Guide
JP1/Performance Management User's Guide
JP1/Performance Management Reference

To Page Top

■ Organization of this manual

This manual is organized into the parts listed below. This manual can be used as a common reference under the following condition: the host on which JP1/Performance Management - Agent Option for Service Response is installed runs on the Windows operating system. When there are differences in functionality between OSs, this manual provides a separate description for each OS.

Part 1. Overview: This part provides an overview of JP1/Performance Management - Agent Option for Service Response.
Part 2. Configuration and Operations: This part explains how to install and set up JP1/Performance Management - Agent Option for Service Response. It also explains the definitions for service measurement, starting and stopping, and how to perform operations in a cluster system.
Part 3. Reference: This part describes the windows, definition files, monitoring templates, records, commands, and messages of JP1/Performance Management - Agent Option for Service Response.
Part 4. Troubleshooting: This part describes the actions to be taken for errors that might occur during operation of JP1/Performance Management - Agent Option for Service Response.

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

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
`\|`	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.
x	Multiplication sign
`/`	Division sign

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