Preface
This manual describes the windows 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 as 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.
- Organization of this preface
■ Intended readers
This manual is intended for users who want to operate an infrastructure that manages an open-platform system from JP1/IM windows. More specifically, it is intended for:
-
System administrators and operators who operate JP1/IM windows to centrally monitor events that arise in the system
-
System administrators and operators who operate JP1/IM windows to centrally monitor the status of the system management infrastructure based on correlation with events that arise in the system
-
Those who have knowledge of operating systems and applications
■ Organization of this manual
This manual is organized into the following chapters:
- 1. Window Transitions and Login Window
-
Chapter 1 describes the window transitions and the Login window of JP1/IM - View.
- 2. Integrated Operation Viewer Window
-
Chapter 2 describes the items displayed and defined in the Integrated Operation Viewer window.
- 3.Event Console Window
-
Chapter 2 describes the items displayed and defined in the Event Console window.
- 4. Monitoring Tree Window
-
Chapter 3 describes the items displayed and defined in the Monitoring Tree window.
- 5. IM Configuration Management Window
-
Chapter 4 describes the items displayed and defined in IM Configuration Management - View.
■ Manual suite
JP1/IM manuals provide necessary information according to the phase in the system life cycle (the phases include system design, configuration, and operation). Read the manual appropriate for the purpose.
The following figure explains which phases the JP1/IM manuals provide information for.
![[Figure]](GRAPHICS/CO000500.GIF)
![[Figure]](GRAPHICS/CO000200.GIF)
■ Conventions: Fonts and symbols
Font and symbol conventions are classified as:
-
General font conventions
-
Conventions in syntax explanations
These conventions are described below.
General font conventions
The following table lists the general font conventions:
|
Font |
Convention |
|---|---|
|
Bold |
Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following:
|
|
Italics |
Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:
|
|
Code font |
A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
|
Examples of coding and messages appear as follows (although there may be some exceptions, such as when coding is included in a diagram):
MakeDatabase
...
StoreDatabase temp DB32
In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.
Conventions in syntax explanations
Syntax definitions appear as follows:
StoreDatabase [temp|perm] (database-name ...)
The following table lists the conventions used in syntax explanations:
|
Example font or symbol |
Convention |
|---|---|
|
StoreDatabase |
Code-font characters must be entered exactly as shown. |
|
database-name |
This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command. |
|
SD |
Bold code-font characters indicate the abbreviation for a command. |
|
perm |
Underlined characters indicate the default value. |
|
[ ] |
Square brackets enclose an item or set of items whose specification is optional. |
|
| |
Only one of the options separated by a vertical bar can be specified at the same time. |
|
... |
An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified 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 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