Preface

■ What you can do with JP1/IM

With the growing size and complexity of the systems underpinning an enterprise's business operations, management of system operation is a vital issue. JP1/IM optimizes system operations management by offering integrated management tailored to objectives and integration of operational tasks.

JP1/IM has the following features:

• Integrated management using JP1 events (simply called events hereafter) and centralized system monitoring

• Error detection and reporting

• Integrating troubleshooting based on JP1/IM

• Integrated management of the system hierarchy and host settings

With the above features, JP1/IM integrates monitoring and operation into a unified management process based on JP1/IM, thus simplifying complex tasks.

The following figure shows the major JP1/IM functions.

To Page Top

■ What is explained in this manual

This manual is intended for professionals who want to use JP1/IM to manage and operate open platform systems, and those who are considering introducing JP1/IM. More specifically, it is intended for:

• System administrators and operators who want an overview of the basic use of JP1/IM

• Those who are considering implementation of JP1/IM to centrally monitor events that occur in their system

Users who have not purchased a support services contract can also use this manual.

The chapters of this manual describe how to install and set up programs, and configure the functions required for intended readers to start system monitoring in a basic configuration. Furthermore, appendixes in this manual explain advanced monitoring functions such as email notifications, visual monitoring, and other functions for efficient use of JP1/IM.

Operation procedures in this manual assume systems consisting of monitored hosts (agents) and management servers (managers) with JP1/Integrated Management - Manager installed. Agents and managers are configured hierarchically in two levels, as shown in the following figure:

To Page Top

■ How to read this manual

The following environments are required to perform the operations in each window.

Operations on the manager:

Environment in which Windows Server 2008 R2 or Linux 6 (x64) is used

Operations on the viewer:

Environment in which Windows 7 is used

Some windows in this manual might differ from the windows of your product because of improvements made without prior notice.

The JP1/IM manual set consists of seven manuals, including this one. For details about the setup and operation methods introduced in this manual, read the pertinent descriptions in the manuals shown below.

The following shows an example of the reading sequence of manuals, based on user requirements:

In this manual, the term Administrator permissions means the Administrator permissions for a local PC. If the user has Administrator permissions for the local PC, operations are the same no matter whether they are performed with a local user account, a domain user account, or in an Active Directory environment.

This manual uses the following replacement characters to represent installation folders for Windows versions of JP1/IM and JP1/Base:

• View-path

• Manager-path

• Console-path

• Scope-path

• Base-path

For details about these replacement characters, see F. Reference Material for this Manual.

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