Preface
This manual provides an overview and describes the functionality and system design of JP1/Integrated Management 3 - Manager, JP1/Integrated Management 3 - View and JP1/Integrated Management 3 - Agent.
In this manual, JP1/Integrated Management is abbreviated to JP1, and JP1/Integrated Management 3 - Manager, JP1/Integrated Management 3 - View and JP1/Integrated Management 3 - Agent are generically referred to as JP1/Integrated Management or JP1/IM. In addition, in this manual, read JP1/Integrated Management - Manager, JP1/Integrated Management - View and JP1/Integrated Management 3 - Agent as JP1/Integrated Management 3 - Manager, JP1/Integrated Management 3 - View and JP1/Integrated Management 3 - Agent respectively.
JP1/IM is a suite of integrated management products that provide the core foundation for performing integrated management of IT systems.
In addition to the integrated management products, the JP1 series of products listed below are mentioned in this manual. For further details, see the documentation accompanying the product.
Product name |
Contents covered in this manual |
---|---|
JP1/Service Support |
|
JP1/TELstaff |
|
JP1/Integrated Management 3 - Event Gateway for Network Node Manager i |
|
JP1/Integrated Management - Message Optimizer |
|
JP1/Navigation Platform |
|
JP1/Automatic Job Management System 3 |
|
JP1/Performance Management |
|
- Organization of this preface
■ Intended readers
This manual is intended for professionals who are considering introducing JP1/IM to manage open platform systems. More specifically, it is intended for:
-
System administrators who are considering introducing JP1/IM to centrally monitor events that occur in the system
-
Those who have knowledge of operating systems and applications
■ Organization of this manual
This manual is organized into the following parts:
- PART 1: Overview
-
This part provides an overview of the integrated management products, the JP1 series products, and JP1/IM.
- PART 2: Functionality
-
This part describes the functionality of JP1/IM.
- PART 3: Design
-
This part describes the requirements for the monitoring tasks supported by JP1/IM and the system requirements for achieving those objectives.
■ Manual suite
JP1/IM manuals provide necessary information according to the phases in the system life cycle, which include planning and design, configuration, and operation.
The following figure explains which phases the JP1/IM manuals provide information for.
■ Conventions: Diagrams
This manual uses the following conventions in diagrams:
■ 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: Installation folders for the Windows version of JP1/IM and JP1/Base
In this manual, the default installation folders of JP1/IM and JP1/Base for Windows are represented as follows:
Product name |
Installation folder notation |
Default installation folder# |
---|---|---|
JP1/IM - View |
view-path |
system-drive:\Program Files\Hitachi\JP1CoView |
JP1/IM - Manager |
manager-path |
system-drive:\Program Files\Hitachi\JP1IMM |
console-path |
system-drive:\Program Files\Hitachi\JP1Cons |
|
scope-path |
system-drive:\Program Files\Hitachi\JP1Scope |
|
JP1/IM - Agent |
agent-path |
system-drive:\Program Files\Hitachi\JP1IMA |
JP1/Base |
base-path |
system-drive:\Program Files\Hitachi\JP1Base |
#: Represents the installation folder when the product is installed in the default location. The location represented by system-drive:\Program Files is determined at the time of installation by an OS environment variable, and might differ depending on the environment.
■ Conventions: Meaning of "Administrator permissions" in this manual
In this manual, Administrator permissions refers to Administrator permissions for the local PC. The local user, domain user, or user of the Active Directory environment can perform tasks requiring Administrator permissions if granted Administrator permissions for the local PC.
■ 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.
■ Online manual
JP1/IM comes with an HTML manual that you can read in a Web browser.
The HTML manual has the same contents as this manual.
To view the HTML manual:
-
In JP1/IM - View, choose Help and then Help Contents.
-
In Integrated Operation Viewer Window, choose Help and then Online Manual.
Note:
-
Depending on the OS settings, the HTML manual might appear in the active window when opened from the Start menu.
■ Output destinations of Integrated trace log file
Starting with JP1/IM 12-10, all 32-bit Java processes for JP1/IM have been changed to 64-bit Java processes. Therefore, the integrated trace log output destination output by the Java process function of each function of JP1 / IM is changed.
The following is the destination of the integrated trace log for each JP1/IM function from version 12-10 or later. If you are using the log file trap function, you must change the settings as you change the destination.
Output destinations of Integrated trace log file (32 bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool
-
IM database
-
Central Scope Service
-
Process management
-
Command execution
-
Automatic action
-
Installation and Setup
Output destinations of Integrated trace log file (64 bit): system-drive\Program Files\Hitachi\HNTRLib2\spool
-
Event base service
-
Central Console viewer
-
Central Scope viewer
-
Event Genaration Service
-
IM Configuration Management
-
IM Configuration Management viewer
-
Intelligent Integrated Management Base