JP1 Version 13 JP1/Integrated Management 3 - Manager GUI Reference

3021-3-L05-30(E)

Notices

Relevant program products

For details about the supported operating system version and prerequisite service packs and patches for JP1/Integrated Management 3 - Manager, JP1/Integrated Management 3 - View and JP1/Integrated Management 3 - Agent see the Release Notes of the applicable product.

JP1/Integrated Management 3 - Manager (for Windows):

P-2A2C-8EDL JP1/Integrated Management 3 - Manager 13-11

The above product includes the following:

P-CC2A2C-9MDL JP1/Integrated Management 3 - Manager 13-11 (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC2A2C-6HDL JP1/Integrated Management 3 - View 13-00 (for Windows 11, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 10)

P-CC2A2C-9GDL JP1/Integrated Management 3 - Agent 13-11 (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC842C-9GDL JP1/Integrated Management 3 - Agent 13-11 (for Linux 9, Linux 8, Linux 7, Oracle Linux 9, Oracle Linux 8, Oracle Linux 7, SUSE Linux 15, SUSE Linux 12, Amazon Linux 2023)

P-CC2A2C-6LDL JP1/Base 13-10 (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC842C-6LDL JP1/Base 13-10 (for Linux 9, Linux 8, Linux 7, Oracle Linux 9, Oracle Linux 8, Oracle Linux 7, SUSE Linux 15, SUSE Linux 12, Amazon Linux 2023)

P-CC1M2C-6LDL JP1/Base 13-10 (for AIX)

JP1/Integrated Management 3 - Manager (for Linux):

P-842C-8EDL JP1/Integrated Management 3 - Manager 13-11

The above product includes the following:

P-CC842C-9MDL JP1/Integrated Management 3 - Manager 13-11 (for Linux 9, Linux 8, Linux 7, Oracle Linux 9, Oracle Linux 8, Oracle Linux 7)

P-CC9W2C-9MDL JP1/Integrated Management 3 - Manager 13-11 (for SUSE Linux 15, SUSE Linux 12)

P-CC2A2C-6HDL JP1/Integrated Management 3 - View 13-00 (for Windows 11, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 10)

P-CC2A2C-9GDL JP1/Integrated Management 3 - Agent 13-11 (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC842C-9GDL JP1/Integrated Management 3 - Agent 13-11 (for Linux 9, Linux 8, Linux 7, Oracle Linux 9, Oracle Linux 8, Oracle Linux 7, SUSE Linux 15, SUSE Linux 12, Amazon Linux 2023)

P-CC2A2C-6LDL JP1/Base 13-10 (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC842C-6LDL JP1/Base 13-10 (for Linux 9, Linux 8, Linux 7, Oracle Linux 9, Oracle Linux 8, Oracle Linux 7, SUSE Linux 15, SUSE Linux 12, Amazon Linux 2023)

P-CC1M2C-6LDL JP1/Base 13-10 (for AIX)

Trademarks

The company and product names mentioned in this document may be the trademarks of their respective owners.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project.

Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.

This product includes software developed by the University of California, Berkeley and its contributors.

This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).

Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

This product includes software developed by Ralf S.Engelschall <rse@engelschall.com> for use in the mod_ssl project (http://www.modssl.org/).

1. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

2. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)

3. This product includes software written by Tim Hudson (tjh@cryptsoft.com)

4. This product includes the OpenSSL Toolkit software used under OpenSSL License and Original SSLeay License. OpenSSL License and Original SSLeay License are as follow:

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a double license, i.e. both the conditions of

the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts. Actually both licenses are BSD-style

Open Source licenses. In case of any license issues related to OpenSSL

please contact openssl-core@openssl.org.

OpenSSL License

---------------

/* ====================================================================

* Copyright (c) 1998-2018 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

*

*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

*

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

This product includes software developed by Andy Clark.

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes software developed by IAIK of Graz University of Technology.

This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

Java is a registered trademark of Oracle and/or its affiliates.

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

Hyper-V

Microsoft(R) Windows Server(R) 2012 Hyper-V(R)

SCVMM

Microsoft(R) System Center Virtual Machine Manager 2012

Windows 10

Windows(R) 10 Enterprise 64-bit

Windows(R) 10 Home 64-bit

Windows(R) 10 Pro 64-bit

Windows 11

Windows(R) 11 Enterprise

Windows(R) 11 Home

Windows(R) 11 Pro

Windows Server 2016

Microsoft(R) Windows Server(R) 2016 Datacenter

Microsoft(R) Windows Server(R) 2016 Standard

Windows Server 2019

Microsoft(R) Windows Server(R) 2019 Datacenter

Microsoft(R) Windows Server(R) 2019 Standard

Windows Server 2022

Microsoft(R) Windows Server(R) 2022 Datacenter

Microsoft(R) Windows Server(R) 2022 Standard

Windows is often used generically to refer to Windows 11, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 10.

Restrictions

Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty.

Material contained in this document may describe Hitachi products not available or features not available in your country.

No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.

Issued

Mar. 2025: 3021-3-L05-30(E)

Copyright

Copyright (C) 2023, 2025 Hitachi, Ltd.

Copyright (C) 2023, 2025 Hitachi Solutions, Ltd.

Colophon

Publisher

Hitachi, Ltd.

6-6, Marunouchi 1-chome, Chiyoda-ku, Tokyo, 100‒8280 Japan

Summary of amendments

The following table lists changes in this manual (3021-3-L05-30(E)) and product changes related to this manual.

Changes

Location

Added the dashboard list collection/deletion function for administrators.

Accordingly, a description of this function was added to the explanation in the Dashboard List dialog box of the Integrated Operation Viewer.

2.4.1(1)(b)

In addition to the above changes, minor editorial corrections were made.

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.

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.

Conventions: Diagrams

This manual uses the following conventions in diagrams:

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:

From the File menu, choose Open.

Click the Cancel button.

In the Enter name entry box, type your name.

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:

Write the command as follows:

copy source-file target-file

Do not delete the configuration file.

Code font

A code font indicates 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.

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

1 Window Transitions and Login Window

This chapter describes the window transitions and the Login windows of the integrated operation viewer and JP1/IM - View.

1.1 Window transitions

The following figures show the window transitions in JP1/IM - View.

Figure 1‒1: Transitions of the Login window

Figure 1‒2: Transitions of the Event Console and related windows

Figure 1‒3: Transitions of the Monitoring Tree and related windows

Figure 1‒4: Transitions of the Monitoring Tree (Editing) and related windows

Figure 1‒5: Transitions of the IM Configuration Management and related windows

The following figure shows the window transitions of the Integrated Operation Viewer window.

Figure 1‒6: Transitions of the Integrated Operation Viewer window

1.2 Login window

There are three different Login windows: one for logging in to Central Console and to Central Scope, and one is for logging in to IM Configuration Management, and one is for logging in to Intelligent Integrated Management Base.

You can access the Login window of the Intelligent Integrated Management Base through a Web browser. The Login window of Central Console, Central Scope, or IM Configuration Management is displayed when JP1/IM - View is started.

When a user logs in to Central Console from the Login window of Central Console and Central Scope, and is authenticated, the Event Console window appears. When a user logs in to Central Scope from the Login window of Central Console and Central Scope, and is authenticated, the Monitoring Tree window appears. When a user logs in from the Login window of IM Configuration Management, and is authenticated, the IM Configuration Management window appears.

1.2.1 Login window of the Intelligent Integrated Management Base

You can open the Login window of the Intelligent Integrated Management Base by entering the URL of the Login window in the address bar (URL entry area) of the Web browser.

The URL is defined in the following syntax:

http://host-name-of-the-Intelligent-Integrated-Management-server:port-number/login

Note: The URL starts with https if SSL communication is used.

For the port number of the URL, specify the port number of the Intelligent Integrated Management Base set in the Intelligent Integrated Management Base definition file (imdd.properties) (default is 20703).

For details, see Intelligent Integrated Management Base definition file (imdd.Properties) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The Intelligent Integrated Management Base displays different Login windows depending on the authentication method to be used. The following figure shows the Login window of the Intelligent Integrated Management Base.

Figure 1‒7: Login window of the Intelligent Integrated Management Base (when you want to be authenticated by JP1/Base)

User name

If you want to be authenticated by JP1/Base to log in, enter the user name you want to use. The user name that is entered must be one that is already registered in JP1/Base on the authentication server. During registration of a user name, the permissions for operating JP1/IM windows must be granted for the user. For details about registering users permitted to log in and the permissions for operating JP1/IM windows, see the following manuals:

Registering a user

JP1/Base User's Guide (chapter on the settings for user management)

Granting permissions

JP1/Integrated Management 3 - Manager Overview and System Design Guide (Appendix E. Operating Permissions)

User names can consist of 1 to 31 alphanumeric characters, and are not case sensitive.

Password

Text box for entering the password corresponding to the entered user name.

Passwords are case sensitive. A character string with 0 to 32 bytes can be specified.

Figure 1‒8: Login window of the Intelligent Integrated Management Base (when you want to be authenticated by an OpenID provider)

JP1 User name / Password

Enter them if you want to be authenticated by JP1/Base to log in. See the descriptions of User name and Password in Login window of the Intelligent Integrated Management Base (when you want to be authenticated by JP1/Base).

Log in using another account / Log in using the following account

The window displays buttons showing the names of OpenID providers. Click a button to display the authentication window of the OpenID provider. After you are authenticated by the OpenID provider, the Integrated Operation Viewer window appears.

To enable authentication by OpenID providers, they must be defined in the Intelligent Integrated Management Base definition file (imdd.properties) in advance.

For details, see Intelligent Integrated Management Base definition file (imdd.properties) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

1.2.2 Login window of Central Consol and Central Scope

The following figure shows the Login window of Central Console and Central Scope.

Figure 1‒9: Login window (Central Console and Central Scope)

The following describes the items displayed in the window.

User name

Text box for entering the user name of the user who is logging in. By default, the name of the last user to successfully log in appears. The user name that is entered must be one that is already registered in JP1/Base on the authentication server. During registration of the user name, the permissions for operating JP1/IM windows must be granted for the user. For details about registering users permitted to log in and the permissions for operating JP1/IM windows, see the following manuals:

Registering a user

JP1/Base User's Guide (chapter on the settings for user management)

Granting permissions

JP1/Integrated Management 3 - Manager Overview and System Design Guide (Appendix E. Operating Permissions)

User names can consist of 1 to 31 alphanumeric characters, and are not case sensitive.

Password

Text box for entering the password corresponding to the entered user name. Passwords are case sensitive. A character string having from 0 to 32 bytes can be specified.

Host to connect

Text box for specifying the JP1/IM - Manager host to which JP1/IM - View is to connect. A character string having from 0 to 255 bytes can be specified. All characters other than control characters can be used. By default, the name of the host used for the last successful login appears. Specify a host name that the OS can resolve or an IP address in dot format (such as 10.100.1.1). The system does not look for host names in the jp1hosts or jp1hosts2 file.

Note that, when specifying an IP address, you can use the IPv4 format only. You cannot use the IPv6 format.

When a user logs in from a Web browser, an address in IPv6 format cannot be used.

When using the communication encryption function, you can use a host name only. You cannot use an IP address.

Central Console

Selecting this check box connects the user to JP1/IM - Manager (Central Console) and displays the Event Console window.

Central Scope

Selecting this check box connects the user to JP1/IM - Manager (Central Scope) and displays the Monitoring Tree window.

1.2.3 Login window of IM Configuration Management

The following figure shows the Login window of IM Configuration Management.

Figure 1‒10: Login window (IM Configuration Management)

The following describes the items displayed in the window.

User name

Text box for entering the user name of the user who is logging in. By default, the name of the last user to successfully log in appears. The user name that is entered must be one that is already registered in JP1/Base on the authentication server. During registration of the user name, the permissions for operating JP1/IM windows must be granted for the user. For details about registering users permitted to log in and permissions for operating JP1/IM windows, see the following manuals:

Registering a user

JP1/Base User's Guide (chapter on the settings for user management)

Granting permissions

JP1/Integrated Management 3 - Manager Overview and System Design Guide (Appendix E. Operating Permissions)

User names can consist of 1 to 31 alphanumeric characters, and are not case sensitive.

Password

Text box for entering the password corresponding to the entered user name. Passwords are case sensitive. A character string having from 0 to 32 bytes can be specified. Alphanumeric characters and symbols other than control characters can be used.

Host to connect

Text box for specifying the IM Configuration Management host to which JP1/IM - View is to connect. A character string having from 0 to 255 bytes can be specified. All characters other than control characters can be used. By default, the name of the host used for the last successful login appears. Specify a host name that the OS can resolve or an IP address in dot format (such as 10.100.1.1). The system does not look for host names in the jp1hosts or jp1hosts2 file. Note that, when specifying an IP address, you can use the IPv4 format only. You cannot use the IPv6 format.

When using the communication encryption function, you can use a host name only. You cannot use an IP address.

For details about the settings for using IM configuration management functionality, see 1.4.4 Settings for using the functions of IM Configuration Management (for Windows) in the JP1/Integrated Management 3 - Manager Configuration Guide.

1.3 Notes on operations in windows

Note the following about performing operations in windows:

1.3.1 Notes on JP1/IM - View

Operations from the keyboard are guaranteed only for the keyboard shortcuts that are explicitly displayed in windows. Whenever possible, use the mouse to perform operations in windows.

JP1/IM - View does not redraw any windows while it is querying JP1/IM - Manager. If a window is moved or is behind another window, the information displayed in the window might become temporarily garbled. However, the window will be redrawn correctly when the query is completed.

Multibyte characters and specific character codes may be displayed incorrectly or may not be handled as the indicated characters or as character codes. For the specific character codes, see Table 1-1 Character codes that might be handled incorrectly.

Table 1‒1: Character codes that might be handled incorrectly

Code

Value

Description

00

NUL

NULl (null character)

01

SOH

Start Of Heading

02

STX

Start of TeXt

03

ETX

End of TeXt

04

EOT

End Of Transmission

05

ENQ

ENQuiry

06

ACK

ACKnowledge

07

BEL

BELl

08

BS

Back Space

09

HT

Horizontal Tabulation

0A

LF

Line Feed

0B

VT

Vertical Tabulation

0C

FF

Form Feed

0D

CR

Carriage Return

0E

SO

Shift Out

0F

SI

Shift In

10

DLE

Data Link Escape

11

DC1

Device Control 1

12

DC2

Device Control 2

13

DC3

Device Control 3

14

DC4

Device Control 4

15

NAK

Negative AcKnowledge

16

SYN

SYNchronous idle

17

ETB

End of Transmission Block

18

CAN

CANcel

19

EM

End of Medium

1A

SUB

SUBstitute

1B

ESC

ESCape

1C

FS

File Separator

1D

GS

Group Separator

1E

RS

Record Separator

1F

US

Unit Separator

7F

DEL

DELete

80

PAD

PADding character

81

HOP

High Octet Preset

82

BPH

Break Permitted Here

83

NBH

No Break Here

84

IND

INDex

85

NEL

NExt Line

86

SSA

Start of Selected Area

87

ESA

End of Selected Area

88

HTS

Horizontal Tabulation Set

89

HTJ

Horizontal Tabulation with Justification

8A

VTS

Vertical Tabulation Set

8B

PLD

Partial Line Down

8C

PLU

Partial Line Up

8D

RI

Reverse line feed

8E

SS2

Single Shift 2

8F

SS3

Single Shift 3

90

DCS

Device Control String

91

PU1

Private Use 1

92

PU2

Private Use 2

93

STS

Set Transmit State

94

CCH

Cancel CHaracter

95

MW

Message Waiting

96

SPA

Start of Protected Area

97

EPA

End of Protected Area

98

SOS

Start Of String

99

SGCI

Single Graphic Character Introducer

9A

SCI

Single Character Introducer

9B

CSI

Control Sequence Introducer

9C

ST

String Terminator

9D

OSC

Operating System Command

9E

PM

Privacy Message

9F

APC

Application Program Command

When an attempt is made to open the JP1/IM - View Help from the Start menu, the HTML Help might be displayed in a Web browser that is already open.

Before restarting a connected host (JP1/IM - Manager), make sure that JP1/IM - View is disconnected from the host. The user can log in again to JP1/IM - View when the host is restarted.

On rare occasions, the window display might be garbled when an operation is performed in the window. Performing the operation again might correct the problem.

If a command that outputs large amounts of data is executed from the Execute Command window or by an automated action, output of data from the next command might be delayed.

Positioning the mouse pointer at a toolbar button of the Event Console window displayed behind the Tool Launcher, Execute Command, or the List of Action Results window in order to display ToolTip text may bring the Event Console window to the front. To bring the Tool Launcher, Execute Command, or the List of Action Results window to the front, click the corresponding taskbar button.

The following operations may cause CPU utilization rise to 100%, therefore taking a few minutes before a reply is returned.

Entering a long string in the text box of each configuration window, and pressing Home key or End key.

Entering a long string in the text box of each configuration window, and click the left button of the mouse in the text box in a short interval.

If it takes a long time to start the event console service due to such reasons as system load, and if the limits are exceeded in terms of the number of retries and interval of retries when connecting the Event Flow Control Service and the Event Console Service, the past events are no longer displayed in Monitor Events page and Severe Events page when JP1/IM - View is connected. Restart the Event Console Service, and ensure that "KAVB4754-l Event Console Server was connected." has been output to the integrated trace log, and then restart JP1/IM - View.

JP1/IM - View does not support characters in the JIS level-3 and level-4 kanji sets. These characters are corrupted in JP1/IM - View. Therefore, if they are used, JP1/IM - View might be unable to operate correctly.

Characters entered in JP1/IM - View windows are converted to UTF-8 format, in which zenkaku characters are represented by three or four bytes. Keep this in mind when entering zenkaku characters.

Do not use any environment-dependent character for definitions configured by JP1/IM -View. Such a character might cause character corruption.

Depending on the environment, window components such as buttons and menus may not be drawn correctly. If they are not drawn correctly, perform the following operations:

Resize the window.

Minimize the window, and then restore it to its previous size.

Close the window, and then re-open it.

Terminate (log out from) JP1/IM - View, and then log in again.

If JP1/IM - View becomes inoperable, close and restart the next viewer running from the Applications tab or Process tab of Task Manager.

"JP1 Central Console"

"JP1 Central Scope", or "Tree View"

"JP1 Configuration"

When the JP1/IM - View taskbar button is displayed in the taskbar, the JP1/IM - View window may not be displayed in the following cases:

When the virtual window configuration# is used, JP1/IM - View is terminated while a window area in which JP1/IM - View is not displayed is displayed.

#: A configuration providing an in-memory desktop that is wider than the displayable area and that is divided into areas, each of which can be displayed as a single desktop. This configuration is also referred to as a "virtual desktop."

If the window does not appear, press Alt + Tab a few times to select JP1/IM - View, and use any of the following operations to restore the window display:

In the taskbar, choose Cascade to display all windows in the cascaded format. Then, move and resize the JP1/IM - View window and other windows.

In the taskbar, choose Tile windows horizontally to display all windows one above the other. Then, move and resize the JP1/IM - View window and other windows.

In the taskbar, choose Tile windows vertically to display all windows side by side. Then, move and resize the JP1/IM - View window and other windows.

From the context menu of JP1/IM - View, choose Move. Then, use the cursor keys to move the window (or its frame) to the desired location, and press the Return key to fix it there.

From the context menu of JP1/IM - View, choose Maximize to maximize the window. With the window maximized, log out and log in again. Then, move and resize the window.

Do not use Fast User Switching to run JP1/IM - View programs as multiple users at the same time.

When you use the Web page call definition file from Tool Launcher to call a Web page for a different product, if the called Web page is in a different zone, the page might open in a different window for security reasons.To prevent a called Web page from opening in a different window, you must perform the following:

Register URL described in WWW page call definition file on the trusted site.

Disable protected mode in the security level for this trusted sites zone (default).

In order for JP1/IM - View to run normally, the corresponding DLL and OS-standard DLLs are required. If another product injects a DLL into a JP1/IM - View process, it will affect the behavior of JP1/IM - View. This might lead to unstable operation or prevent JP1/IM - View from starting. If this problem occurs, to identify the cause, you can ask the customer to confirm whether the same problem occurs when no other products are installed. If the customer cannot verify that a DLL being injected by another product is not the cause of the problem, Hitachi might not be able to provide normal support service.

Before changing the desktop theme or color scheme, be sure to close JP1/IM - View, which is activated first.

Depending on the desktop theme or color scheme being used, the screen might be difficult to read.

Depending on the desktop theme or color scheme, some deactivated display items might appear to be active, but still they cannot be operated.

For DPI scaling, specify 100% (96 DPI) for the font size to be used in windows.

If the font size is not 100% (96 DPI), windows might not be displayed correctly.

If DPI scaling is increased, the labels for JP1/IM - View windows might be displayed as "..." and the full text might not be displayed. Note, however, that this is an operating system setting, and some values may differ according to the version of the operating system you are using.

The minimum screen resolution required for using IM - View is 1024 x 768 pixels. If the screen resolution is smaller than 1024 x 768 pixels, the IM - View screen cannot be fully displayed.Note that this minimum resolution does not include the width of the taskbar.

If UAC (User Account Control) is enabled, when an administrator or standard user starts and uses JP1/IM - View to save displayed events, UAC redirects the file containing the data to a user-dependent virtual folder. The destination folders are as follows:

When redirected to %ProgramFiles%

%LocalAppData%\VirtualStore\Program Files

(The default folder is <system-drive>:\Users\<OS-user-name>\AppData\Local\VirtualStore\ProgramFiles)

When redirected to %WINDIR%

%LocalAppData%\VirtualStore\Windows

(The default folder is <system-drive>:\Users\<OS-user-name>\AppData\Local\VirtualStore\Windos)

When the displayed events are saved, the reply message (KAVB0321-Q or KAVB0322-Q) that appears contains the file name path that was specified before the redirection was performed.

About the icons displayed in the Visual Monitoring window

The icons in the Visual Monitoring window are associated with monitoring nodes in the monitoring tree. However, a monitoring tree that is different from the one that was used when the Visual Monitoring window was created may be updated using the central scope. If such an update has been made, the icons displayed in the Visual Monitoring window may not be associated with monitoring nodes as intended.

If the association between the icons and the monitoring nodes has been changed incorrectly, acquire the monitoring tree in the central scope, and re-edit the monitoring tree in the Visual Monitoring window.

The displayed menu doesn't disappear by moving the focus on another window or clicking the title bar in the window where the menu is displayed.

1.3.2 Notes on Integrated Operation Viewer Window

If you attempt to simultaneously display seven or more charts in the Trends tab of the Integrated Operation Viewer window, it might take time to display the charts depending on the number of concurrent connections set on the Web browser.

By setting the Web browser, you can configure windows invoked from the Integrated Operation Viewer window (Repeated event list window, and linked products' windows invoked from the Monitor button) to open in a new tab or a new window. If you use Chrome as the Web browser, these windows always open in a new tab.

You can set the Web browser as follows:

Open in a new tab (In Firefox)

In Firefox, select Options, Tabs, and then Open links in tabs instead of new windows.

In Firefox's address bar, enter about:config. In the displayed list of settings, search for browser.link.open_newwindow.restriction.

Change the value of the setting browser.link.open_newwindow.restriction to 0.

Open in a new window (In Firefox)

In Firefox, select Options and Tabs, and then clear Open links in tabs instead of new windows.

For user-defined characters, the following characters, and certain control codes (see Table 1-2 Target Control Codes ), characters may be garbled on-screen displays or may not be treated as such characters.

Table 1‒2:  Target Control Codes

Code

Value

Description

00

NUL

NULl (null)

01

SOH

Start Of Heading (Starting Headers)

02

STX

Start of TeXt (text-to-begin)

03

ETX

End of TeXt (end-of-text)

04

EOT

End Of Transmission (End of transmission)

05

ENQ

ENQuiry (inquiry)

06

ACK

ACKnowledge (acknowledgement)

07

BEL

BELl (bell)

08

BS

Back Space (backward)

09

HT

Horizontal Tabulation (horizontaltab)

0A

LF

Line Feed (line feed)

0B

VT

Vertical Tabulation (vertical-tab)

0C

FF

Form Feed (page feed)

0D

CR

Carriage Return (return)

0E

SO

Shift Out (Shift-out)

0F

SI

Shift In (Shift In)

10

DLE

Data Link Escape (transmission control extension)

11

DC1

Device Control 1 (device control 1)

12

DC2

Device Control 2 (device control 2)

13

DC3

Device Control 3 (device control 3)

14

DC4

Device Control 4 (device control 4)

15

NAK

Negative AcKnowledge (negative acknowledgement)

16

SYN

SYNchronous idle (Synchronization)

17

ETB

End of Transmission Block (transfer-block completion)

18

CAN

CANcel (Cancel)

19

EM

End of Medium (Media Termination)

1A

SUB

SUBstitute (Replace)

1B

ESC

ESCape (extended)

1C

FS

File Separator (File Separation)

1D

GS

Group Separator (group-separated)

1E

RS

Record Separator (record isolation)

1F

US

Unit Separator (unit separate)

7F

DEL

DELete (Remove)

80

PAD

PADding character (Pad Characters)

81

HOP

High Octet Preset (High Octet Preset)

82

BPH

Break Permitted Here (division enable)

83

NBH

No Break Here (division prohibited)

84

IND

INDex (Index)

85

NEL

NExt Line (carriage return line feed)

86

SSA

Start of Selected Area (Selection area starts)

87

ESA

End of Selected Area (selected area finished)

88

HTS

Horizontal Tabulation Set (horizontaltab)

89

HTJ

Horizontal Tabulation with Justification (Adjustable Horizontal Tab)

8A

VTS

Vertical Tabulation Set (vertical-tab)

8B

PLD

Partial Line Down (bottom line)

8C

PLU

Partial Line Up (ascending)

8D

RI

Reverse line feed (Previous page)

8E

SS2

Single Shift 2 (1 character shifted 2)

8F

SS3

Single Shift 3 (1-character shifted 3)

90

DCS

Device Control String (device control text)

91

PU1

Private Use 1 (Private use 1)

92

PU2

Private Use 2 (Private use 2)

93

STS

Set Transmit State (transmission status setting)

94

CCH

Cancel CHaracter (cancel character)

95

MW

Message Waiting (waiting for messaging)

96

SPA

Start of Protected Area (protected area started)

97

EPA

End of Protected Area (protected area terminated)

98

SOS

Start Of String (beginning of text)

99

SGCI

Single Graphic Character Introducer (beginning of single graphic character)

9A

SCI

Single Character Introducer (beginning with a single character)

9B

CSI

Control Sequence Introducer (Control Sequence Start)

9C

ST

String Terminator (end-of-string)

9D

OSC

Operating System Command(OS Commands)

9E

PM

Privacy Message (private messaging)

9F

APC

Application Program Command(AP Commands)

Integrated operation viewer does not support JIS level 3 and level 4 characters. If you use these characters on JP1/IM - View, garbled characters may occur, resulting in incorrect operation.

If you use environment-dependent characters in the definitions that you set with integrated operation viewer, garbled characters may occur in the definitions, so do not use them.

2 Integrated Operation Viewer Window

This chapter describes the items displayed and defined in the Integrated Operation Viewer window in the Intelligent Integrated Management Base.

2.1 Overview of the Integrated Operation Viewer window

When a user logs in to JP1/IM - Manager (Intelligent Integrated Management Base), the Integrated Operation Viewer window appears.

The Integrated Operation Viewer window consists of two areas: the Operating status area and the Details area. You can switch the display format of the Operating status area between the sunburst and tree chart format, or search results. In the Details area, you can change the tab to see the information of the IM management node selected in the Operating status area.

Important

Operation of the Integrated Operation Viewer window can not be done with the keyboard.

The figures below show examples of the Integrated Operation Viewer window.

Figure 2‒1: Operating status area in Integrated Operation Viewer window

The following describes the items displayed in the window:

File menu

Displays the following menu:

Log Out

Clicking it logs you out from the Integrated Operation Viewer window and then displays the Login window.

View menu

Displays the following menu:

Dashboard List

Display the Dashboard List dialog box.

List of Response Action Results

Display the List of Response Action Results window.

Option menu

This menu is used to configure the settings required for operation monitoring, configure the operation monitoring target, and execute operation of the functions used for operation monitoring. Click to display the next menu. Menus other than Run Response Action are displayed for users with JP1_Console_Admin privileges.

Issue Initial Secret

Display the Show Initial Secret window.

Set Up Definition Files for Managers

Displays the List of Definition Files for Managers window or the List of Definition Files(host-name) window.

Set UP Integrated Agents

Display the List of Integrated Agents window.

Add/Delete Lower Managers

Display the List of Lower Managers window.

Add/Delete IM Clients

Display the List of IM Clients window.

Run Response Action

Display the Run Response Action window.

Help menu

Displays the following menu items:

Online Manual

Displays the online manual. With the default settings of the Integrated Operation Viewer at the time of installation, clicking the Help button does not open the manual. For details about how to set up to display the manual in Windows or UNIX, see 1.24 Saving manuals to a computer (for Windows) or 2.22 Saving manuals to a computer (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide, respectively.

About

Displays the version of the Integrated Operation Viewer .

Login user name

Displays the name of the user currently logged in the Integrated Operation Viewer window.

Log Out button

Used to log out from the Integrated Operation Viewer window and display the Login window.

Tree path

Displays the tree path to the hierarchy selected in the Operating status area. At login, All Systems is displayed.

When you click a hierarchy name link, the window changes to show the information of the selected hierarchy.

If the area is not enough to show a tree path, you see the button on the left edge and the button on the right edge, which allow you to scroll the tree path. Click either of the buttons to scroll the path to the left or right.

Operation menu button

Shows the following operation menu items:

Copy tree URL

Copy tree SID

Copy tree path

Important

If you share or refer to the window in which you selected the IM management node, use the URL copied through Copy tree URL.

Operating status area

By default, this area is displayed in the sunburst chart format. You can switch the display format using icons. For details, see 2.5 Operating status area.

Details area

Displays the information of component selected in the Operating status area.

Tabs area

The Tabs area shows the information related to the component selected in the Operating status area on a tab basis. For details about each tab, see 2.6.1 Tabs area.

Events area

Lists the JP1 events occurring in the components selected in the sunburst chart, the tree chart, search results, or the Job flow or Related node tab.

For details, see 2.6.2 Events area.

Expand/Shrink button

Click this button if you want to close the area. To show the area, click it again. Drag it if you want to change the width of the area.

2.2 Windows related to Option

This section describes the windows displayed from the Option menu of Integrated Operation Viewer window. For details on the Run Response Action window, see 2.3 Window related to response action.

2.2.1 List of Integrated Agents window

The List of Integrated Agents window lists integrated agent host to be managed by Intelligent Integrated Management Base and add-on program that can be used for that host, so that the administrator knows about it.

If you need to remove integrated agent host from Intelligent Integrated Management Base managed, remove integrated agent host and add-on program associated with it. In addition, delete the trend data stored in the Trend data Management Database by Prometheus and Fluentd of the integrated agent host to be deleted. If you have user's own Prometheus or user's own Fluentd installed on your integrated agent host, the trend data is also deleted when they store trend data in Trend data Management Database.

You can also remove trend data stored in Trend data Management Database by integrated agent host's Prometheus and Fluentd, leaving Intelligent Integrated Management Base managed integrated agent host and the add-on features associated with it intact. If you have user's own Prometheus or user's own Fluentd installed on your integrated agent host, the trend data is also deleted when they store trend data in Trend data Management Database.

Figure 2‒2: List of Integrated Agents window

The items displayed in the List of Integrated Agents window are as follows.

Describes a criterion. A long description can be truncated and followed by an ellipsis (...). Click to view the complete description. Click to go back to the initial view.

Host name

Enter a text string up to 255 characters to filter the Integrated agent host list by host name.

You can enter single-byte alphanumeric characters, hyphens, and single-byte periods.

Search button

The host name in integrated agent host list is searched by a partial match of the character string entered in the text area of the Host name search, and the host that matches the criteria is displayed.

button (previous page)

Displays the previous page the Integrated agent host list.

Display range

Displays the number of integrated agent that correspond to the search criteria and the displayed range of the current page in the format of x to y/z.

button (next page)

Displays one page behind the Integrated agent host list.

Integrated agent host list

Lists integrated agent host that are requested to be registered by JP1/IM agent control base of integrated agent host and stored in Intelligent Integrated Management Database.

By default, host names are displayed in ascending order.

The maximum number of items displayed per page is 200. When the number of pages exceeds 200, use the Page button to switch between pages.

If there is no single data record to be displayed, NO DATA is displayed.

Select All/Clear All check box

Select the check box in the header of the List of Unified Agent hosts to select all Unified Agent hosts on the page you are viewing. To deselect all, click to uncheck it.

If you want to select only a particular integrated agent host, select the individual check boxes.

Host name

Displays the host name of integrated agent host.

OS

Displays OS of integrated agent host.

(e.g. Windows, Linux)

Integrated agent version

Displays integrated agent version in integrated agent host.

Manager host name

Displays the host name of the manager managing integrated agent.

Registration date/time

Displays the date and time integrated agent host was registered.

The date and time are displayed in the format "YYYY-MM-DD hh:mm:ss" according to the time zone set in the Integrated Operation Viewer.

The registration date and time are updated when you start JP1/IM - Agent after the following tasks:

Installing JP1/IM - Agent

Upgrading JP1/IM - Agent

Deleting JP1/IM - Agent in the List of Integrated Agents window

Set Up Definition Files button

■When there is one check in the Select check boxes of the Integrated agent host list

Clicking this button displays the List of Definition Files(host-name) window for integrated agent host checked in the Integrated agent host list.

■If there is no check in the Select check boxes in the Integrated agent host list or there are more than one check box

This button is inactive.

Set Up Secrets button

■When there is one check in the Select check boxes of the Integrated agent host list

Clicking this button displays the List of Secrets dialog box for integrated agent host checked in the Integrated agent host list.

■If there is no check in the Select check boxes in the Integrated agent host list or there are more than one check box

This button is inactive.

Distribute alert configuration file button

■When there is one check in the Select check box of the Integrated agent host list

Clicking this button displays the Distribute alert configuration file dialog box for the hosts checked in the Integrated agent host List.

■When there is no one check in the Select check box of the Integrated agent host list

This button is inactive.

Delete button

■When the Select check box in the Integrated agent host list is checked

When you click this button, a message window will appear asking you to confirm the deletion of the definition file. Clicking the OK button deletes the checked integrated agent host in the Integrated agent host list. In addition, any trend data stored in the Trend data Management Database by Prometheus and Fluentd of integrated agent host to be deleted will also be deleted. If you have user's own Prometheus or user's own Fluentd installed on your integrated agent host, the trend data is also deleted when they store trend data in Trend data Management Database.

Note

After deletion, the deleted information is not reflected in JP1/IM - Manager (Intelligent Integrated Management Base) tree information. To import tree information, you must generate and import tree information from integrated operation viewer, or execute jddcreatetree command and jddupdatetree command (specify the configuration change mode (-c option)).

■When even one of the Select check boxes in the Integrated agent host list is not checked

This button is inactive.

Delete trend data button

■When the Select check box in Integrated agent host List is checked

Clicking this button displays a message to confirm deletion of the trend data of integrated agent. When you click the OK button, the trend data saved in the Trend data Management Database by Prometheus and Fluentd of the checked integrated agent host in the Integrated agent host List will be deleted. If you have user's own Prometheus or user's own Fluentd installed on your integrated agent host, the trend data is also deleted when they store trend data in Trend data Management Database.

Note

After deletion, the deleted information is not reflected in JP1/IM - Manager (Intelligent Integrated Management Base) tree information. To import tree information, you must generate and import tree information from integrated operation viewer, or execute jddcreatetree command and jddupdatetree command (specify the configuration change mode (-c option)).

■When even one of the Select check boxes in the Integrated agent host List is not checked

This button is inactive.

Close button

Close the window.

(1) The Distribute alert configuration file dialog box

The Distribute alert configuration file dialog box is used to specify alert configuration file to be distributed using alert configuration file batch distribution function.

Figure 2‒3: Distribute alert configuration file dialog box

The following items are displayed in the Distribute alert configuration file dialog box.

Select Files (*.yml)

Displays alert configuration file that you specified for upload.

The maximum size of a file that can be specified is 10MB.

Browse button

Display the input screen for specifying the file to upload. If the specified filename is not jpc_alerting_rules.yml, the KAJY68127-E message is displayed.

Upload button

The upload confirmation screen is displayed.

OK Click this button to upload the specified file and add the uploaded file to the definition file list.

If reading of the specified file fails, the KAJY00032-E message is displayed.

If there is no entry in the text area of Select Files (*. zip), this button is inactive. The following items are displayed in the Distribute alert configuration file dialog box.

Close button

Close the window.

(2) The List of distribution results dialog box

The List of distribution results dialog box displays the results of distribution using alert configuration file batch distribution function for each destination host.

Figure 2‒4: List of distribution results dialog box

The display items of the List of distribution results dialog box are shown below.

List of distribution results

The results of alert configuration file bulk distribution feature are displayed for each destination host. If all results cannot be displayed in the list, a scroll bar appears. Each item in the list can be sorted by item name.

If there is no single data record to be displayed, "NO DATA" is displayed.

Host name

Displays the host name of the destination host.

Distribution result

Displays the distribution results of the destination host. One of the following distribution results is displayed:

Distributing

During distribution

Distribution failure

Success

Message

When Distribution result is Distribution Failed

The details of the error (the details of REST API returned) are displayed.

When Distribution result is Distributing, During Distribution or Success

Nothing is displayed.

Close button

Close the window.

2.2.2 List of Definition Files for Managers and List of Definition Files(host-name) windows

The List of Definition Files for Managers window is used by the administrator to operate JP1/IM - Manager definition files from Web GUI.

Figure 2‒5: List of Definition Files for Managers window

The List of Definition Files(host-name) window is used by the administrator to operate JP1/IM - Agent definition files from Web GUI.

Figure 2‒6: List of Definition Files(host-name) window

The following items are displayed on the List of Definition Files for Managers and List of Definition Files(host-name) windows.

Describes a criterion. A long description can be truncated and followed by an ellipsis (...). Click to view the complete description. Click to go back to the initial view.

Title

When the target is JP1/IM - Manager

Displays the List of Definition Files for Managers.

When the target is JP1/IM - Agent

Displays List of Definition Files(host-name).

Category tab

Display the category of the definition file displayed in the Definition file list in the tab. Depending on the definition file you want to view, the tabs in the following categories are listed from left to right. If both the category ID and category name are omitted, the definition file is displayed on the others tab. If there is no definition file to be displayed in the others tab, the others tab is not displayed.

For JP1/IM - Manager

jp1_central_console

jp1_intelligent

jp1_createtree

jp1_updatetree

Ascending order of user-created-definition file list definition file category names (UTF-8)

others

For JP1/IM - Agent

jp1_certificate

jp1_imagent

jp1_imexporter

jp1_imfluentd

Ascending order of user-created-definition file list definition file category names (UTF-8)

others

Definition file list

Displays a list of IM management node (JP1/IM - Manager or JP1/IM - Agent) definition files selected in the original Integrated Operation Viewer of this window. If there is no single data record to be displayed, NO DATA is displayed. The initial display is in ascending order of the file name.

Select check box

Select the line of the definition file that you want to download or delete.

File name

Displays the definition file name.

File path

Displays the file path of the definition file.

Last update

Displays the date and time when the definition file was last updated.

The date and time are displayed in "YYYY-MM-DD hh:mm:ss" format according to the time zone set on the Integrated Operation Viewer.

Delete button

■When the Select check box is selected in the Definition file list

When you click this button, a message window will appear asking you to confirm the deletion of the definition file. Clicking the OK button deletes the checked definition file in Definition file list.

■When there is no one check in the Select check box of the Definition file list

This button is inactive.

Download button

■When the Select check box is selected in the Definition file list

Clicking this button compresses the definition file with the check mark in the Definition file list to zip format, and downloads it the file name of the host-name-from-whichi-the-definition-file-was-obtained_ID.zip#.

■When there is no one check in the Select check box of the Definition file list

This button is inactive.

#

ID is given a unique ID for each download.

A compressed file contains a property file that contains information about the file to be downloaded, in addition to the entity of the definition file selected for download. The properties file contains the definition file name and information about the file path. For details about the properties file, see Definition file properties file (imdd_file_properties.json) and Definition file property file (jpc_file_properties.json) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Upload button

The Upload Definition Files dialog box appears.

Generate Tree Information button

This item is displayed when the jp1_createtree tab is selected. Click this button to display the Generate Tree Information dialog box.

Apply Tree Information button

This item is displayed when the jp1_updatetree tab is selected. Click this button to display the Apply Tree Information dialog box.

Close button

Close the window.

(1) Upload Definition Files dialog box

The Upload Definition Files dialog box is used to upload a definition file.

When you perform an upload, the commands required to change the configuration of the definition file (such as reloading) are also executed automatically after the upload.

Figure 2‒7: Upload Definition Files dialog box

The display items of the Upload Definition Files dialog box are shown below.

Select Files (*. zip)

Specifies to the compressed file# of the definition file to be uploaded as a character string of up to 200 bytes. Allowed characters are single-byte alphanumeric characters, single-byte spaces, "-", "_", ".". Control characters cannot be entered.

The maximum size of a file that can be specified is 10MB.

#

The name of the compressed file specified in the upload is arbitrary. The file format is the same as the compressed file to download.

In addition to the entity of the definition file to be uploaded, the compressed file must include a property file that contains information about the file to be uploaded. The property file contains the definition file name and information about the file path. For details about property files, see Definition file properties file (imdd_file_properties.json) and Definition file property file (jpc_file_properties.json) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Browse button

Display the input window for specifying the file to upload.

Upload button

The upload confirmation window is displayed.

Click the OK button to upload the specified file and add the uploaded file to the definition file list. #1

If there is no entry in the text area of the Select Files (*. zip), this button is inactive.

#1

Note the following when performing an upload:

Before updating the definition file, check Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference to make sure that the format and character code of the definition file are correct.

If the definition file is invalid, the update may fail. If updating of the definition file fails, an JP1 event is sent. Check the details of JP1 event that occurred and take appropriate action.

Some services are restarted automatically when you update the definition file. For the service to be restarted, see the explanation of each definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

When the service is restarted, monitoring may be temporarily stopped. In addition, in a clustered configuration, a failover may occur due to #2 of setting the outage detection times for the service targets monitored by the cluster software.

Therefore, update the definition file during maintenance.

#2

Depending on the specifications of the machine and the load on the system, the service is restarted for each update of one definition file, so the estimated stop detection time is about one minute for each definition file.

For example, if you are updating 10 definition files at the same time, specify 10 minutes as the cluster software stop detection time.

If you cannot increase the detection time, log in to the host without using the definition file operation facility and update the definition file directly.

Close button

Close this dialog box.

(2) Generate Tree Information dialog box

The Generate Tree Information dialog box is used to generate tree information in the integrated manager.

Figure 2‒8: Generate Tree Information dialog box

The display items of the Generate Tree Information dialog box is shown below.

OK button

Click this to request the manager specified in the integrated manager host to generate tree information.

Cancel button

Close this dialog box.

(3) Apply Tree Information dialog box

The Apply Tree Information dialog box is used to reflect the tree information in the integration manager.

Figure 2‒9: Apply Tree Information dialog box

The display items of the Apply Tree Information dialog box is shown below.

OK button

Clicking this button imports IM management node-related files tree into Intelligent Integrated Management Base and creates IM management node.

Application method

Select the reflection method from the pull-down menu. The default is Configuration change mode.

New and rebuilding mode: Specify this in the following cases:

- New build

- Fixing build errors

- When the IM database is backed up (jimdbbackup command) and recovered (jimdbrecover command)

- When the Integrated monitoring DB is unset (jcodbunsetup command) and re-set up (jcodbsetup command)

- Upgrading JP1/IM - Manager in an environment that uses an Intelligent Integrated Management infrastructure

- Configuration change mode: In addition to correcting construction errors, it is specified when the addition, deletion, and modification of the management of the Intelligent Integrated Management infrastructure are reflected.

Configuration change mode: Specify this mode to reflect addition, deletion, or modification of Intelligent Integrated Management Base managed objects in addition to the modification of build errors.

Cancel button

Close this dialog box.

(4) List of Secrets dialog box

The List of Secrets dialog box is a window for managing secrets used by integrated agents.

Figure 2‒10: List of Secrets dialog box

The display items of the List of Secrets dialog box are shown below.

Title

Displays the List of Secrets(host-name). The host name is the host name of the target integrated agent.

Secret key

Enter the secret key to be added, up to 1024 characters. Characters within ASCII code 0x20 to 0x7E can be entered.

Secret

Enter the secret to add, up to 1024 characters. Characters within ASCII code 0x20 to 0x7E can be entered. The entered characters are displayed in the abbreviation of • •.

Add button

You can add the contents entered in Secret key and Secret to the List of Secrets. Add is displayed in Changes made of the added secret.

Show Only Updated Secrets check box

When this check box is selected, only secrets whose changes are not blank are displayed in the List of Secrets.

List of Secrets

Lists the secrets that are managed on the target host in ascending secret key order. You can sort by the Secret key column. 10 items are displayed in the list. The number of items displayed per page is 200. A scroll bar appears if you cannot list all secrets.

If there is no single secret, NO DATA is displayed.

button (previous page)

Displays the previous page of the secret list.

Display area

Displays the number of secrets that correspond to the search conditions and the displayed area of the current page in the format of "x to y/z".

button (next page)

Displays the next page of the secret list.

Secret key search

Enter the secret key to be searched, up to 1024 characters. Characters within ASCII code 0x20 to 0x7E can be entered. Filter the secret list by secret key with the entered character string.

Search button

Performs a partial search with the contents entered in the secret key search and displays the search results in the secret list.

Delete check box

Check the row of the secret you want to delete.

Changes made

The following items are displayed according to the settings.

Initial State

Operation Description

Add

Update

Deleted

Blank

-

Update

Deleted

Add

-

Add

Disappear the run

Update

-

Update

Deleted

Deleted

Update

Update

Deleted

Secret key

The secret key is displayed.

Secret

The secret is displayed in ** asterisk.

Edit button

Click this button to display the Edit Secret dialog box.

Secret key

The selected secret key in the List of Secrets dialog box is displayed. Cannot be edited.

Secret

Enter the secret to edit using up to 1024 characters. You can enter characters within 0x20 to 0x7E of ASCII codes. The entered characters are displayed in the abbreviation of • •.

Update button

The edited contents are reflected in the List of Secrets dialog box. Update is displayed in Changes made of the target secret.

Cancel button

Close the dialog box.

Delete button

Delete is displayed in Changes made of the secret of the row selected by the Delete check box.

Apply button

A confirmation window for adding, updating, or deleting a secret appears. Click the OK button to apply the addition, update, or deletion of the secret to the target host.

Close button

A confirmation window for the exit of the List of Secrets dialog box appears. Click the OK button to close the List of Secrets dialog box.

2.2.3 Show Initial Secret window

The Show Initial Secret window is for displaying the issued initial secret.

Figure 2‒11: Show Initial Secret window

The following shows the items displayed in the Show Initial Secret window.

Initial secret

Displays the initial secret that was issued.

Issue button

Clicking this button displays a window for confirming the issuance of initial secret. Clicking the OK button issues the initial secret.

Copy button

Click to copy the contents of the initial secret to the clipboard.

Close button

Close this window.

2.2.4 List of IM Clients window

The List of IM Clients window displays a list of registered IM clients. You can also add IM clients, retrieve IM client secrets, and delete registered IM client information.

Figure 2‒12: List of IM Clients window

The following shows the items displayed in the List of IM Clients window.

List of IM clients

Lists the IM client that the manager authentication for. Defaults to ascending order of IM client ID. It can be sorted in the IM client ID column.

10 items are displayed in the list. If all IM client cannot be listed, a scroll bar is displayed.

Select check box

Select the row for IM client ID that you want to remove.

IM client ID

Displays ID of the registered IM client secret.

If it cannot be displayed completely, "..." is displayed at the end.

IM client secret

IM client secret is displayed in ** abbreviation.

Copy button

The Copy button is displayed only in the line of the IM client added in the Add IM Client dialog box. When clicked, IM-client-ID:IM-client-secret is copied to the clipboard.

Add button

Click this button to display the Add IM Client dialog box.

IM client ID

Enter a ID for IM client secret, up to 280 characters. You cannot specify the same ID as an added ID.

Characters that can be entered include ASCII code 0x20 to 0x7e excluding the colon ":". The following characters cannot be entered.

Characters beginning with AGENT_

Characters beginning with MANAGER_

Add button

When clicked, creates and adds a IM client secret with the entered IM client ID.

Delete button

Click this button to display a window confirming the deletion. Clicking the OK button deletes client secret of IM client ID selected in the Select check box.

Close button

Close this window.

2.2.5 List of Lower Managers window

The List of Lower Managers window is used to manage the secret used for communication with lower manager.

Figure 2‒13: List of Lower Managers window

List of Lower Managers

Lists lower manager. The default is ascending order of the host name. You can sort by the host name column.

Select check box

Select the row for the host name that you want to delete.

Host name

Displays the host name on which lower manager is installed.

Delete button

Click this button to display a window for confirming the deletion. Click the OK button to delete the host name selected in the Select check box.

Add button

The Add Lower Manager dialog box appears.

Host name

Enter the host name of lower manager, up to 255 characters. You can enter the following characters:

Numbers (ASCII code 0x30 to 0x39), lowercase letters (0x61 to 0x7a), uppercase letters (0x41 to 0x5a), hyphens (-) (ASCII code 0x2d), periods (.) (ASCII code 0x2e)

Note that hyphen "-" and period "." cannot be used at the beginning.

Initial secret

Enter a initial secret, up to 1024 characters. Characters within ASCII code 0x20 to 0x7E can be entered. The entered characters are displayed in the asterisk of **.

Add button

Add the content you entered to lower manager info. If Host name or Initial secret is blank, this button is inactive.

Close button

Close this window.

2.3 Window related to response action

This section describes the windows related to response action.

2.3.1 Run Response Action window

The Run Response Action window is for manually executing response action. You can start the Run Response Action window in one of the following ways:

For response action associated with event-information

In the Operation menu, click the Run Response Action (Event information inheritance) menu.

In the Event details dialog box, click the Run Response Action button.

When response action is not associated with the event-information

From Integrated Operation Viewer window Option menu, select the Run Response Action menu.

Action type

Select the type of action to be executed from the pull-down menu.

cmd: Execute with command.

restApi: Run in REST API.

eventStatus: Changes the response status of an event.

jump: Jumps to the specified URL.

The displayed window differs depending on the type of action selected.

(1) When cmd is selected as an action type

The following explains when cmd is selected as the action type.

Figure 2‒14: Run Response Action window (when the action type is cmd)

Event information to inherit

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

Inherit event information check box

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

Target host

Specify the host name under which response action is to be executed, up to 255 bytes.

Command

Specifies the command line to be executed.

You can specify a command line of up to 4096 bytes.

Attribute information of JP1 event displayed in the Event information to inherit can be passed as a parameter of the command using a variable. For details about the variables that can be specified, see 7.8 Response actions manual execution inheritance function in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Environment variable file

Specifies the name of environment variable file stored on the host where response action is executed, as a full path of no more than 255 bytes.

Action name

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action to see the history of the actions taken.

Execute button

The following occurs depending on whether the Inherit event information check box is selected in the Event information to inherit.

When the Inherit event information check box is selected

The Preview Execution Script of Response Action window is displayed.

When the Inherit event information check box is not checked

Executes the specified response action.

Execution history

Display the execution history list. When you hover over a line in the execution history, the tooltip text displays its contents.

A maximum of 100 execution histories are displayed. When the number exceeds 100, the oldest one is deleted from the oldest one.

(2) When restApi is selected as an action type

The following explains when restApi is selected as the action type.

Figure 2‒15: Run Response Action window (when the action type is restApi)

Event information to inherit

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

Inherit event information check box

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

Method

Select REST API method from the pull-down menu.

GET

HEAD

POST

PUT

PATCH

DELETE

OPTIONS

TRACE

URL#

Specifies URL of REST API, up to 2046 bytes.

Request header#

Specifies REST API request header in object format. Specify within 65,536 bytes.

Body#

Specifies the body of REST API in an object format. If you specify GET or DELETE in the Method, you can omit it if you do not need the body. If it exceeds 10MB(10,485,760 byte), an error will occur.

Action name

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action to see the history of the actions taken.

Execute button

The following occurs depending on whether the Inherit event information check box is selected in the Event information to inherit.

When the Inherit event information check box is selected

The Preview Execution Script of Response Action window is displayed.

When the Inherit event information check box is not checked

Executes the specified response action.

Execution history

Display the execution history list. When you hover over a line in the execution history, the tooltip text displays its contents.

A maximum of 100 execution histories are displayed. When the number exceeds 100, the oldest one is deleted from the oldest one.

#

Attribute information of JP1 event displayed in the Event information to inherit can be passed as a parameter using a variable. For details about the variables that can be specified, see 7.8 Response actions manual execution inheritance function in the JP1/Integrated Management 3 -Manager Overview and System Design Guide.

(3) When eventStatus is selected as an action type

The following explains when eventStatus is selected as the action type.

Figure 2‒16: Run Response Action window (When the action type is eventStatus)

Event information to inherit

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

Inherit event information check box

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

Response status

Specify the response status. The default is Unprocessed.

Unprocessed

Processed

Processing

Held

JP1 Events SID, ...

Specifies SID of JP1 events for which you want to obtain response status. If you want to specify SID for more than one JP1 event, specify SID of JP1 event concatenated with ",". You can specify up to 2000 SID. An error occurs if the value is 10MB or higher.

The attribute information of JP1 event displayed in the Event information to inherit can be passed as a parameter of SID of JP1 event using a variable. For details about the variables that can be specified, see 7.8 Response actions manual execution inheritance function in the JP1/Integrated Management 3 -Manager Overview and System Design Guide.

Action name

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action to see the history of the actions taken.

Execute button

The following occurs depending on whether the Inherit event information check box is selected in the Event information to inherit.

When the Inherit event information check box is selected

The Preview Execution Script of Response Action window is displayed.

When the Inherit event information check box is not checked

Executes the specified response action.

Execution history

Display the execution history list. When you hover over a line in the execution history, the tooltip text displays its contents.

A maximum of 100 execution histories are displayed. When the number exceeds 100, the oldest one is deleted from the oldest one.

(4) When jump is selected as an action type

The following explains when jump is selected as the action type.

Figure 2‒17: Run Response Action window (When the action type is jump)

Event information to inherit

Displays events that are inherited by response action executable (events subject to inheritance). If there are no JP1 events, they are inactive.

Inherit event information check box

Checked when inheriting the information of the event subject to inheritance to the execution content of response action.

If it is not checked, it will not be inherited.

URL#

Specify URL to be jumped to, up to 2046 bytes.

Specify "http://", "https://", or "index?" at the beginning.

The following characters can be specified:

Single-byte alphanumeric characters and ";", "/", "?", ":", "@", "&", "=", "+", "$", ",", "-", "_", ".", "!", "~", "*", "'", "(", ")", "%"

HTML "target" attribute#

Specifies target of HTML when opening the jumped URL, up to 64 bytes.

The following characters cannot be specified:

_self

_parent

_top

Value starting from JP1IM_

If a character that cannot be specified is included when the Execute button is clicked, KAJY64703-E messaging window is displayed.

If the specification is omitted, _blank is assumed.

If a URL beginning with index is specified for URL, this specification is ignored.

Action name

Specify the action name within 50 bytes.

It is recommended that you enter a meaningful name for each response action.

Execute button

The following occurs depending on whether the Inherit event information check box is selected in the Event information to inherit.

When the Inherit event information check box is selected

The Preview Execution Script of Response Action window is displayed.

When the Inherit event information check box is not checked

Executes the specified response action.

#

Attribute information of JP1 event displayed in the Event information to inherit can be passed as a parameter using a variable. For details about the variables that can be specified, see 7.8 Response actions manual execution inheritance function in the JP1/Integrated Management 3 -Manager Overview and System Design Guide.

2.3.2 Preview Execution Script of Response Action window

The Preview Execution Script of Response Action window displays the execution contents specified in the Run Response Action window by replacing the specified variable with the event information. You can check whether response action has been successfully replaced prior to executing it, or whether response action has been executed properly.

Figure 2‒18: Preview Execution Script of Response Action window (When cmd is specified as action type in Run Response Action window)

Figure 2‒19: Preview Execution Script of Response Action window (When restApi is specified as action type in Run Response Action window)

Figure 2‒20: Preview Execution Script of Response Action window (When eventStatus is specified as action type in Run Response Action window)

Figure 2‒21: Preview Execution Script of Response Action window (When jump is specified as action type in Run Response Action window)

Action type

Displays the type of the specified action.

A is displayed next to the label if one of the following conditions is true:

Upper limit exceeded due to variable expansion

Attribute corresponding to variable does not exist

Attribute value of the attribute corresponding to the variable is empty

Invalid encoding specification format for a variable

Invalid type specification for a variable

Target host

Displays the host name under which response action runs.

Command

Displays the command line to be executed.

Environment variable file

Displays the name of environment variable file stored on the host where response action runs.

URL

Displays URL of REST API.

Request header

Displays the request header of REST API in object format.

Body

Displays the body of REST API in an object format.

Response status

This displays the response status.

JP1 Events SID, ...

Displays SID of JP1 events for which you want to obtain response status.

URL

Displays the destination URL.

HTML "target" attribute

Displays target properties of HTML when opening the jumped URL.

Execute button

Run response action.

Cancel button

Close the Preview Execution Script of Response Action window.

2.3.3 List of Response Action Results window

The List of Response Action Results window is a list window for checking the results of action execution. The List of Response Action Results window is launched in one of the following ways:

For response action associated with event-information

In the Operation menu, click the Show Response Action Results button.

In the Event details dialog box, click the Show Response Action Results button.

When response action is not associated with the event-information

From Integrated Operation Viewer window View menu, select the List of Response Action Results menu.

(1) Search conditions settings in the List of Response Action Results window

When you set a search condition in the Search conditions, you can filter and view response action results. If search conditions are specified for more than one item, the search is executed using AND conditions.

Figure 2‒22: Example of Search conditions setting

Search conditions

Click the Collapse menu to open or close the search criteria settings window. If you close the menu, you cannot set search conditions.

When transitioning from the display menu, the initial display is set to the "Display" state.

Action name

Specify the action name.

In the list box on the left, select either RegExp or ExactMatch as the condition for the specified string.

Response action SID

Specifies the name of response action SID.

In the list box on the left, select either RegExp or ExactMatch as the condition for the specified string.

Return value

Specifies the return value of the executed action.

In the list box on the left, select either RegExp or ExactMatch as the condition for the specified string.

Target host

Specifies the host name in which response action was executed.

In the list box on the left, select either RegExp or ExactMatch as the condition for the specified string.

Reception time

Specify response action entry time to be searched in the following format:

Specify in YYYY-MM-DD HH:MM:SS format.

Action status

Check the action state to be searched.

Sending

Ended

Unexecutable

Queued

Unknown

Communication failed

Running

None

Execution failed

Search button

Performs a search based on the specified search conditions.

Acquires the latest 100 events and displays them in the search result list.

Clear Conditions button

Clears the specified search condition.

Oldest button

Displays 100 older response action results starting from the oldest response action results displayed in the search results list.

Previous button

The 100 items on the previous page of the search result list are displayed.

Next button

The 100 items on the next page of the search result list are displayed.

Latest button

Displays 100 older response action results starting from the most recent response action results in the search results list.

Refresh button

Refreshes the display contents of the Search result list. Click this button to cancel the selected item.

Select All/Clear All check box

Select the check box in the search results list header to select all response action results in the search results list. To deselect all, click to uncheck it.

If you want to select only certain response action findings, select the individual check boxes.

Search result list

Displays a list of response action searches. If there is no search result, NO DATA is displayed.

Search for target events button

Searches for the event that triggered the action of response action result selected in the execution result list. If you select more than one action result, this button is inactive.

2.3.4 Response Action Results window

The Response Action Results window is used to check the details of response action execution results. Displayed when Details button in the List of Response Action Results window is clicked.

The displayed contents differ depending on the type of action.

Figure 2‒23: Example of displaying the Response Action Results window (When the action type is cmd)

Figure 2‒24: Example of displaying the Response Action Results window (When the action type is restApi)

Figure 2‒25: Example of displaying the Response Action Results window (When the action type is eventStatus)

Response action SID

Displays SID of response action.

Target host

Displays the host name to be executed.

Action name

Displays the action name.

Action type

Displays the action type.

cmd

restApi

eventStatus

Command

If the action type is cmd, the command name is displayed.

Environment variable file

If the action type is cmd, the environment variable file is displayed.

Action status

Displays a string representing the execution state of the action.

Execution-target SID

Displays SID to be executed.

Execution trigger

Displays the trigger event.

auto: Auto response action

manual: Manual response action

Trigger details

Displays detailed information about the trigger event.

Reception time

Displays response action entry time in "YYYY-MM-DD HH:MM:SS" format.

Start time

Displays response action input time in "YYYY-MM-DD HH:MM:SS" format.

End time

Displays response action ending time in "YYYY-MM-DD HH:MM:SS" format.

Return value

Displays the return value.

Execution results

Displays the execution result.

Message

Displays the message that was output when the action was executed.

Method

Displays the method if the action type is restApi.

URL

If the action type is restApi, a URL is displayed.

Request header

Displays the request header if the action type is restApi.

If the character string is in JSON format, it is converted to JSON character string and displayed.

Body

Displays the body if the action type is restApi.

If the character string is in JSON format, it is converted to JSON character string and displayed.

Response status

Displays the response status if the action type is eventStatus.

JP1 event SID

Displays SID of JP1 events if the action type is eventstatus

If the content of the Response Action Results window is long, to cut off the display in the middle, Displays a "..." at the end of the string.

When a character string is truncated, the contents are displayed in the tooltip when the mouse cursor is hovered.

2.4 Dashboard window

This section describes the Dashboard window.

2.4.1 Configuring the Dashboard tab

The following is an example of the Dashboard tab.

Figure 2‒26: Example of how the Dashboard tab appears

(1) Dashboard Display area

The Dashboard Display area displays the window according to the contents of the menu selected in the Side menu.

Figure 2‒27: Example of display in the Dashboard Display area

The following are the display items:

Side menu button

Display the side menu. The side menu displays a list of Home and favorites.

List of dashboards added to favorites

The names of the dashboards you have added to your favorites are displayed in a list. When you click the dashboard name, the corresponding dashboard window is displayed in the Dashboard Display area. When you click Home to display, the dashboard window corresponding to the selected node is displayed.

Display target date and time

The start and end date and time of the data to be displayed are displayed.

If you want to change the display target range, click to display the Display range setting dialog box.

When you click the pull-down menu of Specification method, you can select Display until the current date and time, Before and after the current date and time, Before or after the specified date and time, Specify end time, Specify start time, and Start time and end time.

If you specified Before and after the current date and time as the specification method, specify Past range and Future range. You can specify the value of the range by clicking the value (1h,3h,12h,1d, or 1w) on the right or by typing. For direct entry, specify an integer value greater than or equal to 1 and a unit (m,h,d, or w).

The display period can also be set directly as follows:

1h: 1 hour

2d: 2 day

3w: 3 week

Update button

Click to update the latest status.

Update interval

click to select the interval at which the data displayed in the dashboard is refreshed from the pull-down menu. The default is 10 minutes.

Manual

1 minute

5 minutes

10 minutes

15 minutes

30 minutes

1 hour

Panel Display area

Multiple panels that you have created are displayed.

Miscellaneous Dashboard operations

Click on the dashboard to display the dashboard operation menu.

Open in another window: Displays the dashboard in a separate window.

Full screen display: Displays the dashboard in full screen.

Copy dashboard URL: Copy the dashboard URL.

Add to favorites, Remove from favorites: Add or unsubscribe favorites.

Edit: Switch to the Setting Dashboard window.

Duplicate dashboard: Duplicate the dashboard and switch to the Setting Dashboard window.

Output CSV: Converts the data in all panels of the dashboard you are viewing into CSV files for each panel, and then archives and downloads them as a zip file.

(a) Panel operation

Describes the operation of the panels displayed in the dashboard that is being monitored.

Various panel operations

Maximize: Maximize the appropriate panel. The maximized panel returns to its original size by clicking on the upper right demaximize.

Comparison: Displays a new dashboard with only the panel you are currently viewing and two panels with different ranges. It is used when you want to refer to a comparison with the past time zone, such as a trend graph.

When you click the Comparison, the Display range setting dialog box is displayed.

You can specify the panel in the same way as the dashboard display range setting.

Edit: Switch to the panel edit window.

Create dashboard: Switch to the dashboard creation window.

Approximate straight line (y-axis): Choose to show or hide Approximate straight line on the y-axis. If Approximate straight line is set to be displayed, is displayed when , is hidden.

Approximate straight line (y2-axis): Choose to show or hide Approximate straight line of y2 axis. If Approximate straight line is set to be displayed, is displayed when , is hidden. This menu appears only if the panel type is Trend and the y-axis is enabled.

Output CSV: Converts the data in the displayed panel to a CSV file and downloads it.

(b) Dashboard List dialog box

Select View - Dashboard List from the integrated operation viewer menu to display the Dashboard List dialog box.

If the dashboard list collection/deletion function for administrators is enabled, you can list and delete dashboard definitions for all JP1 users if the JP1 resource group is "*" and you are logged in as a JP1 user with JP1_Console_Admin privileges. For details, see 3.2.4 Dashboard Import / Export Function and Expanded Delete Function in the manual JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Following shows the example of displaying the Dashboard List dialog box:

Figure 2‒28: Example of displaying the Dashboard List dialog box

Click to display a sidebar with a list of your favorite dashboards. When you select a dashboard in the list, the selected dashboard is displayed.

New button

Click this button to display the Setting Dashboard window. You can add dashboards.

Full-text search

You can search for the full text, such as the title of the dashboard.

Click to delete the selected dashboard.

Select/Deselect check box

Select the check box in the header to select all dashboards. Click again to clear the full selection.

If you want to select only specific dashboards, select the individual check boxes.

Click to update the dashboard list.

ID

Displays the ID of the dashboard that was automatically numbered by the system.

Title

The title of the dashboard. Click to switch to the monitoring window of the selected dashboard.

Favorite

By clicking , add favorite to the dashboard and switch the icon to . For dashboards that have already been added to favorites, click to remove the favorite and switch the icon to .

: Dashboards that are registered as favorites

: Dashboards that are not registered as favorites

Visibility

From the pull-down menu, select the visibility of the dashboard.

Private: Visible only to the owner.

public: Visible to users other than the JP1 user who created it.

Owner

Displays the JP1 username that owns the dashboard.

Updated date and time

Displays the date and time when the dashboard title was last modified.

Node name

The node name associated with the dashboard is displayed.

2.4.2 Setting Dashboard window

The Setting Dashboard window is a window for creating or editing new dashboards. This is displayed when you click the New button in the Dashboard List dialog box or click Edit from the Operation menu on the Dashboard tab.

The following shows an example of the Setting Dashboard window.

Figure 2‒29: Setting Dashboard window

Dashboard name

Specify the dashboard name up to255 character.

Display target date and time

The start and end date and time of the data to be displayed are displayed.

When selected, the Display range setting dialog box is displayed.

Update interval

Select the interval at which the data displayed in the dashboard is refreshed from the pull-down menu. The default is 10 minutes.

Manual

1 minute

5 minutes

10 minutes

15 minutes

30 minutes

1 hour

Finish

Do not save the contents and end the edit.

Save button

Save your edits.

Add panel button

Clicking this button displays the Add panel window.

Miscellaneous Dashboard operations

Clicking this button displays the various setting menus in the pull-down menu.

Layout:Column

Set the number of panel to display next to the dashboard.

You can set a value from 1 to 8.

Delete all panels

Deletes all panels in the dashboard.

Delete dashboard

Delete the dashboard you are configuring.

2.4.3 Add panel window

Clicking the Add panel button in the Setting Dashboard window displays the Add panel window.

The following shows an example of the Add panel window.

Figure 2‒30: Add panel window

Panel name

Specify the panel-name up to 255 characters.

Panel type

Select the panel type you want to add from the pull-down menu.

The eight panel types are Trend, Ranking, Numerical value, Gauge, Alert information, Node state, Node state map, and Text. Depending on the selected panel type, different display items can be set.

(1) Trends

If you select Trend as the panel type, the trend data (time-series data) of various metric such as CPU utilization of the specified node is displayed in the panel in a graphical format. It is used for analysis at the time of failure and estimation of future trends.

The following shows an example of the display when Trend is selected in the panel type.

Figure 2‒31: Display example when Trend is selected as the panel type

Target metric

Select the target metric from the pull-down menu. Metrics include CPU utilization and free disk space.

Target node

Set target node by clicking the Add button.

Display options

Select a display format and legend from the pull-down menus.

Display format

Select one of the following display formats from the pull-down menu:

Line graph

Bar graph

Legend

Select the display position of the legend from the next pull-down menu.

Hidden

Bottom

Stacked graph

Select whether to enable the display in the stacked graph. When this is activated, the values of the selected nodes are stacked and displayed.

Area chart

Select whether to enable display in area graphs. This can be specified when the Line graph is set in the Display format.

Point radius

Specifies the size of the plot. This can be specified when the Line graph is set in the Display format.

Number of plots

Specifies the number of trend data to use for the graph display.

Grid

Determines whether the graph displays a grid. The default is on.

Minimum value

Specifies the minimum value for the axis of the graph.

Maximum value

Specifies the maximum value for the axis of the graph.

Approximate straight line

Specifies whether Approximate straight line is to be displayed.

y2-axis

When this button is clicked, the Enable y2 axis button is displayed. Click the button to create a graph with two axes. Setting items are the same as for y1-axis.

(2) Ranking

If you select the Ranking as the panel type, you can select more than one target node and view it as a ranking. It is easier to compare with other nodes.

The following shows an example of the display when the Ranking is selected for the panel type.

Figure 2‒32: Display example when Ranking is selected as the panel type

Target metric

Select target metric from the pull-down menu. Metric can include CPU utilization, free disk space, and so on.

Target node

Set target node by clicking the Add button.

Display options

Select Sort from the pull-down menu.

Descending order

Ascending order

Number of plots

Specifies the number of trend data to use for the graph display. The ranking panel displays the latest values of this trend data.

(3) Numerical value

When the Numerical value is selected as the panel type, the latest trend data of the specified node is displayed in numerical format. Use this format for operations that want to check only the most recent metric. Large numbers are displayed so that you can check specific values from a distance.

If you want to monitor the color change of the numerical panel, use it in the case where values such as usage rate and usage are monitored for increase.

The following shows an example of the display when the Numerical value is selected for the panel type.

Figure 2‒33: Display example when Numerical value is selected as the panel type

Target metric

Select target metric from the pull-down menu. Metrics include CPU utilization, network transmission speed, and so on.

Target node

Click the Add button to set the target node.

Display options

Select the value to be displayed from the pull-down menu. The default is Total value.

Total value

Average value

Specify Minimum value, Alert value, Danger value, or Maximum value, When the set value is exceeded, the panel color changes.

Minimum value: Specify the minimum value. The default is 0.

Alert value: Specify the warning value. The default is 60.

Danger value: Specify the hazard value. The default is 80

Maximum value: Specify the maximum value. The default is 100.

The following table shows the meaning of panel colors.

Red: When the value of Danger value is exceeded

Orange: When the value of Alert value is exceeded and the value is less than or equal to the Danger value.

Green: If the value is less than or equal to the number of Alert value or if Alert value or Danger value is not specified

Number of plots

Specifies the number of trend data to use for the graph display. The numerical value panel displays the most recent value of this trend data.

(4) Gauge

When the Gauge is selected as the panel type, the latest trend data of the specified node is displayed in gauge format. It is used for operations where you want to check only the value of the most recent metric. Large display on gauge, so you can check if it is in Minor or Critical area from a distance.

If you want to monitor the color change of the gauge panel, use it in the case of monitoring the increase in values such as usage rate and usage.

The following shows an example of the display when the Gauge is selected in the panel type.

Figure 2‒34: Display example when Gauge is selected as panel type

Target metric

Select target metric from the pull-down menu. Metrics include CPU utilization, network transmission speed, and so on.

Target node

Set target node by clicking the Add button.

Display options

Select the value to be displayed from the pull-down menu. The default is Total value.

Total value

Average value

Specify Minimum value, Alert value, Danger value, or Maximum value. When the set value is exceeded, the panel color changes.

Minimum value: Specify the minimum value. The default is 0.

Alert value: Specify the warning value. The default is 60.

Danger value: Specify the hazard value. The default is 80

Maximum value: Specify the maximum value. The default is 100.

The following table shows the meaning of panel colors.

Red: When the value of Danger value is exceeded

Orange: When the value of Alert value is exceeded, and the value is less than or equal to the Danger value.

Green: If the value is less than or equal to the number of Alert value or if Alert value or Danger value is not specified

Number of plots

Specifies the number of trend data to use for the graph display. The gauge panel displays the most recent value of this trend data.

(5) Alert information

When the Alert information is selected as the panel type, the number of alerts occurring under the target node is displayed. Alerts are displayed when a certain period of time has passed when the metric exceeds the threshold and is canceled when the threshold is less than or equal to the threshold.

The following shows an example of the display when the Alert information is selected in the panel type.

Figure 2‒35: Display example when Alert information is selected as the panel type

Target node

Set target node by clicking the Add button.

Display options

You can narrow down the alerts that you want to view. You can also specify only the Alert name for the alert that is displayed.

In the donut chart, the number of alerts per severity is displayed.

Red: Emergency/Alert/Critical

Orange: Error

Yellow: Warning

Green: Notice/Information/Debug

Gray: Others

Click the Alert information panel to display the Instance list window.

Instance list window

Node name: Displays the node on which the alert occurred.

Severity: Displays the severity of the alert.

Alert name: Displays the type of alert that occurred.

Time when threshold was exceeded: Displays the time when the threshold was exceeded.

It becomes an alert state at the time when the time specified in the alert definition has elapsed since the threshold was exceeded.

Time when threshold was exceeded is the first time the threshold was exceeded. This is different from the time when an alert state was triggered after a certain amount of time after being exceeded.

(6) Node state

Select the Node state as the panel type to display the status of the specified IM management node. Displays the status of the selected node.

The following shows an example of the display when the Node state is selected in the panel type.

Figure 2‒36: Example of display when Node statue is selected as the panel type

Target node

Set target node by clicking the Add button.

The meaning of the panel color of the node state is as follows:

Red: Emergency/Alert/Critical

Orange: Error

Yellow: Warning

Green: Normal/Resolved

Blink setting

The default for blinking is Never.

Warning button: When enabled, the entire node state panel flashes when the target node is in the Warning state.

Error button: When enabled, the entire node state panel flashes when the target node is in the Error state.

Emergency button: When enabled, the entire node state panel flashes when the target node is in the Emergency/Alert/Critical state.

(7) Node state map

When the Node statue map is selected as the panel type, the status of the specified node is displayed on the background image. You can also display multiple nodes.

When the Node statue map is selected in the panel type, the following is a sample view.

Figure 2‒37: Display example when Node state map is selected as the panel type

New button

Click the New button to add the target node. The target node can be specified more than once.

button

Removes the selected target node from the map.

Map settings

Width of map (px): Specify the maximum width of the background image size. The default is 800. The unit is px (pixels). If the specified maximum width is smaller than the panel size, it is displayed reduced. The aspect ratio is not changed. If the vertical size is larger than the panel size, a scroll bar is displayed.

Initial size of node (px): Specify the size to display the node specified in the Node state. The default is 50. Units are in px (pixels).

Background image setting button: Click to specify the background image of Node state map.

Blink setting

The default for blinking is "Yes".

Warning button: When enabled, the entire node status panel flashes when the target node enters the Warning state.

Error button: When enabled, the entire node status panel flashes when the target node enters the Error state.

Emergency button: When enabled, the entire node status panel flashes when the target node enters the Emergency/Alert/Critical state.

Figure 2‒38: Create new window

Add button

Click the Add button to set the target node.

Background image setting button

When the background image is set, the node state color is displayed in the transparent part of the background image.

Mask image setting button

The element of the background image is multiplied by the mask image, and the transparent part of the mask image is displayed on the window.

OK button

Click to return to the Add panel window. The added node is placed in the upper left corner.

Figure 2‒39: Example of display when background image is set

Resize button

Select to change the display size of the node.

button

Move the selected node icon on the map to the back. Use when nodes overlap on the map.

button

Brings the selected node icon to the front on the map. Use when nodes overlap on the map.

(8) Text

Select the Text for the panel type to display the text data. Text can be written in a markdown format.

The following shows an example of the display when the Text is selected for the panel type.

Figure 2‒40: Display example when Text is selected as the panel type

Text

The text data described is displayed. The text can be filled in in the markdown notation.

Text color

Select the color of the text from the pull-down menu. The colors are "White" and "Black", and the default is "White".

Background color

Select the color of the entire text panel from the pull-down menu. The colors available are "Light Red", "Light Blue", "Light Green", "Light Yellow", "White", and "Black". The default is "Black".

Background image setting

Click the Background image setting button to set the background image of the text panel. PNG is the only extension of image data that can be specified as a background image.

Remove background image

When you click the Remove background image button, the background image of the text panel is deleted.

2.4.4 Notes

When displaying multiple instances of bar graphs in the Trend panel, some bar graphs may not be displayed in the graph area. If you want to check the bar graph that is not displayed, do one of the following.

Click the instance displayed in the legend to hide the object other than the target to confirmed.

Change the display range of the dashboard so that the time to be checked fits sufficiently within the graph area.

Change to a stacked graph in the Edit panel window.

There is no upper limit to the number of instances displayed in the Trend panel. If there are many instances and it is difficult to see the graph, please consider defining a metric for each instance by following the steps below.

1. Change the jp1_pc_trendname of the Prometheus configuration file (jpc_prometheus_server.yml) or the discovery configuration file of the Exporter of each JP1/IM - Agent.

For details of each file, see Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

- Example: jpc_file_sd_config_oracledb.yml (When spliting the oracledb_exporter metrics of hostA)

- targets:
  - ORAHOST1:ACCTDB:30001
  labels:
    jp1_pc_exporter: JPC OracleDB exporter
    jp1_pc_category: database
    jp1_pc_trendname: oracledb_exporter_hostA
    jp1_pc_remote_monitor_instance: hostA:OracleDB metric collector(OracleDB exporter)

2. Copy the metric definition file of the Exporter whose metric is to be splited, rename it to the metrics_jp1_pc_trendname-label-value.conf, and place it in the same path, and then add per-instance metrics to the metrics_jp1_pc_trendname-label-value.conf.

For details of metric definition files, see Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

- Example: metrics_oracledb_exporter_hostA.conf (When creating a metric to display tablespace utilization for instance RBS_TS0000Q only)

....
  {
    "name":"tablespace_used_percent_ RBS_TS0000Q ",
    "default":true,
    "promql":"oracledb_tablespace_used_percent {tablespace="RBS_TS0000Q",type="PERMANENT"} and $jp1im_TrendData_labels",
    "resource_en":{
      "category":"database_oracle",
      "label":"Tablespace Usage_ RBS_TS0000Q ",
      "description":"Shows the usage of RBS_TS0000Q tablespace. If automatic extension is ON, it is calculated based on the size considering automatic extension.",
      "unit":"%"
    },
    "resource_ja":{
      "category":"database_oracle",
      "label":"##Japanese phrases##",
      "description":"##Japanese phrases##",
      "unit":"%"
    }
  },,
....

3. Add the added metric definition file to the user-created definition file list definition file, and add the target of the definition file manipulation function.

For details about the user-created definition file list definition file, see User-created definition file list definition file (imdd_user_deffile_list.json) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

- Example: imdd_user_deffile_list.json (When adding a description of the metrics_oracledb_exporter_hostA.conf)

{
    "filelist":[
        {
        "filename": "metrics_oracledb_exporter_hostA.conf",
        "filepath": "C:\Program Files (x86)\\Hitachi\\JP1IMM \\conf\\imdd\\plugin\\jp1pccs",
        "filecategoryID": "user_def",
        "filecategoryName": "user_def",
        "updateaction": ""
        }
    ]
}

4. Restart the Prometheus server.

For details, see 10. Starting and Stopping JP1/IM - Agent in the JP1/Integrated Management 3 - Manager Administration Guide.

5. Create and reflect the tree information of the IM management node.

For Windows

For details about the procedure, see 1.19.3(1)(c) Creation and import of IM management node tree data (for Windows) (required) in the JP1/Integrated Management 3 - Manager Configuration Guide.

For Linux

For details about the procedure, see 2.18.5(2)(c) Creating and importing IM management node tree data (required) in the JP1/Integrated Management 3 - Manager Configuration Guide.

When the value of the metric type Counter is obtained using the PromQL function rate, irate, increase, delta and displayed with the panel type Trend, the value of the time when the value of the counter is reset (the value of the metric to be calculated is 0) is displayed as 0 for rate, irate, and increase, and the value of the minus in the case of delta is displayed. For example:

time

counter

rate

(counter[2m])

irate

(counter[2m])

increase

(counter[2m])

delta

(counter[2m])

00:01

0

0

0

0

0

00:02

60

1

1

60

60

00:03

180

2

2

120

120

00:04

0

0

0

0

-180

00:05

60

1

1

60

60

When the value of the time series data is NaN, +Inf, or -Inf, the display for each panel type is as follows. Note that when the calculation of the PromQL statement specified in promql of the metric definition file is divided by zero, the value of the time series data becomes NaN, +Inf, or -Inf.

For Trend:

Points with time values of NaN, +Inf, or -Inf are not displayed, and line graphs do not display lines or are cut off.

For Ranking:

Instances with values NaN,+Inf, or -Inf are not displayed.

For Number or Gauge:

"No Data", "Infinity", and "-Infinity" are displayed, respectively.

If you are viewing a dashboard screen with different display ranges in multiple tabs or multiple windows of the browser, clicking the Refresh button in the Dashboard Display area changes the display range to the display range of the dashboard screen that you set the display range last. In this case, set the display range again in the dashboard where you clicked the update button.

2.5 Operating status area

You can switch the display format of the Operating status area between the sunburst and tree chart formats, or search results. The information in the Operating status area is automatically updated when system status changes. This section describes the Operating status area.

2.5.1 Sunburst chart format

Figure 2‒41: Operating status area in the sunburst chart format

The following describes the items displayed in the Operating status area in the sunburst chart format.

Switch view buttons

: Indicates that the Operating status area is displayed in the sunburst chart format.

: Switches the display format of the Operating status area from the sunburst chart format to the tree chart format.

: Switch the display format of Operation Status from Sunburst to search result.

Sunburst chart

Displays the components of the monitored system (IM management nodes) in a hierarchical structure. Colors indicate the status of the components. These colors automatically change as the system status changes.

At the initial state, the first to fifth levels of the hierarchy in the sunburst chart are displayed. When a component is clicked, it is drilled down to show the second to sixth levels. The information in the Details area changes depending on the clicked component.

With the sunburst chart, the system administrator can drill down the component where a failure occurred to identify the cause of the failure and analyze the operations affected by the failure.

If a component has equal to or fewer than four levels of the hierarchy, the component cannot be drilled down further. To move one level up of the hierarchy, click the center of the sunburst chart.

Configuration elements are displayed up to the 3rd level, or up to the 2nd level if there are more than 3,000 elements. If there are not more than 3,000 elements, a maximum of elements up to the 5th level is displayed, within a scope not exceeding 3,000 elements.

Colors used in the sunburst chart

The following colors are used for the components of the sunburst chart:

Red: Emergency, Alert, or Critical

Orange: Error

Yellow: Warning

Green: Normal or Resolved

Failure location

In this area, locations of the failures, which are indicated as Emergency/Alert/Critical, Error, and Warning in the sunburst chart, are displayed in a tree chart format. When the entire system is in a healthy state (only green colors), nothing is displayed.

When you click a component in the sunburst chart, the corresponding row in this area appears in blue to indicate that it is selected.

If no failure occurs, the message No failure has been detected. is displayed.

The table below lists failure levels and corresponding icons. Note that the tree displays different icons depending on whether the IM management node has suggestion definition information.

Table 2‒1: Failure level and corresponding icons

Failure level

icons

When no suggestion definition information exists

When suggestion definition information exists

Emergency/Alert/Critical

Error

Warming

2.5.2 Tree chart format

Figure 2‒42: Operating status area in the tree chart format

The following describes the items displayed in the Operating status area in the tree chart format.

Switch view buttons

: Indicates that the Operating status area is displayed in the tree chart format.

: Switches the display format of the Operating status area from the tree chart format to the sunburst chart format.

: Switch the display format of Operation Status from the tree to the search result.

Tree chart

The tree chart allows users to monitor the system status visually with a centralized tree view. It displays the names of the components for each hierarchy level in the sunburst chart. The colors used in the tree chart are the same as those in the sunburst chart. The component selected in the sunburst chart appears in blue in the tree chart to indicate that it is selected.

The information in the Details area changes depending on the component clicked in the tree chart.

With the tree chart, the system administrator can drill down the row of the component where a failure occurred to identify the cause of the failure and analyze the operations affected by the failure.

If a failure occurs, the tree displays an icon according to the failure level. For details, see Table 2-1 Failure level and corresponding icons.

Regardless of whether a failure occurs, IM management nodes that have suggestion definition information are displayed with (suggestion icon) at the left side in the tree, which indicates that suggestion definition information exists.

(Bulk Collapse/Expand icon) is displayed to the right of (suggestion icon) display position for IM management node other than the following end:

Selected IM management node

IM management node with mouse cursor on

Clicking the left mouse button on (Batch Collapse/Expand icon) displays the following menu.

Collapse all Menu

Click to collapse all of the child nodes of the node and display only the child nodes.

If you clicked Collapse all menu for a closed node, all child nodes are also collapsed.

Expand all Menu

Click to expand all nodes under the corresponding node and display all nodes under them.

2.5.3 Displaying search result format

Figure 2‒43: Example of displaying search result format

The following items are displayed when Operating status is in the search result format.

Switch view buttons

: Operating status is in search format.

: Switch the display format of Operating status from the search result to Sunburst.

: Switches the display format of Operating status from the search result to the tree.

Node search (targets the entire system)

Enter the keyword to search for IM management node you want to view, up to 255 characters. Nodes that can be referenced by the logged-in JP1 user (node names of all nodes displayed in tree chart format) are searched.

If you enter even one character in the text box, the search results are displayed in the search result list immediately according to the input contents.

Clicking clears the text entered in the text box.

The text box entries are retained until you log out or disconnect the session. When logging in, it is displayed in the state of not being entered.

Number of search results

Displays the number of search results.

Search result list

Displays the node-name that partially matches the search keyword entered in Node search text box. They are not case sensitive. One-byte and two-byte characters are distinguished. The maximum number of node names that can be displayed in the search result list is 1,000. If more than 1,000 node names are hit in the search, only up to 1,000 are displayed in search result list. In this case, the Search result list displays the number of hits. To the left of it, a message indicating that the maximum number has been exceeded is displayed in red letters. Also, the Node count displays the number of nodes with the same node name being displayed.

If the same node name exists more than once, all lines are displayed with multiple nodes open (the [-] button is displayed to the left of the first node).

[-] Clicking this button closes multiple nodes, displays only the first row of nodes, and switches to the [+] button. Clicking the [+] button opens multiple nodes, displays all lines, and switches to the [-] button.

Search result information is retained until you log out or disconnect the session. When logging in, it is displayed in an empty state.

Node name (Node count) #

The node name and number of nodes that partially matched the search keyword are displayed in ascending order of the character code (Unicode) of the node name. A string portion that matches the search keyword is highlighted in yellow.

Failure location is displayed in the same color as tree chart format.

Tree path #

Displays Tree path of the node that is partially matched with the search keyword. If two or more nodes have the same node name, the corresponding line is displayed in ascending order of Tree path character encoding (Unicode).

Paths lower than the top-level node "All Systems" are omitted from the top-level node. Also, if you search for "All Systems", only nodes that contain "All Systems" are displayed.

#

The selected node is selected in Integrated Operation Viewer window by clicking Node name (Node count) or Tree path.

2.6 Details area

The Details area consists of two areas: the Tab area and the Events area. The Tabs area is further divided into two areas. You can change the sizes of the areas by clicking and scrolling up or down the bar that divides the areas or dragging the bar. This section describes the Details area.

2.6.1 Tabs area

The information related to the component selected in the Operating status area is displayed in a tab of the Details area. The following table of tabs that appear in the tabs area:

Table 2‒2: tabs that appear in the tabs area

Tab display order (from left)

Tabs name

Distriction

1

Dashboard tab

This tab displays various information such as graphs of various IT resources together. Various information and graphs can be displayed in units called "panels" on one tab.

For details of the window, see 2.4.1 Configuring the Dashboard tab.

2

Performance tab

This tab appears if this product links with JP1/PFM. It shows the JP1/PFM - Web Console window. For details about the window, see the JP1/Performance Management Reference of version 12-10 or later.

3

Custom UI tab

This tab shows a user-defined window that corresponds to the IM management node, if any. When there are multiple user-defined windows, as many tabs as the number of windows are displayed.

If no window that corresponds to the IM management node is defined, this tab is not displayed.

4

Suggestion tab

This tab appears when an IM management node with the suggestion icon is selected.

This tab can suggest actions according to the status of the system.

5

Job flow tab

If the selected IM management node is a root jobnet, this tab shows a line to indicate the relation with the root jobnet. If the IM management node is not for a job, this tab is not displayed.

6

Related node tab

This tab shows lines to indicate the relations between nodes in the selected IM management node.

7

Trends tab

This tab shows trend information, such as job accumulations and performance data, of the selected IM management node or its related node.

The information displayed on a selected tab persists even if you move to another tab. If you select a different node in the tree, the information displayed on each tab is initialized.

(1) Performance tab

When an IM management node of JP1/PFM is selected, a JP1/PFM - Web Console window is displayed on the Performance tab.

When the selected IM management node is JP1/PFM - Manager, the System Operational Status Summary window appears, which allows you to view the operating status of systems. When the selected IM management node is JP1/PFM - Agent, the Alarm Status window appears, which allows you to view the alarm status. The Performance tab allows you to make various adjustments during system operations. For example, by clicking View report in one of the windows described above, you can open the View Report window. The Alarm Table Bind Settings window, on the other hand, allows you to edit monitoring thresholds and data collection conditions.

The following figure shows an example of the Performance tab.

Figure 2‒44: Example of the Performance tab

For details about the window of the JP1/PFM - Web Console, see the JP1/Performance Management Reference of version 12-10 or later.

(2) Custom UI tab

The Custom UI tab opens a window predefined by the user when a specific IM management node is selected. A different window is displayed depending on the definition.

The following figure shows an example of the Custom UI tab. In this example, it is defined to open a specific window when you select All Systems.

Figure 2‒45: Example of the Custom UI tab

For details about the settings to display the Custom UI tab, see Chapter 6. Customization of Integrated Operation Viewer Window in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(3) Suggestion tab

The Suggestion tab appears when you click an IM management node with the suggestion icon. The tab consists of two areas: the suggestion list area and the Suggestion details area. The suggestion list area displays a list of suggestions that are associated with an IM management node you selected in the Operating status area. The Suggestion details area displays the details of a suggestion you selected in the suggestion list area.

The following figure shows the layout of the Suggestion tab.

Figure 2‒46: Layout of the Suggestion tab

(a) Suggestion list area

This subsection describes the suggestion list area.

Figure 2‒47: Example of the suggestion list area

Message

This field displays the message: To check whether there is a response action that can be executed at this moment, click the [Suggestion] button.

Suggestion button

This button starts judgment on the criteria of displayed suggestion bars to suggest response actions. When this button is clicked, the system judges whether criteria associated with the suggestions match the current system status to activate/deactivate the suggestion bars. Then, the suggestion list area is refreshed, resulting in activated suggestion bars being moved to the top of the list.

Suggestions: number-of-suggestions / number-of-suggestion-definitions

The number-of-suggestions placeholder represents the number of activated suggestion bars. The number-of-suggestion-definitions placeholder represents the number of suggestion bars.

Suggestion bar

A bar displays a suggestion that is defined for the selected IM management node. Suggestion bars can be activated or deactivated depending on whether the Suggestion button is clicked and how the criteria are judged.

Deactivated (not judged)

Indicates that the Suggestion button has not yet been clicked.

Activated (judged)

Indicates that the Suggestion button was clicked and the criteria of the suggestion were judged to match the current status.

Deactivated (judged)

Indicates that the Suggestion button was clicked and the criteria of the suggestion were judged not to match the current status.

If the judgment of suggestion criteria failed, the suggestion bar displays the error icon at the left of the bar.

When you select a suggestion bar, the bar is enclosed in a blue frame indicating that the suggestion is currently selected.

Each suggestion bar displays the following items:

Suggestion icon

The icon appears when the suggestion bar is activated. When the suggestion bar is deactivated, the suggestion icon is also deactivated.

Suggestion name

Displays the suggestion name. A long suggestion name can be truncated and followed by an ellipsis (...).

Start time

Displays the date and time when the previous execution of the suggestion started. The following format is used:

YYYY-MM-DD HH:mm:ss

The Start time field is blank if the response action has not yet been executed.

End time

Displays the date and time when the previous execution of the suggestion finished. The following format is used:

YYYY-MM-DD HH:mm:ss

The End time field is blank if the response action has not yet been executed, the action is running, or the call failed.

Execution status

Displays the result of the response action executed last time. The text color varies as follows:

Finished (blue)

Call error (red)

Unexecuted (gray)

Running (green)

Execute button

This button appears after the Suggestion button is clicked to judge the criteria of the suggestion. The button is activated when the suggestion bar is activated, or the response action is not running.

Clicking the Execute button opens a dialog box asking you to confirm the execution of the response action. When you click the OK button on the dialog box, the caption of this button changes from Execute to Running, and the execution of the selected suggestion starts.

(b) Suggestion details area

The Suggestion details area displays the details of a suggestion bar you selected in the suggestion list area. It just displays the message If you select a suggestion, details about the suggestion are displayed. until a suggestion bar is selected.

Note that the Suggestion details area displays different information depending on the criteria of the suggestion bar you selected in the suggestion list area.

Figure 2‒48: Example of the Suggestion details area

Message

The message If you select a suggestion, details about the suggestion are displayed. is shown.

[Suggestion ID]

Displays the ID of the suggestion.

[Suggestion name]

Displays the suggestion name of the suggestion bar that you selected in the suggestion list area.

[Case status]

Displays whether the defined criteria are established, after the Suggestion button is clicked and the criteria of the suggestion are judged. Additionally, a message appears in red to provide users with information, if available. A long message can be truncated and followed by an ellipsis (...). Click to view the complete message. Click

to go back to the initial view.

The possible states are as follows:

Established

Indicates that the criteria were judged and the suggestion bar was activated.

Not established

Indicates that the criteria were judged and the suggestion bar was deactivated. The icon appears when an error occurred with the suggestion.

Not judged

Indicates that the Suggestion button has not yet been clicked.

Show the case details button

Opens the Case details window to display the details of the criteria defined for the selected suggestion bar. This button is activated when the Suggestion button in the suggestion list area is clicked.

[Response action]

Displays the description of the response action that is defined for the selected suggestion bar. The response action does not appear if the Suggestion button in the suggestion list area is not clicked.

When you use your mouse to hover over each item in [Response action], is displayed. Clicking it causes what you selected to be copied.

[Execution status] / [Results of the previous execution]

Displays the execution status while the selected suggestion bar is running, or otherwise the result of the previous execution.

The execution status or the result of the previous execution of the response action is displayed in one of the following text colors:

Finished (blue)

Call error (red)

Unexecuted (white)

Running (green)

Start time

Displays the date and time when the previous execution of the response action started. The following format is used:

YYYY-MM-DD HH:mm:ss

The start time does not appear if the response action has not yet been executed.

End time

Displays the date and time when the previous execution of the response action finished. The following format is used:

YYYY-MM-DD HH:mm:ss

The end time does not appear if the response action has not yet been executed, or the action is running.

Execution user

Displays the user name of the user who last executed the response action. The user name does not appear if the response action has not yet been executed.

(c) Case details window

Click the Show the case details button to open the Case details window. The Case details window displays the status of the activation criteria for the suggestion bar you selected in the suggestion list area.

Figure 2‒49: Example of the Case details window

Suggestion name

Displays the suggestion name.

Case status

Displays the status of the suggestion activation criteria.

Established

It is displayed when the suggestion activation criteria are met.

Note that the icon appears if the judgment of a criterion failed.

Not established

It is displayed when the suggestion activation criteria are not met.

Message

If there is information that the user is notified of, a message is displayed in red letters above Case set n. If the message is too long to show the whole of it, the end of it is replaced with an ellipsis (...). Clicking allows you to view the whole text of the message. Clicking causes the message to shrink.

Case set n

The placeholder n is a sequence number of a set of suggestion activation criteria, starting from 1.

A set of suggestion activation criteria is defined as an array where criteria are combined with the AND condition and evaluated to judge whether to activate the suggestion. For details, see Suggestion definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Judgment result

Displays the result of judgment on the set of suggestion activation criteria. The value can be either of the following:

Established

Not established

Note that the icon appears if the judgment of a criterion failed.

Judgment

Displays the judgment result of each suggestion activation criterion. The possible values are as follows:

Match

Does not match

Error

Not judged

Case

Describes a criterion. A long description can be truncated and followed by an ellipsis (...). Click to view the complete description. Click to go back to the initial view.

Acquisition time

Displays the date and time when the data of the criterion used for judgment was acquired, in the following format:

YYYY-MM-DD HH:mm:ss

A hyphen (-) appears when Judgment displays Not judged or Error. The text color is changed to gray for failed.

Close button

Closes the Case details window.

(4) Job flow tab

The Job flow tab consists of two areas: the job flow area and the properties for job flow area. The job flow area shows lines to indicate the relations with root jobnets if the system component selected in the Operating status area is a job. The properties for job flow area shows the properties of the center node and selected node in the job flow area.

The following figure shows the layout of the Job flow tab.

Figure 2‒50: Layout of the Job flow tab

(a) Job flow area

This subsection describes the Job flow area.

Figure 2‒51: Job flow area

Get impact info. button

Retrieves the information about whether failures in the preceding root jobnets impact following root jobnets from the Intelligent Integrated Management server and displays the work impact icons in the Job flow.

Access time

Indicates the time when the information about whether failures in the preceding root jobnets impact following root jobnets is retrieved from the Intelligent Integrated Management server.

To show the access time in the following format, click the Get impact info. button:

Access time: YYYY-MM-DD hh:mm:ss

If part of the information is updated, (*) is displayed at the end of the date and time.

Node

Each root jobnet is represented as a box. The colors of a node are the same as those of the corresponding component in the sunburst chart. When you click a node, the clicked node shows up in the middle of the window as the center node, and the window is refreshed to display information regarding the clicked node. Note, however, that gray nodes are not clickable.

On the other hand, you can click any node names regardless of their color. If you click a node name, only information displayed in the properties for job flow area is refreshed.

The nodes of JP1 events that are defined as severe events are colored according to the event level and status. The nodes of JP1 events that are not defined as severe events appear in white.

The table below describes how the nodes of JP1 events that are defined as severe events are colored according to the event level and status.

Table 2‒3: Colors of nodes according to the event level and status of JP1 events

Event level

Event status

UNKNOWN node#

Unprocessed

Held

Processing

Normal or Resolved/Processed

Emergency

Red

Red

Red

Green

Gray

Alert

Critical

Error

Orange

Orange

Orange

Warning

Yellow

Yellow

Yellow

Notice

Information

Debug

#

This means a root jobnet for which the user has no permissions or a root jobnet (node) that lacks the tree SID.

When you hover over the icon, the tree path of the node is displayed in a tooltip.

Center node

The component (root jobnet) selected in the Operating status area, the Job flow tab, or the Related node tab is put in the middle of the window as the center node, and the relationships with other nodes are displayed. If the center node has no relationship with other nodes, only the center node is displayed. The center node is displayed enclosed in a blue frame.

The preceding root jobnets and succeeding root jobnets are displayed on the left and right of the center node on the window, respectively. If there is no preceding root jobnet or succeeding root jobnet, a gray node (UNKNOWN node) is displayed.

The Events area displays the information on the center node.

Root jobnet name

The name of the node is displayed as the root jobnet name. When you hover over a node, the tree path appears. If the full path is too long, the end of the path is replaced with an ellipsis (...).

When you click it, the root jobnet name turns blue, showing the information in the properties for Job flow area. Note that the component selected in the Operating status area remains unchanged.

Relationships between root jobnets

The relationships between root jobnets are represented with curved lines.

If a root jobnet has a looped connection to itself, the node is displayed at the right end and left end on the window as separate nodes.

Work impact icon

Shows if failures in the preceding root jobnets impact following root jobnets when failures occur, with one of the icons below.

There is no impact if no icon is displayed.

: Impact: Yes

: Error

: Unknown#

#: If this icon is configured in the Intelligent Integrated Management Base definition file not to be shown, a blank field is displayed.

When you hover over the icon, the meaning of the icon is displayed in a tooltip.

When you click the work impact icon, the information of the linked units for the relation line on which the icon is shown is displayed in the Linked unit dialog box. For details about the Linked unit dialog box, see the description in (b) Properties for job flow area.

Note that the Job flow tab can display relationships involving the same root jobnet repeatedly. For example, a definition to run root jobnet A, root jobnet B, and then root jobnet A results in the same root jobnet appearing repeatedly. Repeated nodes have the work impact icons individually, but all icons displayed on the nodes with the same root jobnet name open the Linked unit dialog box containing the same information. This means that you do not need to click every work impact icon displayed on repeated nodes to open the Linked unit dialog box.

(b) Properties for job flow area

This subsection describes the properties for job flow area. The displayed properties vary depending on the conditions of the selected IM management node.

Figure 2‒52: Properties for job flow area

Tree selection node info.

The area shows the information of the node selected in the tree. When you hover over a value, the icon appears. Clicking it allows you to copy the value to the clipboard.

Clicking causes Tree selection node info. to be closed. Clicking causes Tree selection node info. to be opened.

The property names and values are shown below. If there is no information to be shown, no value is displayed in the field.

Tree SID: Displays the SID of the tree.

Tree path: Displays the tree path. It is the same information as the tree path that is displayed when you hover over the node.

Node name: Displays the node name of the tree.

IM node type: Displays the type name of the tree SID.

Resource group: Displays the resource group name.

SID: Displays the SID of the configuration information.

Object type: Displays the object type.

Linked prod.: Displays the JP1/AJS3 - Web Console link of the root jobnet to which the node selected in the tree belongs. When you click the link, the window of JP1/AJS3 - Web Console appears. If there is no information to be shown, the item itself is not displayed.

Display linked units button

This button is activated when a linked unit is connected with the selected node through a relation line.

When you click it, the Linked unit dialog box appears, showing the linked unit for which the IM management node selected in the tree serves as either a preceding root jobnet or following root jobnet.

If the selected IM management node does not have a linked unit, this button is inactive.

Selected node info.

Displays the information of the selected node. It shows the same information as that of Tree selection node info., other than the Display linked units button.

(c) Linked unit dialog box

Units that realize the relationships between root jobnets, such as JP1 event sending jobs and JP1 event reception monitoring jobs, are called linked units.

The Linked unit dialog box displays the list of linked unit information for each relation line. The information varies depending on the window from which the Linked unit dialog box is opened.

If the dialog box is opened through the Display linked units button in the properties for job flow area:

All linked units connected to the node selected in the tree via relation lines are displayed.

If the dialog box is opened through an icon in the job flow area:

The linked units connected to the relation line that has the icon selected in the job flow area are displayed.

Figure 2‒53: Linked unit dialog box

Each item can be sorted by item name. You can also change the order of the columns by dragging the header.

NO DATA is displayed if any of the following conditions is met:

If a preceding root jobnet or following root jobnet shows the following linked unit:

Linked unit in a link of a subordinate root jobnet of JP1/AJS - Manager 12-00

If a linked unit in the following link is displayed:

Link for which no linked unit information defined in the IM management node link definition file is specified

If, after JP1/IM is upgraded from 12-00 to 12-10 or later, linked units are displayed without the jddcreatetree command and jddupdatetree command

The following describes the items displayed in the Linked unit dialog box.

Access time

Displays the date and time when the Linked unit dialog box is opened, in the following format:

Access time: YYYY-MM-DD hh:mm:ss

If part of the information is updated, (*) is displayed at the end of the date and time.

Refresh button

Refreshes the information in the Linked unit dialog box and updates the information in the job flow area.

Full screen button

Displays the Linked unit dialog box in full screen. Clicking the button restores it to the original size.

Close button

Closes the Linked unit dialog box.

Preceding unit

Displays a link showing the name of a linked unit when the selected IM management node is a preceding unit.

For a waiting relationship, this displays a link showing the name of the unit whose end is being waited for. For a relationship with a jobnet connector#, this displays a link showing the job connector or the name of the connection-destination root jobnet.

When you click a link, the Monitor window of JP1/AJS3 - Web Console appears with the preceding unit selected. The generation of which impact information is retrieved in the Linked unit dialog box is displayed in the Monitor window.

Following unit

Displays a link showing the name of a linked unit when the selected IM management node is a following unit.

For a waiting relationship, this displays a link showing the name of the unit with wait conditions. For a relationship with a jobnet connector#, this displays a link showing the job connector or the name of the connection-destination root jobnet.

When you click a link, the Monitor window of JP1/AJS3 - Web Console appears with the following unit selected. The generation of which scheduled link time of the following unit is retrieved is displayed in the Monitor window.

#

For jobnet connectors, the relationship between units in Preceding unit and Following unit varies depending on how execution order is controlled. When execution order is controlled synchronously, the unit names are displayed as follows:

Preceding unit displays a jobnet connector, and Following unit displays a connection-destination root jobnet.

Preceding unit displays a connection-destination root jobnet, and Following unit displays a jobnet connector.

When execution order is controlled asynchronously, the unit names are displayed as follows:

Preceding unit displays a connection-destination root jobnet, and Following unit displays a jobnet connector.

For details about how to control execution order, see the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Note

Suppose that you open the Linked unit dialog box by using the Display linked units button in the properties for job flow area. In this case, the name of the unit corresponding to the node (root jobnet) selected in the tree is displayed in bold. On the other hand, if you open the Linked unit dialog box by using a work impact icon displayed in the job flow area, unit names are not displayed in bold.

Impact (yes/no)

An icon is displayed if there is an impact on the following root jobnet from a failure in the preceding root jobnet.

It is displayed based on the information retrieved of the result generation whose root jobnet's end date and time is closest to the current date and time, or about the currently being executed generation. There is no impact if no icon is displayed.

: Impact :Yes

: Error

: Unknown

Scheduled date and time for linkege

Displays the scheduled linkage date and time. The date and time displayed is the date and time of execution simulation by JP1/AJS.

When the preceding unit is a root jobnet unit whose end is being waited for, and the following unit is a unit with wait conditions

This displays the scheduled start date and time of an executing generation or scheduled generation of the following unit that is waiting for the execution ID of the preceding unit.

A hyphen (-) appears in Scheduled date and time for linkage when the unit with wait conditions has no execution schedule, and the JP1/AJS - Manager environment setting parameter PREWAITNOSCHUNITS is set to yes.

When the preceding unit and following unit are a jobnet connector or connection-destination root jobnet

This displays the scheduled end date and time or the scheduled start date and time of an executing generation or scheduled generation of the following unit that is associated with the execution ID of the preceding unit. The scheduled end date and time appears when the following unit is a jobnet connector, or the scheduled start date and time appears when the following unit is a connection-destination root jobnet.

When the preceding unit and following unit are units other than those described above

This displays the information of an executing generation or scheduled generation whose scheduled start date and time or scheduled end date and time is the closest to the current date and time.

Message

Displays a message when an attempt to acquire linked unit information fails.

(5) Related node tab

The Related node tab consists of two areas: the related node area and the properties for related node area. The related node area displays the relationship with each linked product and relationships in the system configuration displayed in the Operating status area as connected lines. The properties for related node area displays the properties of the base node in the related node area, and the properties of the selected node or selected relation line.

The following figure shows the layout of the Related node tab.

Figure 2‒54: Layout of the Related node tab

(a) Related node area

This subsection describes the related node area.

Figure 2‒55: Related node area

Note

You can change the position where a related node icon is displayed in the window by clicking and dragging the node in the related node area. To enlarge the node, double-click it. You can also use the mouse wheel to change the scale of enlargement.

Related node icon

Displays the types of related nodes, starting from the IM management node selected in the Operating status area or on the Job flow tab. For details about various icons for related nodes, see (7) Icons for related nodes.

At the lower left of a related node icon, an icon appears to indicate the status of the related node. The status icons are displayed in the same colors as those in the sunburst chart. Click a related node icon to display the information of the selected node in Selected node info. of Properties. You can click any related node icon and related node name regardless of the color of the status icon.

For JP1 events that are defined as severe events, the status icons are colored according to the event level and status. For JP1 events that are not defined as severe events, the status icons appear in white.

The table below describes how status icons for JP1 events that are defined as severe events are colored according to the event level and status of the JP1 events.

Table 2‒4: Colors of status icons according to the event level and status of JP1 events

Event level

Event status

UNKNOWN node#

Unprocessed

Held

Processing

Normal or Resolved/Processed

Emergency

Red

Red

Red

Green

Gray

Alert

Critical

Error

Orange

Orange

Orange

Warning

Yellow

Yellow

Yellow

Notice

Information

Debug

#

This means a related node for which the user has no permissions or a related node that lacks the tree SID.

Related node name

Displays the names of related nodes. When you hover over a node, the tree path is displayed. If the full path is too long, the end of the path is replaced with an ellipsis (...).

This displays UNKNOWN if the relationship between the nodes indicates that no following node exists for the preceding node or no preceding node exists for the following node.

Relationships between nodes (relation line)

Displays connections between nodes as lines (relation lines).

By default, the relationships between the selected node and nodes with link information and the upper layer (infrastructure nodes) in the sunburst chart or the tree chart are displayed. The lower layers are not displayed.

The following shows the colors and meanings of the relation lines:

Magenta: The relation type is Tree and the direction of the relation is from preceding node (left) to following node (right).

Yellow: The relation type is Tree and the direction of the relation is from following node (left) to preceding node (right).

Turquoise: The relation (link information) has a relation type other than Tree.

White: There is a mix of multiple relation types (relation type Tree and others, or a mix of multiple relations (link information) other than Tree).

Relation type of a relation line

When you hover over a relation line, the relation type of the relation line is displayed in a tooltip.

On a relation line with a mix of multiple relation types (blue), the tooltip shows the relation types separated by new lines.

If some relation types as part of a mix of relation types are hidden through Relation line filter, the ends of the applicable relation types are followed by (-).

If multiple relations (link information) other than Tree exist and they all are of the same relation type, they are displayed as one relation type.

Selecting a relation line

When you click a relation line, the line is thickened, showing the information of the selected relation line in Info. on selected relation line of Properties.

If you try to display the same combination of relation lines as the one that has been displayed before, the relation lines are not displayed, but all the buttons are switched to expanded state.

Expand related node button

When you click it, the related nodes and the upper and lower layers of the system configuration are expanded to the right. If all the relation lines have already been displayed, the icon is displayed.

Shrink related node button

When you click it, the related nodes displayed to the right are all shrunk.

Initialize zoom button

When you click it, the display positions and scale of enlargement in the Related node tab return to their initial states.

Relation line filter

Enables you to specify the type of relation lines displayed in the Related node tab through the selection of filter items. When you click a filter item, you can show or hide the corresponding relation line. All the relation lines are shown by default. The following lists available relation line filter items with their meanings:

rootJobnetExecutionOrder: Relations for execution order of root jobnets

rootJobnetAgent: Relations for root jobnets and AJS agents

managerAgent: Relations for JP1 product managers and agents

sameNode: Relations for nodes with the same name

tree: Relations for parent nodes and child nodes in IM management node trees

(b) Properties for related node area

The properties for related node area displays the properties of the base node in the related node area, and the properties of the selected node or selected relation line.

This subsection describes the properties for related node area. Displayed properties vary depending on the conditions of the selected IM management node.

Figure 2‒56: Properties for related node area

Tree selection node info. / Selected node info.

Displays the same property information as that in the properties for job flow area as well as the property information specified by user-created plug-ins. However, for the Linked prod. item, it displays the information obtained from the plug-ins. For details about user-created plug-ins, see Chapter 4. User-created Plug-ins in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

See Tree selection node info. and Selected node info. in 2.6.1 (4)(b) Properties for job flow area.

Info. on selected relation line

Displays the information of the selected relation line.

When you hover over a value, appears. Clicking it allows you to copy the value to the clipboard.

Clicking causes Info. on selected relation line to be closed. Clicking causes Info. on selected relation line to be opened.

The property names and values are shown below. If there is no information to be shown, no value is displayed in the field.

Relation selection line

Relation type: Displays the type of the relation line.

Preceding node: The tree path of the preceding node are displayed in the following format:

Preceding-node-name (preceding-node's-configuration-information-SID or tree-SID)

Following node: The tree path of the following node are displayed in the following format:

Following-node-name (following-node's-configuration-information-SID or tree-SID)

Left node / Right node

Tree SID: Displays the SID of the tree.

Tree path: Displays the tree path. It is the same information as the tree path that is displayed when you hover over the node.

Node name: Displays the node name.

IM node type: Displays the IM management node type.

Resource group: Displays the resource group name.

SID: Displays the SID of the configuration information.

Object type: Displays the object type.

Linked prod.: Displays the link of the linked product obtained from the plug-ins. When you click the link, the window of the linked product appears. If there is no information to be shown, the item itself is not displayed.

Note that Left node and Right node also show the property information specified by user-created plug-ins. For details about user-created plug-ins, see Chapter 4. User-created Plug-ins in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(6) Trends tab

The Trends tab consists of two areas: the trend graph view area and the trend graph settings area. The trend graph view area displays trend information of the node selected in the Operating status area in the charts. The trend graph settings area is used to set necessary information to show the charts in the trend graph view area.

The following figure shows the layout of the Trends tab.

Figure 2‒57: Layout of the Trends tab

For details about the types of metrics (time-series data) that can be retrieved in a linkage with JP1/AJS and JP1/PFM, see 2.7 Metrics that can be retrieved from linked products.

(a) Trend graph view area

This subsection describes the trend graph view area.

Figure 2‒58: Trend graph view area

Display period

Displays the period of the trend information on display in the following format:

YYYY-MM-DDΔhh:mm:ss (YYYY: year, MM: month, DD: day, Δ: space character, hh: hour, mm: minute, and ss: second)

Title

Displays the information below. If the title is too long, the end of it is replaced with an ellipsis (...).

If a metric is not selected: label-name-of-the-IM-management-node

If a metric is selected: label-name-of-the-IM-management-node - metric-name

If the chart on display is summarized, the title is displayed in the format of title. When you hover over , Summarized is displayed in the tooltip. If you want to see values before they are summarized, use Change display period so that the display period is shorter.

Chart info.

When you hover over it, the tree path of the chart on display is displayed in the tooltip.

Node transition

When you click it, the IM management node from which the chart on display retrieves the information is selected in the Operating status area, showing the list of events on the selected IM management node in the Events area.

The metrics, time period, and chart displayed in the trend graph settings area remain the same even after the transition. All the other tabs are initialized by the transition.

When you find an unusual node (for example, any unexpected value in the displayed chart), you can transition to that node and view a list of relevant events.

This icon is deactivated when the node to transition to happens to be the currently selected node.

Move up button

Moves the selected chart up by one spot.

Move down button

Moves the selected chart down by one spot.

Minimize button

Minimizes the selected chart. Clicking it again restores it to the original size.

Restore button

Restores the minimized chart to the original size.

Close button

Closes the selected chart.

Data of a point on the chart

Displays the time, legends on the chart, and values when you hover over a point on the chart.

Occurrence time

Displays the time when the event selected in Events occurred, together with the serial number. If multiple events with the same occurrence time are selected, the occurrence time of the event with the largest serial number is displayed.

Legend

Displays the legend of a graph. When you hover over a legend, the graph for the selected legend is highlighted in the chart, showing the legend in the tooltip.

If you want to show a specific graph in the chart, click the legends for graphs you want to hide. The graphs that correspond to the legends you clicked are hidden. When you click the legends again, the graphs are shown.

(b) Trend graph settings area

This subsection describes the trend graph settings area.

Figure 2‒59: Trend graph settings area

Apply changes and refresh the display button

Updates the trend information in the view area with the edits on the chart.

Change display period

Displays the period displayed in the trend information view area in the following format:

YYYY-MM-DDΔhh:mm:ss (YYYY: year, MM: month, DD: day,

Δ: space character, hh: hour, mm: minute, and ss: second)

Clicking closes Change display period. Clicking opens Change display period.

Start / End

If an event is not selected: The period to be displayed is from 59 minutes 59 seconds ago up to the current time.

If an event is selected: The period to be displayed is from 29 minutes 59 seconds before the event occurrence time to 30 minutes after.

If multiple events are selected: The issuance date and time of the event with the latest date and time of event issuance is displayed.

If an event that occurred between 30 minutes ago and now: The period between 29 minutes 59 seconds before the event occurrence time and now is displayed.

If you want to change the display period, click to open the calendar, where you can change the year, month, and time. You can specify a range between 1970/01/01:00:00 ~ 2099/12/31 23:59:59.

When you hover over the time, the time adjustment buttons appear. You can set the year by one year, the hour by one hour, the minute by five minutes, and the second by five seconds. You can enter the time manually.

If the start time specified in the calendar is later than the set end time, or if the specified end time is earlier than the set start time, the time specified as the end time is treated as the start time, and the time specified as the start time is treated as the end time.

Reset period button

Resets the time specified in Change display period.

Previous 1h button

Sets the Start time and the End time in Change display period to the time one hour before the specified time.

Chart

Displays the chart for the selected IM management node.

Clicking closes Chart. Clicking opens Chart.

IM node name

When you click next to the IM management node name, the node is deactivated, showing . Clicking undoes it.

If you want to remove a deactivated node, click the Apply changes and refresh the display button. You cannot recover a node once removed.

When you hover over a node name, the information below is displayed. If the text in the information is too long, the end of it is replaced with an ellipsis (...).

Tree path of the IM management node

Type of the metric

Metric name

Category name

Displays the name of the category for the selected node. If the node has no category name, No category is displayed.

Clicking closes the corresponding category. Clicking opens the corresponding category to show the metric names.

Metric names: Display the metric names under the node, with check boxes. Select the check boxes for the metrics for which you want to show graphs in the trend graph view area.

For details about the metrics that can be retrieved from linked products, see 2.7 Metrics that can be retrieved from linked products.

[+] Add node button

Opens the Add node dialog box.

(c) Add node dialog box

The Add node dialog box is used to add a node that is selected in the displayed related node area.

It has the same items as those displayed in the related node area, other than those described here. For details, see 2.6.1(5)(a) Related node area.

Figure 2‒60: Example of add node dialog box

The following describes the items displayed in the Add node dialog box.

Full screen button

Displays the Add node dialog box in full screen. Clicking the button restores it to the original size.

Close button

Closes the Add node dialog box.

Node icon

You can add nodes with white node names only.

When you hover over a node icon, the mouse cursor turns to , and text is displayed in the tooltip. The relation lines that connect to the node icon over which you hover become opaque.

When you hover over an inactive node name, the mouse cursor turns to .

When you select a node icon, the node icon is enclosed in a blue frame and the text color of the node name is changed to blue.

Once you add a node, you cannot add it again. You also cannot select and add multiple nodes at once. If you want to add multiple nodes, repeat the process to add each node.

Color of node name letters

The following shows the meanings of the node name letters:

White: Means a node that has trend information and is not added to the trend graph settings area.

Gray: Means a node that has no trend information.

Bold gray: Means a node that has already been added.

Connection between nodes (relation line)

Displays a connection between nodes as a line (relation line). The relation line cannot be selected.

Selected node: node name

Displays the name of the selected node. If no node is selected, a hyphen (-) is displayed. If the node name is too long, the end of it is replaced with an ellipsis (...).

Add button

Adds the selected node.

Close button

Closes the Add node dialog box.

When you select a metric for the added node and click the Apply changes and refresh the display button, the graph for the added node is displayed in the trend information view area.

Figure 2‒61: Adding a node

(7) Icons for related nodes

The table below lists various icons with their meanings that represent related nodes displayed in the related node area and the Add node dialog box.

Table 2‒5: Related node icons and their meanings (for IM management nodes)

No.

Icon file name

Icon

Meaning

1

ROOT

Represents a root node.

2

SYSTEM

Represents a system node.

3

SUBCATEGORY

Represents a subcategory node.

4

HOST

Represents a host node.

5

_OTHER_

Represents an IM management node of a type other than the types listed in No. 1 to No. 4.

Table 2‒6: Related node icons and their meanings (for category nodes)

No.

Icon file name

Icon

Meaning

1

CATEGORY_job

Represents Job.

2

CATEGORY_serviceResponse

Represents Service Response.

3

CATEGORY_enterprise

Represents Enterprise.

4

CATEGORY_transactionProcessing

Represents Transaction Processing.

5

CATEGORY_applicationServer

Represents Application Server.

6

CATEGORY_database

Represents Database.

7

CATEGORY_platform

Represents Platform.

8

CATEGORY_virtualMachine

Represents Virtual Machine.

9

CATEGORY_managementApplications

Represents Management Applications.

10

CATEGORY_otherApplications

Represents Other Applications.

11

CATEGORY__OTHER

Represent a category node of a type other than the types listed in No. 1 to No. 10.

Table 2‒7: Related node icons and their meanings (for object nodes - JOB objects)

No.

Icon file name

Icon

Meaning

1

OBJECT_JP1ROOTJOBNET

Represents a root jobnet.

2

OBJECT_JP1AJSMJOB

Represents JP1/AJS - Manager.

3

OBJEC_JP1SCHE

Represents a scheduler service.

4

OBJECT_JP1JOBG

Represents a job group.

5

OBJECT__OTHER_

Represent an object node of a type other than the types listed in No. 1 to No. 5.

Table 2‒8: Related node icons and their meanings (when acquisition of an IM management node fails)

No.

Icon file name

Icon

Meaning

1

_UNKNOWN__JP1ROOTJOBNETDUMMY

Represents a root jobnet (unknown link information).

2

_UNKNOWN___OTHER

Represents a type other than the type of No. 1.

2.6.2 Events area

The Events area displays the JP1 events occurring in the selected system components. The latest events are collected and displayed periodically. If JP1 events are consolidated by use of the suppression of repeated-event display provided by the Intelligent Integrated Management Base, consolidation events are displayed in the events list.

This section describes the Events area.

Figure 2‒62: Events area

Operation menu button

Shows the following operation menu items:

Repeated event list: This menu item is activated when one selected JP1 event is a consolidation start event. When you click it, the Repeated event list window is displayed in a separate window.

Monitor: This menu item is activated when one selected JP1 event is an event for which monitor startup is specified. When you click it, a window that corresponds to the selected JP1 event is displayed.

Run Response Action (Event information inheritance): Activated when the selected JP1 event is one. Clicking this button takes over the data of the selected JP1 event. The Run Response Action window is displayed.

Toolbar

Oldest button

Displays 100 old events starting from the oldest event in the Events area excluding dummy events.

Previous button

Displays 100 events listed on the previous page.

Next button

Displays 100 events listed on the next page.

Latest button

Displays 100 events older than the latest event (excluding dummy events) shown in the Events area as a starting point.

Filter by status button

Narrows down the status of events based on the color of the selected button. Multiple buttons can be selected for filtering.

For example, when you click the button that indicates the Error state, the list in the Events area is narrowed down to show only JP1 events in orange and the button changed to .

button

After filtering is performed, this button changes to . You can click it to clear the filter.

Event view

Displays the JP1 events occurring in the component selected in the Operating status area or a Each tab area.

The event view displays up to 100 events. New JP1 events appear under the older ones.

The event view displays the following items: Event status, Consolidation event, (Severe event), Event level, Serial number, Registered time, Event source host, User name, Event ID, Message, Object type, and Action.

You can change the width of a column by dragging its boundary. You can also change the column order by dragging the column.

Select All/Clear All check box

To select all JP1 events in the Events area, click the check box on the header of the area. To clear all selection, click the check box to deselect them.

To select an event, select the check box for the event.

Details button

Displays the Event detail window for the selected event.

Full screen button

Displays the Event detail window in a full screen view. Click the button to return the dialog box to its original size.

Close button

Closes the Event detail window.

Monitor button

This button is activated when the selected JP1 event is an event for which monitor startup is specified. When you click it, a window that corresponds to the selected JP1 event is displayed.

Run Response Action (Event information inheritance) button

Activates when the selected JP1 event is one. Clicking this button takes over the data of the selected JP1 event. The Run Response Action window is displayed.

Guide

Displays the event guide information for the shown JP1 event. If the event guide function is disabled or no event guide information exists for the JP1 event, the Guide area is not displayed.

The event guide information to be displayed in this area must be specified in the event guide information file. For details, see Event guide information file (jco_guide.txt) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Event status

Displays the status of an event (Processed, Unprocessed, Processing, or Held) with a status icon that corresponds to the event status. For a consolidation event, the event status of the consolidation start event is displayed.

The following table lists the event statuses and the corresponding status icons. If the event status of the consolidation start event differs from the event status of a repeated event consolidated with it, an exclamation mark (!) is displayed in the Event status column of the consolidation start event.

Users who have JP1_Console_Admin permission or JP1_Console_Operator permission can use this menu.

Table 2‒9: Event statuses and corresponding icons

Event status

Status icon

Processed

Processing

Held

Unprocessed

(No icon)

If you change the event status, select the check box for the event you change, and select an event status from the pull-down menu under Event status.

Note that when the check box for a consolidation start event is selected, only the event status for the consolidation start event is changed. The event status of repeated events is not changed.

Consolidation event

Displays if an event is the consolidation start event.

(Severe event)

If an event is the severe event, is displayed. If an event is the consolidation start event, is displayed when the consolidation start event is the severe event.

When repeated events consolidated as a severe event actually consist of not only severe events but also non-severe events, an exclamation mark (!) is displayed.

Event level

Indicates the following levels of the event: Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug. The Event level column displays text that indicates the level of the event and the corresponding icon. The text color and background color cannot be changed.

The following table lists the event levels and the corresponding icons, text colors, and background colors.

Table 2‒10: Event levels and corresponding icons, text colors, and background colors

Event level

Icon

Text color#

Background color

Emergency

Black

For severe events: Red

For non-severe events: White

Alert

Critical

Error

For severe events: Orange

For non-severe events: White

Warning

For severe events: Yellow

For non-severe events: White

Notice

Information

Debug

Serial number

Displays the serial number in the event database for the received JP1 event. The serial number is displayed in decimal format.

Registered time

Displays the registered time for the received JP1 event.

The registered time is displayed in the time zone on the machine that displays the integrated operation viewer, in YYYY-MM-DD hh:mm:ss format.

Event source host

Displays the name of the host where the event that triggered the JP1 event occurred. If any control characters are contained in the host name, they will be removed from the displayed name.

User name

Displays the user name for the JP1 event. If any control characters are contained in the user name, they will be removed from the displayed name.

Event ID

Displays the event ID for the JP1 event. The event ID is displayed in 8-digit hexadecimal format. A to F are displayed in uppercase letters.

Message

Displays the message text for the JP1 event.

Object type

Displays the object type for the JP1 event in a string. If any control characters are contained in the string, they will be removed from the displayed string.

Action

When the function for suppressing automated actions is used, the suppression status is displayed with an icon in the Integrated Operation Viewer window.

Auto responseAction

Displays the target and non-target action of the responseAction with the event.

Displays for the target. If it is non-target, nothing is displayed.

Table 2‒11: Action suppression status icons

Icon

Description

Action that has not been suppressed

Action that has been suppressed

Action that has been partially suppressed

If many events occur when execution of automated actions is suppressed by a condition for suppressing monitoring of repeated events, the icon is displayed. If a common exclusion-condition prevents an action from being executed, the icon is displayed.

When the action status differs between a consolidation start event and repeated events, an exclamation mark (!) is displayed in the Action column.

(1) Repeated event list window

The Repeated event list window is displayed in a window separated from the integrated operation viewer.

It has the same items as those displayed in the Events area, other than those described here.

Important

Multiple Repeated event list windows cannot be opened in the same session of the Web browser. You can use different sessions in the browser to open the Repeated event list window for each session.

Figure 2‒63: Repeated event list window

The following describes the items displayed in the Repeated event list window.

Consolidation event

Displays consolidation start events.

Operation menu button

Shows the following operation menu items:

Status change at once: Changes the event statuses of repeated events at once. Clicking it shows the following menu items:

- Unprocessed

- Processed

- Processing

- Held

When you select a menu item, the Status change at once for repeated events dialog box appears.

Clicking the OK button starts changing the event statuses of all repeated events. When the changes are finished, a message is displayed in the dialog box. To close the dialog box, click the OK button. To suspend the changes in the event statuses of repeated events, close the Web browser while changing them at once. In this case, the changes in the event statuses take effect before the Web browser is closed.

Monitor: This menu item is activated when the selected JP1 event is an event for which monitor startup is specified. When you click it, a window that corresponds to the selected JP1 event is displayed.

Refresh

Updates the information of consolidation events.

Repeated event condition: condition-name

Displays the condition name of the repeated event condition.

Repeated event list

Displays the list of consolidated repeated events.

Operation menu button

Shows the following operation menu item:

Monitor: This menu item is activated when the selected JP1 event is an event for which monitor startup is specified. When you click it, a window that corresponds to the selected JP1 event is displayed.

2.7 Metrics that can be retrieved from linked products

This section describes the types of metrics (time-series data) that can be retrieved in a linkage with JP1/AJS and JP1/PFM.

2.7.1 Metrics that can be retrieved from JP1/AJS

The following table lists the metrics that can be retrieved from JP1/AJS.

Table 2‒12: Metrics that can be retrieved from JP1/AJS

No.

Category name

Metric name

Metric display name

Item output to the performance report of the ajsreport command#

Units

1

Change in the processing amount in the entire scheduler services

root_exec_start_num

Number of started root jobnets

RJ_EXEC_START_NUM

jobnets

CONDRJ_EXEC_START_NUM

2

job_exec_start_num

Number of started jobs

JOB_EXEC_START_NUM

jobs

EVJOB_EXEC_START_NUM

3

running_and_scheduled_next_generations_num

Change in the number of running generations and generations to be executed next time

RUNNING_AND_SCHEDULED_NEXT_GENERATIONS_NUM

generations

4

alarm_info_num

Alarm notification item

CONTENTJOB_NUM

items

EVJOB_UNREPORTED_EVENT_NUM

5

nest_exec_start_num

Number of started nested jobnets

NEST_EXEC_START_NUM

jobnets

6

all_noexec_end_units_num

Number of units that finished without starting execution

ALL_NOEXEC_END_UNITS_NUM

units

7

Standard job - start

job_start_operation_result_num

Standard job start operation (operational outcomes)

JOB_EXECWAIT_NUM

jobs

JOB_TRANSITTED_QUEUING_NUM

JOB_EXEC_START_NUM

8

job_start_wait_num

Standard job start operation (wait)

JOB_SUBMIT_RETRY_BACKLOG_NUM

generations

JOB_QUEUING_BACKLOG_NUM

9

job_exceeded_max_con-exe

Standard job start operation (multiplicity)

JOB_EXCEEDED_MAX_CON-EXE

detected/not detected

10

job_maximum_transfer_file_size

Standard job start operation (transferred file)

JOB_MAXIMUM_TRANSFER_FILE_SIZE

bytes

11

job_error_agent_detected

Standard job start operation (error agent)

JOB_ERROR_AGENT_DETECTED

detected/not detected

12

Standard job - end

job_end_operation_result_num

Standard job end operation (operational outcomes)

JOB_END_NOTIFICATION_DETECTED_NUM

jobs

JOB_EXEC_END_N_NUM

JOB_EXEC_END_W_NUM

JOB_EXEC_END_E_NUM

13

job_end_wait_num

Standard job end operation (wait)

JOB_EXEC_END_BACKLOG_NUM

jobs

14

job_maximum_result_file_size

Standard job end operation (transferred file)

JOB_MAXIMUM_RESULT_FILE_SIZE

bytes

15

Jobnets and event jobs with start conditions

condrj_operation_result_num

Jobnet-related operation with start conditions (operational outcomes)

CONDRJ_MONITOR_START_NUM

operations

CONDRJ_EXEC_END_N_NUM

CONDRJ_EXEC_END_W_NUM

CONDRJ_EXEC_END_E_NUM

16

evjob_operation_result_num

Event job operation (operational outcomes)

EVJOB_EXEC_START_NUM

operations

EVJOB_EXEC_END_N_NUM

EVJOB_EXEC_END_W_NUM

EVJOB_EXEC_END_E_NUM

17

condrj_wait_num

Jobnet-related operation with start conditions (wait)

CONDRJ_EXEC_START_BACKLOG_NUM

operations

CONDRJ_EXEC_END_BACKLOG_NUM

18

evjob_wait_num

Event job operation (wait)

EVJOB_QUEUING_BACKLOG_NUM

operations

EVJOB_START_BACKLOG_NUM

EVJOB_DETECTED_NOTIFICATION_WITHO

UT_EV_END_BACKLOG_NUM

EVJOB_DETECTED_EV_END_BACKLOG_NUM

19

evjob_error_agent_detected

Event job operation (error agent)

EVJOB_ERROR_AGENT_DETECTED

detected/not detected

20

condrj_monitor_num

Jobnet-related operation with start conditions (monitored generation)

CONDRJ_EV_DETECTED_NUM

operations

CONDRJ_MONITOR_END_N_NUM

CONDRJ_NOMONITOR_END_NUM

CONDRJ_MONITOR_END_E_NUM

CONDRJ_MONITOR_STOPPED_END_NUM

21

evjob_other_num

Event job (number of notifications)

EVJOB_DETECTED_EV_NUM

jobs

22

Others

rj_exec_end_num

Root jobnet (number of finished jobnets)

NEST_EXEC_END_N_NUM

jobnets

NEST_EXEC_END_W_NUM

NEST_EXEC_END_E_NUM

23

nest_exec_end_num

Nested jobnet (number of finished nested jobnets)

NEST_EXEC_END_N_NUM

jobnets

NEST_EXEC_END_W_NUM

NEST_EXEC_END_E_NUM

24

qljob_exec_num

Queueless job related operation (operational outcomes)

QLJOB_EXEC_START_NUM

operations

QLJOB_EXEC_END_N_NUM

QLJOB_EXEC_END_W_NUM

QLJOB_EXEC_END_E_NUM

25

jobcon_exec_num

Jobnet connector related operation (operational outcomes)

JOBCON_EXEC_START_NUM

operations

JOBCON_EXEC_END_N_NUM

JOBCON_EXEC_END_W_NUM

JOBCON_EXEC_END_E_NUM

26

otherjob_exec_num

Other jobs (operational outcomes)

OTHERJOB_EXEC_START_NUM

jobs

OTHERJOB_EXEC_END_N_NUM

OTHERJOB_EXEC_END_E_NUM

27

delay_num

Delays

DELAY_NET_START_NUM

jobnets (jobs)

DELAY_NET_END_NUM

DELAY_ALLJOB_END_NUM

#

For details about the items output to the performance report of the ajsreport command, see the JP1/Automatic Job Management System 3 Command Reference.

The collection interval for the performance report is automatically adjusted to accommodate the maximum number of data per instance that can be displayed on the chart. For details about the number of data per instance that can be displayed on the chart, see the Appendix D.1 Limits when using the Intelligent Integrated Management Base in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

2.7.2 Metrics that can be retrieved from JP1/PFM

The following table lists the metrics that can be retrieved from JP1/PFM.

Table 2‒13: Metrics that can be retrieved from JP1/PFM

No.

Category name

Metric name

Metric display name

Description

Units

Product name

1

Management Applications

host_available_rate

Host available

Host available.

%

HealthCheck

2

Platform

cpu_used_rate

CPU used rate

If the PFM - View display name is Windows:

Processor usage. Percentage of elapsed time used by the processor for executing non-idle threads.

If the PFM - View display name is UNIX or RM Platform:

CPU usage. It also indicates the average value per processor.

%

Windows,

UNIX,

RM Platform

3

memory_unused

Memory unused

If the PFM - View display name is Windows:

Available size in the physical memory area. The combined total of zero memory, free memory, and standby memory (cached) that can be immediately allocated to a process or be used by the system.

If the PFM - View display name is UNIX or RM Platform:

The amount of physical memory that can be used by applications. For details about how to support OSs on monitored hosts other than Linux, see the manual of JP1/PFM - Agent Option for Platform for UNIX(R).

megabytes

4

disk_unused

Disk unused

Free disk space as part of the total usable area.

megabytes

5

disk_busy_rate

Disk busy rate

If the PFM - View display name is Windows:

Percentage of time the disk was busy when a read or write request was processed.

If the PFM - View display name is UNIX or RM Platform:

Percentage of time the disk was busy with read and write requests.This value may exceed 100 when processes are continuously executed on a device.

%

6

network_sent

Network sent

Rate at which packets were sent throughthe network interface.

packets/second

7

network_received

Network received

Rate at which packets were receivedthrough the network interface.

packets/second

8

Virtual Machine

cpu_used_rate

CPU used rate

Usage rate of CPU resources. Percentage of CPU resources used by the host machine.

%

RM VirtualMachine

9

memory_unused

Memory unused

Amount of unused memory resources. Memory resources unused by the host.

megabytes

10

disk_unused

Disk unused

Size of free space.

megabytes

11

network_sent

Network sent

Speed of sending to the network by the host machine.

KB/second

12

network_received

Network received

Speed of receiving from the network by the host machine.

KB/second

13

Database

transaction_executed

Transaction executed

Number of transactions per second.

transactions/second

Oracle,

RM Oracle,

SQL,

RM SQLServer

14

"buffer_cache_used_rate

Buffer cache used rate

Percentage ratio of logical read operations.

%

Oracle,

RM Oracle

15

library_cache_miss_rate

Library cache miss rate

Library cache miss rate

%

16

disk_sort_execution_rate

Disk sort execution rate

Percentage ratio of sort operations using temporary segment.

%

17

io_operated

I/O operated

Number of I/O operations per second.

I/O operations/second

18

pga_memory_used

PGA memory used

Size of PGA memory currently being used in bytes.

bytes

19

transaction_executed

Transaction executed

Number of Transact-SQL command batches per second executed within an interval.

transactions/second

SQL,

RM SQLServer

20

cache_hit_rate

Cache hit rate

Rate at which data pages were found inside the data cache.

%

21

disk_used

Disk used

Size of the entire database.

megabytes

22

physical_page_read

Physical page read

Number of physical pages read per second within an interval.

pages/second

23

physical_page_written

Physical page written

Number of physical pages written per second within an interval.

pages/second

24

Enterprise

front_end_wait_time

Wait time at the front end.

Average time the user waited at the front end for a request to be processed. This is the average of the totals of response time, network transfer time, and front-end processing time.

ms

SAP System

25

dialog_step_processing_time

Dialog step processing time

Average dialog step processing time in milliseconds. This is the total time required for processing a dialog step; it includes the database processing time but not the network transfer time or front-end processing time.

ms

26

dialog_steps

Number of dialog steps

Average number of dialog steps per minute.

steps

3 Event Console Window

This chapter describes the items displayed and defined in the Event Console window.

3.1 Overview of the Event Console window

When a user logs in to JP1/IM - Manager (Central Console), the Event Console window appears.

The Event Console window is used to monitor JP1 events and can be used to open windows for performing operations, such as executing a command, from the Event Console window.

The Event Console window has three pages: Monitor Events, Severe Events, and Search Events. The user displays a page by choosing the corresponding tab. For details about the Monitor Events page, see 3.2 Monitor Events page. For details about the Severe Events page, see 3.3 Severe Events page. For details about the Search Events page, see 3.4 Search Events page.

This section describes the items displayed in the Event Console window and the items that are common to all pages.

Note

Some of the items displayed in the Event Console window change if linkage with BJEX or JP1/AS is enabled. For information about the contents of the Event Console window when linkage with BJEX or JP1/AS is enabled, see 3.44.2 Event Console window.

The figure below shows an example of the Event Console window.

Note that some windows, buttons, and other items related to the Event Console window might not be enabled or displayed, depending on the version of JP1/IM - Manager (Central Console). For details, see Appendix H. Connectivity with Previous Versions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Figure 3‒1: Event Console window

The following describes the items displayed in the Event Console window:

Alarm indicator

Indicates whether there are unprocessed severe events on the Severe Events page.

If the alarm indicator is red, unprocessed severe events exist. If the alarm indicator is blue, no unprocessed severe events exist.

When all severe events displayed on the Severe Events page have been processed or deleted, the color of the alarm indicator changes from red to blue.

Toolbar

Provides buttons for executing functions that are frequently used in the Event Console window.

(Event Details button)

Opens the Event Details window, which displays the detailed attribute information of a selected JP1 event.

(Monitor button)

Opens the window of the application from which the selected JP1 event was sent.

(Execute Command button)

Opens the Execute Command window, from which the user can execute a command.

(Refresh button)

Refreshes the information displayed in the event list.

(Action Log button)

Opens the Action Log window to display the execution results of an automated action, if one has been set, for the selected JP1 event.

(Tool Launcher button)

Opens the Tool Launcher window.

(Central Scope button)

Opens the Monitoring Tree window.

Note that this button is disabled if OFF is specified for the -s option of the jcoimdef command and, after starting JP1/IM - Manager, the user restarts the connected JP1/IM - View. For details about the jcoimdef command, see jcoimdef in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(Help button)

Displays the online manual.

With the initial JP1/IM - View settings after installation, this button does not work. Refer to the applicable manual for the procedure to enable this button. For Windows, see 1.24 Saving manuals to a computer (for Windows) in the JP1/Integrated Management 3 - Manager Configuration Guide. For UNIX, see 2.22 Saving manuals to a computer (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide.

Event list

The event list indicates the status of an event (Processed, Unprocessed, Processing, or Held) with a status icon that corresponds to the event status. The following table lists the event statuses and the corresponding status icons.

Table 3‒1: Event statuses and corresponding icons

Event status

Status icon

Processed

Processing

Held

Unprocessed

None (blank)

Mixed#

!

#:

This status means that, when the suppression of monitoring of repeated events or consolidated display of repeated events is enabled, JP1 events for which different event statuses are set are consolidated into one consolidation event.

When the suppression of monitoring of repeated events is enabled, an exclamation mark (!) is displayed if the repeated events from the first event (a consolidation start event) to the 100th event do not all have the same status. When a consolidation event consists of 101 or more events, an exclamation mark (!) is not displayed even if the 101st or a subsequent repeated event has a different status from the first 100 repeated events.

The statuses that the user can set and how the settings are applied to other pages differ depending on the page. The following table describes the differences.

Table 3‒2: Differences in handling of event status settings among pages

Page

Event statuses that can be set

Number of events whose status can be set at one time

How the settings are applied to other pages#1

Monitor Events

Processed, Processing, Held, and Unprocessed

Multiple

Automatically

Severe Events

Processed, Processing, Held, Unprocessed, and Delete#2

Multiple

Automatically

Search Events

Processed, Processing, Held, and Unprocessed

Multiple

After another search is performed

#1: On the Monitor Events or Severe Events page, the event status settings specified on another page are applied automatically (when Automatic refresh is enabled in the Preferences window) or applied when Refresh is chosen from the View menu. On the Search Events page, another search must be performed to acquire the latest information.

The user can also set event statuses from the Related Events window. Which statuses can be set in the Related Events window and how the settings are applied to other pages is the same as on the page from which the window was displayed.

#2: JP1 events that are set to Delete status on the Severe Events page are only hidden on that page. Because these events remain in the event database and integrated monitoring database, they might appear on another page. If this occurs, the user can set the status of the event on that page.

After you set an event to the Delete status, you cannot display it again on the Severe Events page.

The Event level column in the event list shows the severity level (Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug) of each event. This column displays a character string indicating the severity level type of the event and the corresponding icon.

You can apply text and background colors corresponding to the severity level type to the events displayed in the event lists on the following pages:

Monitor Events page

Severe Events page

Search Events page

To apply text and background colors, enable the setting on the Event Attributes page in the Preferences window.

You can change the text and background colors by editing the system color definition file (systemColor.conf). For details, see System color definition file (systemColor.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The following table lists the types of severity levels, and the corresponding icons, text colors, and background colors.

Table 3‒3: Severity level types and the corresponding icons, text colors, and background colors

Severity level type

Icon

Text color#

Background color#

Emergency

White

Red

Alert

Critical

Error

Orange

Warning

Black

Yellow

Notice

White

Information

Debug

#: This column shows the colors for the default settings.

Note that in the Event Details window, the display item Source host is displayed as Event-issuing server.

In the event list, linefeed codes in event messages are ignored.

When consolidated display of repeated events is enabled

On the Monitor Events and Severe Events pages in the Event Console window, repeated events are consolidated as shown in the following figure.

Figure 3‒2:  Example of consolidated display of repeated events

The following items are displayed in a consolidated display of repeated events:

Summary Status

The number of event repetitions is displayed. Note that the displayed number includes one consolidation event. For non-consolidation events, this column is blank.

When consolidation has been completed

The number of event repetitions is displayed. When suppression of monitoring of repeated events is enabled, the range of values that can be displayed is from 1 to 1,000,000.

When consolidated display of repeated events is enabled, the range of values that can be displayed is from 1 to 100.

When consolidation is in progress

The number of event repetitions, followed by a plus sign (+) indicating that consolidation is in progress, is displayed.

When only a consolidation start event exists (there are no repeated events yet), 1+ is displayed. When a consolidation start event and one repeated event exist, 2+ is displayed. The range of displayed values in this case is from 1+ to 99+. Note, however, that on the Severe Events page, 0+ is displayed when the consolidation start event has been deleted and no repeated events exist.

If a consolidation start event is deleted on the Severe Events page of the Event Console window, the status of the consolidation start event changes to the deleted status, and Del is displayed to the right of the number of repetitions.

If severe events of the consolidation start event are released, the status of the severe events changes to the released status, and Released is displayed to the right of the number of repetitions.

Thereafter, when consolidation is completed and the event changes to a non-consolidated event in the deleted status or in the severe events released status, the event is no longer displayed on the Severe Events page of the Event Console window.

Display of the processing status of an event

An icon indicating the processing status of a JP1 event is displayed in the leftmost column.

The status icons and their meanings are the same as those displayed on the Monitor Events and Severe Events pages in the Event Console window.

When the statuses of repeated events and a consolidation event are different, an exclamation mark (!) is displayed.

Type

The icon indicating a correlation event is displayed.

Table 3‒4: Type

Type

Description

Indicates that the event is a correlation approval event.

Indicates that the event is a correlation failure event.

If many events occur when the monitoring of repeated events is suppressed, the icon is displayed.

As the default setting, the Type column is not displayed. The user can display this column by changing the setting in the Preferences window.

Action

When the function for suppressing automated actions is used, the suppression status is displayed with an icon in the Event Console window. The following table lists the status icons.

Table 3‒5: Action suppression status icons

Icon

Description

Action that has not been suppressed.

Action that has been suppressed.

Action that has been partially suppressed.

If many events occur when execution of automated actions is suppressed by a condition for suppressing monitoring of repeated events, the icon is displayed.

If a common exclusion-condition prevents an action from being executed, the icon is displayed.

When the statuses of repeated events and a consolidation event are different, an exclamation mark (!) is also displayed in the Action column.

Action type

The icon indicating an action type is displayed.

Table 3‒6: Action type

Action type

Description

A command is executed.

As the default setting, the Action type column is not displayed. The user can display this column by changing the setting in the Preferences window.

Monitor Events tab

Clicking the Monitor Events tab opens the Monitor Events page.

The Monitor Events page is the page displayed when the Event Console window is first opened. This page displays received JP1 events.

If many events occur when events are suppressed by suppression of monitoring of repeated events, the icon, which means that many events occurred, is displayed on the page.

Severe Events tab

Clicking the Severe Events tab opens the Severe Events page, which displays only severe events.

If many events occur when events are suppressed by suppression of monitoring of repeated events, the icon, which means that many events occurred, is displayed on the page.

Search Events tab

Clicking the Search Events tab opens the Search Events page, which displays JP1 event search results. The user can perform an event search by choosing Search Events from the View menu.

When the integrated monitoring database is used

When the user uses the integrated monitoring database together with the severity changing function, the function for setting memo entries, or the display message change function, the following items are displayed:

New Severity Level

If the user selects New Severity Level as a display item in the Preferences window, the New Severity Level column is displayed as shown below. By default, this column is not displayed.

Original Severity Level

If the user selects Original Severity Level as a display item in the Preferences window, the Original Severity Level column is displayed as shown below. By default, this column is not displayed.

Memo

If the user selects Memo as a display item in the Preferences window, the Memo column is displayed. By default, this column is not displayed.

Changed display message

If the user selects Changed display message as a display item in the Preferences window, the Changed display message column is displayed as shown below. By default, this column is not displayed.

New display message

If the user selects New display message as a display item in the Preferences window, the New display message column is displayed as shown below. By default, this column is not displayed.

Display message change definition name

If the user selects Display message change definition name as a display item in the Preferences window, the Display message change definition name column is displayed as shown below. By default, this column is not displayed.

The following table describes the menu items of the Event Console window.

Table 3‒7: Menu items of the Event Console window

Menu

Command

Description

File

Save Displayed Events

Saves the contents of the displayed event list in a CSV file.

Central Scope

Opens the Monitoring Tree window.

When the window opens, the user logged in to JP1/IM - Manager (Central Console) is logged in to the window. The Login window does not appear.

When the Monitoring Tree window and other windows are displayed within a process, the Monitoring Tree window is displayed in front.

Note that this command is disabled if OFF is specified for the -s option of the jcoimdef command and, after starting JP1/IM - Manager, the user restarts the connected JP1/IM - View. For details about the jcoimdef command, see jcoimdef in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Close

If the Monitoring Tree window has been displayed by choosing Central Scope from the File menu or by clicking the button, the following occurs:

The Monitoring Tree window is brought to the front.

The Event Console window is hidden.

If the Execute Command, List of Action Results, Event Details, and Related Events windows are displayed, they close.

If the Tool Launcher window is displayed, it continues to be displayed.

The profile is saved.

If the Monitoring Tree window has not been displayed by choosing Central Scope from the File menu or by clicking the button, the following occurs:

The message KAVB0122-I is displayed in a dialog box. The user can log out by clicking Yes.

If the Execute Command, List of Action Results, Event Details, and Related Events windows are displayed, they close.

If the Tool Launcher window is displayed, it closes.

The profile is saved.

Exit, Logout

Logs the user out from JP1/IM - Manager, and closes the window that is currently displayed. The following occurs:

The message KAVB0122-I is displayed in a dialog box. The user can log out by clicking Yes.

The displayed window closes.

Edit

Copy

Copies the items selected in the displayed event list to the clipboard.

Note that this command does not appear if the copy-to-clipboard function is disabled.#1

Select All

Selects all columns in the displayed event list.

Edit Event Details

Displays the Edit Event Details window.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Note that this command does not appear if the memo entries setup function is disabled.

View

View List of Filters

Displays the View List of Filters window.

This command is available when the Monitor Events page or Severe Events page is displayed.

View Filter Settings

Displays the Settings for the View Filter window, which is used to define event display conditions.

This command is available when the Monitor Events page or Severe Events page is displayed.

Apply Filter Settings

Enables or disables view filters.

This command is available when the Monitor Events page or Severe Events page is displayed.

Use specified display event period

Switches between enabling and disabling the display of events for the specified period.

Event Search Conditions

Displays the Search Events page, from which the user can retrieve JP1 events by specifying search conditions.

Search for Next Event

Performs another search to display the next set of search results. The user uses this command when all of the search results cannot be acquired in one search.

This command is not available when there are no events in the event list on the Search Events page or when a JP1 event output by JP1/IM is displayed at the top or bottom of the event list. For details about the JP1 events output by JP1/IM, see 3.2 JP1 events issued by JP1/IM in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Cancel Search

Cancels the search for JP1 events.

List of Action Results

Displays the List of Action Results window, which lists the execution results of automated actions set in the JP1/IM - Manager (Central Console) to which the user is logged in.

Event Details

Displays the Event Details window, which displays detailed attribute information for a selected JP1 event.

Display Related Event List

Displays the Related Events window.

The user can choose this command only in the following cases:

When a consolidation event is selected

The repeated events for the selected consolidation event are listed on the Monitor Events or Severe Events page.

When a correlation event is selected

The correlation source events for the selected correlation event are listed on the Monitor Events, Severe Events, or Search Events page.

When correlation events that have been consolidated are selected

The repeated events that are correlation events for the selected consolidation event are listed on the Monitor Events or Severe Events page.

In this case, the user can right-click a correlation event in the list to display a pop-up menu, from which the user can display a list of correlation source events for the correlation event.

Monitor

Displays the window for manipulating the information about the program that issued the selected JP1 event.

Action Log

Displays the Action Log window.

When an automated action has been defined for the selected JP1 event, the execution results of the automated action are displayed in the window.

Register Incident

Displays the Select the process work board as the registration target window, which is used to register incidents in JP1/Service Support.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command. Note that JP1/IM - Manager (Central Console) provides a setting that displays this menu item, and this menu item is displayed only when that setting is specified.#2

Also note that this menu item is disabled in the following cases:

No JP1 events are selected in the event list on a page.

The selected JP1 events are JP1 events displayed in the Search Events page as a result of performing an event search for a host that is not the JP1/IM - Manager host to which JP1/IM - View is connected.

The JP1 user who has logged in to JP1/IM - Manager (Central Console) has only JP1_Console_User permission or no permission.

Execute Command (Event Inheritance)

Displays the Execute Command window with the settings for inheriting the events selected in the event list. Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Display Performance

Opens a report window in JP1/PFM - Web Console that shows the performance of the host where the event selected in the event list occurred, at the time that the event occurred.

This menu item does not appear if the function for displaying performance reports of event-source hosts is disabled.#3.

This menu item is disabled in the following cases:

No JP1 events are selected in the Event Console window.

More than one JP1 event is selected in the Event Console window.

A dummy event is selected.

Processed

Sets the status of the selected events to Processed.

When this command is executed, is displayed in the first column of the selected events.

This command is available when the Monitor Events, Severe Events, or Search Events page is displayed.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Unprocessed

Sets the status of the selected events to Unprocessed.

This command is available when the Monitor Events, Severe Events, or Search Events page is displayed.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Processing

Sets the status of the selected events to Processing.

When this command is executed, is displayed in the first column of the selected events.

This command is available when the Monitor Events, Severe Events, or Search Events page is displayed.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Held

Sets the status of the selected events to Held.

When this command is executed, is displayed in the first column of the selected events.

This command is available when the Monitor Events, Severe Events, or Search Events page is displayed.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Delete

Deletes the severe events selected on the Severe Events page from the window, regardless of their status.

Although the events are deleted from the window, they are not actually deleted from the event database and integrated monitoring database.

After deleting an event in this way, you cannot display it on the Severe Events page again.

This command is available when the Severe Events page is displayed.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Release Severe Events

Changes the JP1 events displayed on the Severe Events page to non-severe events.

Note that if the integrated monitoring database is disabled, this command is not displayed.

If the user releases a severe event, the status of the event changes to the released status. Because the released events are no longer severe events, they no longer appear on the Severe Events page. Once a severe event has been released, the action cannot be undone.

Only users that have the JP1_Console_Admin permission can execute this command.

Exclude by Common Exclusion-Conditions

Displays the Common Exclusion-Condition Settings (Extended) window, which is used to set the selected event as a common exclusion-condition (extended).

Only users that have the JP1_Console_Admin#4 permission can execute this command.

Suppress by Repeated Event Conditions

Displays the Repeated Event Condition Settings window.

The user selects a JP1 event in the event list on the Monitor Events, Severe Events, or Search Events page before clicking this menu command. When the Repeated Event Condition Settings window opens, the conditions for the selected JP1 event are displayed in the window.

This command can be executed when suppression of monitoring of repeated events is enabled.

Only users that have JP1_Console_Admin#4 permission can execute this command.

Add Severity Change Definition Settings

Displays the Add Severity Change Definition Settings window.

The user selects a JP1 event in the event list on the Monitor Events, Severe Events, or Search Events page before clicking this menu command. When the Add Severity Change Definition Settings window opens, the conditions for the selected JP1 event are displayed in the window.

This command is available when severity changing definitions are enabled.

Only users who have the JP1_Console_Admin#4 permission can execute this command.

Add Display Message Change Definition Settings

Displays the Add Display Message Change Definition Settings window.

The user selects an event in the event list on the Monitor Events, Severe Events, or Search Events page before clicking this menu command. When the Add Display Message Change Definitions window opens, the conditions for the selected JP1 event are displayed in the window.

This command is available when display message change definitions are enabled.

Only users who have the JP1_Console_Admin#4 permission can execute this command.

This command can be used only if the IM database has been updated by using the jimdbupdate command after an upgrade installation was performed from version 10-50 or earlier.

Auto Scroll

Switches between enabling and disabling automatic scrolling of the event list on the Monitor Events or Severe Events page.

When automatic scrolling is enabled, the slider on the scroll bar of the event list automatically moves to the bottom when a new JP1 event is received.

Refresh

Refreshes the information displayed in the Event Console window.

Options

System Environment Settings

Displays the System Environment Settings window, which is used to set up the system environment. The user can use the window to change the JP1/IM basic operation settings such as the filter conditions and buffer size for collecting events.

Users that have the JP1_Console_Admin#4 permission can execute this command.

User Preferences

Displays the Preferences window, which is used to set up the user environment. The user can use the window to enable automatic refresh during event monitoring and set the items to be displayed in the event list.

Event Receiver Filter Settings

Displays the Settings for Event Receiver Filter window, which is used to specify user filter settings.

Users that have the JP1_Console_Admin#4 permission can execute this command.

Severe Event Definitions

Displays the Severe Event Definitions window, which is used to define the conditions for treating JP1 events as severe events.

Users that have the JP1_Console_Admin#4 permission can execute this command.

Event-Information Mapping Definitions

Displays the Event-Information Mapping Definitions window, which is used to map the items displayed in the event list with specific extended attributes.

Users that have the JP1_Console_Admin#4 permission can execute this command.

Automated Action Parameter Settings

Displays the Action Parameter Definitions window, which is used to specify the settings for automated actions.

Users that have the JP1_Console_Admin#4 permission can execute this command.

Repeated Event Condition Settings

Displays the List of Repeated Event Conditions window.

This command can be executed when suppression of monitoring of repeated events is enabled.

Only users that have JP1_Console_Admin#4 permission can execute this command.

Severity Change Definitions

Displays the View Severity Change Definitions window.

This command is available when severity changing definitions are enabled.

Only users who have the JP1_Console_Admin#4 permission can execute this command.

Display Message Change Definitions

Displays the Display Message Change Definitions window.

This command is available when display message change definitions are enabled.

Only users who have the JP1_Console_Admin#4 permission can execute this command.

This command can be used only if the IM database has been updated by using the jimdbupdate command after an upgrade installation was performed from version 10-50 or earlier.

Function-Status Notification Return

Cancels the notification suppression that was caused during delay monitoring, status monitoring, or accumulation monitoring of automated actions.

The user can select Action Delay Monitoring or Action Status Monitoring as the type of monitoring for which notification suppression is to be canceled.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Note that this command is disabled in the following cases:

When the function is not supported by the notification function

When the notification function has never been used

Execute Command

Displays the Execute Command window, which is used to execute a command on a monitored host.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can execute this command.

Tool Launcher

Displays the Tool Launcher window.

Help

Help Contents

Displays the Help contents.

About JP1/IM - View

Displays the JP1/IM - View version information.

#1: This command appears when the copy-to-clipboard function is enabled in the IM-View settings file (tuning.conf). For details, see IM-View settings file (tuning.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

#2: This menu command is displayed when the settings described in the following procedure have been specified:

To specify the settings for launching a JP1/Service Support window:

For details, see 10.1.1 Enabling calling the JP1/Service Support window in the JP1/Integrated Management 3 - Manager Configuration Guide.

#3: This menu item is displayed only if the function for displaying performance reports of event-source hosts is enabled. For details about this function, see 10.7 Linking with JP1/PFM in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

#4: If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

3.2 Monitor Events page

The Monitor Events page of the Event Console window displays a list of received JP1 events. The following figure shows an example of the Event Console window with the Monitor Events page opened.

Figure 3‒3: Event Console window (Monitor Events page)

The following describes the items displayed on the Monitor Events page:

(Expand/Shrink button)

Clicking this button displays or hides the event display start-time specification area. The user can expand or shrink this area when the integrated monitoring database is used. The area is enabled when a JP1 event is registered in the integrated monitoring database. If the integrated monitoring database is not used, the area is disabled ().

Display range

The range of arrival times of the listed JP1 events is displayed in the following format (Δ represents a space character):

If one or more JP1 events are displayed in the list:

Display range:Δarrival-time-of-the-oldest-JP1-event(displayed in the YYYY/MM/DDΔhh:mm:ss format)Δ-Δarrival-time-of-the-latest-JP1-event(displayed in the YYYY/MM/DDΔhh:mm:ss format)

If no JP1 events are displayed in the list:

Display range:-Δ

View Filter Settings

Clicking this button displays the Settings for View Filter window. The user can use the window to set view filters, which define the conditions for displaying JP1 events.

Filter name drop-down list

This drop-down list is used to select a view filter for displaying a list of JP1 events.

View filter

This check box is used to determine whether to enable the view filter selected from the Filter name drop-down list. If this check box is selected, the view filter is enabled and the JP1 events that satisfy the conditions defined in the view filter are displayed.

Use specified display event period

If the Display check box has been selected in the Specified display event period area of the User Preferences window, the following check boxes appear.

If the user selects the Use specified display event period check box, the Use event collection range setting function is applied, and the JP1 events are listed according to the conditions.

For details on the event collection range setting function, see 4.18 Specifying the event display period in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Event list

The list of JP1 events. Events are listed from the oldest (top) to the most recent (bottom). The JP1 events displayed in the event list have been transferred to the JP1/IM - Manager (Central Console) to which the user logged in.

When the status of event is changed, a maximum of 2,000 events can be changed at one time. When the integrated monitoring database is used, all JP1 events registered in the integrated monitoring database can be displayed.

When the integrated monitoring database is used, the user can use the event display start-time specification area. The following figure shows the event display start-time specification area.

Figure 3‒4: Monitor Events page with the event display start-time specification area displayed

Event display start-time specification area

When the integrated monitoring database is used, the user can use the event display start-time specification area to specify the event display start-time of JP1 events to be displayed. This area is not displayed at login. If the integrated monitoring database is not used or if no JP1 events are registered in the integrated monitoring database, the user cannot open the event display start-time specification area.

If the user uses the display start-time specification area to search for events, the Status section in the display start-time specification area changes according to the search status and the search results. The following table describes how the Status section changes.

Table 3‒8: Status section

Status

Description

Status section

Items used for operations

Most recent

The latest status is displayed in the event list.

Status: ΔMost recent events displayed

--

Updating

The JP1 events for the specified date and time are being retrieved from the integrated monitoring database, and the event list display is being updated.

Status: ΔUpdating... (event-display-start-time)

Slider, Display button, Oldest Event button

Status: ΔUpdating... (Previous event display)

Previous Event button

Status: ΔUpdating... (Next event display)

Next Event button

Updating completed

The event list was successfully updated.

Status: ΔUpdate ended. (event-display-start-time)

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Previous event display)

Previous Event button

Status: ΔUpdate ended. (Next event display)

Next Event button

The search for updating the event list has been completed to the beginning of the integrated monitoring database.

Status: ΔUpdate ended. (Previous event display) - Oldest event

Previous Event button

The search for updating the event list has been completed to the end of the integrated monitoring database.

Status: ΔUpdate ended. (event-display-start-time) - Most recent event

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Next event display) - Most recent event

Next Event button

Updating of the event list has been canceled and has ended.

Status: ΔUpdate ended. (event-display-start-time) - Interrupted

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Previous event display) - Interrupted

Previous Event button

Status: ΔUpdate ended. (Next event display) - Interrupted

Next Event button

An error has occurred during the event list update processing.

Status: ΔUpdate ended. (event-display-start-time) - Interrupted by error

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Previous event display) - Interrupted by error

Previous Event button

Status: ΔUpdate ended. (Next event display) - Interrupted by error

Next Event button

Legend:

event-display-start-time: The format is YYYY/MM/DDΔhh:mm:ss, where YYYY indicates the year, MM the month, DD the day, Δ a space, hh hours, mm minutes, and ss seconds).

Δ: Space

--: None

The following describes the items in the event display start-time specification area:

Event display start-time text boxes

Used to specify the start time for displaying the JP1 events. If the user enters the event arrival time for the JP1 events that the user wants to display in the text box, and then clicks the Display button, issued JP1 events arriving at or after the specified arrival time are displayed in the event list. By default, the base time for the date on which the user logged in to JP1/IM - Manager is displayed.

The base time can be set in the Specified display event period area of the Preferences window.

Note that if the Display check box in this area is not selected, the default base time (9:00) is used.

However, if the user logs in before the day's base time, the base time of the previous date is displayed.

A time that meets any of the following conditions cannot be specified in the Event display start-time text boxes:

A time later than the arrival time of the latest event that JP1/IM - View has received.

If JP1/IM - View has not received any events, a time later than the arrival time of the latest event registered in the integrated monitoring database.

When the Use specified display event period check box is selected, a time outside the specified period of time.

A time earlier than the arrival time of the oldest event that is registered in the integrated monitoring database.

Display

Displays JP1 events arriving at or after the time specified in the event display start-time text boxes.

Cancel

Interrupts the acquisition of the JP1 events to be displayed.

This button is disabled if the retrieval of events has finished.

(Oldest Event button)

Displays the JP1 events registered in the integrated monitoring database with the oldest at the top. Note that if the Use specified display event period check box has been selected, events are displayed for the specified range with the oldest at the top.

(Previous Event button)

Displays events starting with the one that immediately precedes the oldest event (excluding dummy events) in the event list area.

When the repeated event monitoring suppression function is enabled, repeated events are not displayed as consolidated events and the event preceding the oldest event in the list area is displayed.

If no JP1 events are displayed in the event list, this button is disabled.

(Slider)

The user can specify the JP1 event display start-time by moving the slider to the desired position. Moving the slider to the left specifies an event display start-time that displays older JP1 events. Moving the slider to the right specifies an event display start-time that displays more recent JP1 events. The user can confirm the exact event display start-time by checking the text boxes above the slider.

When the most recent event is displayed, the slider is positioned at its rightmost position, and Most recent events appears above the slider.

(Next Event button)

Displays events starting with the one that immediately follows the newest event (excluding dummy events) in the event list area.

If no JP1 events are displayed in the event list, this button is disabled.

(Most Recent Event button)

Returns the event list to its original state before the user specified an event display start-time.

3.3 Severe Events page

The Severe Events page of the Event Console window also includes an event list, but one that contains only severe events. The following figure shows an example of the Event Console window with the Severe Events page opened.

Figure 3‒5: Event Console window (Severe Events page)

The following describes the items displayed on the Severe Events page:

(Expand/Shrink button)

Clicking this button displays or hides the event display start-time specification area. The user can expand or shrink this area when the integrated monitoring database is used. The area is enabled when a JP1 event is registered in the integrated monitoring database. If the integrated monitoring database is not used, the area is disabled ().

Display range

The range of arrival times of the listed JP1 events is displayed in the following format (Δ represents a space character):

If one or more JP1 events are displayed in the list:

Display range:Δarrival-time-of-the-oldest-JP1-event(displayed in the YYYY/MM/DDΔhh:mm:ss format)Δ-Δarrival-time-of-the-latest-JP1-event(displayed in the YYYY/MM/DDΔhh:mm:ss format)

If no JP1 events are displayed in the list:

Display range:-Δ

View Filter Settings...

Sets the view filter that defines the conditions for displaying JP1 events. Clicking this button displays the Settings for View Filter window.

Filter name:

A list box in which the user can select a view filter. The filter selected in this list box determines which JP1 events appear on the Severe Events page.

View filter

Use this check box to specify whether to apply the view filter selected in the Filter name list box. When you select this check box, the view filter is enabled and the list of JP1 events only shows those that meet the filter conditions.

Use specified display event period

If Specified display event period is enabled in the Preferences window, Use specified display event period appears as shown below.

Selecting this check box enables the event collection range setting function, and the list of JP1 events only shows those that meet the conditions.

For details on the event collection range setting function, see 4.18 Specifying the event display period in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Processed

Clicking this button changes the status of the selected severe events to Processed. When this button is clicked, is displayed in the leftmost column of the selected severe events.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can use this button.

Unprocessed

Clicking this button changes the status of the selected severe events to Unprocessed.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can use this button.

Processing

Clicking this button changes the status of the selected severe events to Processing. When this button is clicked, is displayed in the leftmost column of the selected severe events.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can use this button.

Held

Clicking this button changes the status of the selected severe events to Held. When this button is clicked, is displayed in the leftmost column of the selected severe events.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can use this button.

Delete

Clicking this button deletes the selected severe events from the window, regardless of their status.

This button deletes the selected severe events from only the Severe Events page. It does not delete them from the Monitor Events page, Search Events page, and event database.

Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can use this button.

Note that if the repeated event monitoring suppression function is enabled, deleting a consolidation event deletes consolidated repeated events that are among the oldest 100 and are not yet deleted. The rest of repeated events that were consolidated remain. The number of repeated events for a consolidation event does not change after repeated events are deleted.

After you delete an event in this way, you cannot display it again on the Severe Events page.

Event list

The event list displayed on the Severe Events page contains only the severe events among the JP1 events that are displayed on the Monitor Events page.

Note that the Source host item displayed on the Severe Events page corresponds to the Source event server name item displayed in the Event Details window.

The user can use the event list to change the status of the displayed events. The maximum number of events whose status can be changed at one time is 2,000.

When the integrated monitoring database is used, all JP1 events registered in the integrated monitoring database can be displayed.

When the integrated monitoring database is used, the user can use the event display start-time specification area. The following figure shows the event display start-time specification area.

Figure 3‒6: Severe Events page with the event display start-time specification area displayed

Event display start-time specification area

When the integrated monitoring database is used, the user can use the event display start-time specification area to specify the event display start-time of JP1 events to be displayed. This area is not displayed at login. If the integrated monitoring database is not used or if no JP1 events are registered in the integrated monitoring database, the user cannot open the event display start-time specification area. Note that if the user specifies a display start-time, the deleted severe events are also displayed, but with a background color that has changed to gray. Released severe events are not displayed.

If the user uses the display start-time specification area to search for events, the Status section in the display start-time specification area changes according to the search status and the search results. The following table describes how the Status section changes.

Table 3‒9: Status section

Status

Description

Status section

Items used for operations

Most recent

The latest status is displayed in the event list.

Status: ΔMost recent events displayed

--

Updating

The JP1 events for the specified date and time are being retrieved from the integrated monitoring database, and the event list display is being updated.

Status: ΔUpdating... (event-display-start-time)

Slider, Display button, Oldest Event button

Status: ΔUpdating... (Previous event display)

Previous Event button

Status: ΔUpdating... (Next event display)

Next Event button

Updating completed

The event list was successfully updated.

Status: ΔUpdate ended. (event-display-start-time)

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Previous event display)

Previous Event button

Status: ΔUpdate ended. (Next event display)

Next Event button

The search for updating the event list has been completed to the beginning of the integrated monitoring database.

Status: ΔUpdate ended. (Previous event display) - Oldest event

Previous Event button

The search for updating the event list has been completed to the end of the integrated monitoring database.

Status: ΔUpdate ended. (event-display-start-time) - Most recent event

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Next event display) - Most recent event

Next Event button

Updating of the event list has been canceled and has ended.

Status: ΔUpdate ended. (event-display-start-time) - Interrupted

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Previous event display) - Interrupted

Previous Event button

Status: ΔUpdate ended. (Next event display) - Interrupted

Next Event button

An error has occurred during the event list update processing.

Status: ΔUpdate ended. (event-display-start-time) - Interrupted by error

Slider, Display button, Oldest Event button

Status: ΔUpdate ended. (Previous event display) - Interrupted by error

Previous Event button

Status: ΔUpdate ended. (Next event display) - Interrupted by error

Next Event button

Legend:

event-display-start-time: The format is YYYY/MM/DDΔhh:mm:ss, where YYYY indicates the year, MM the month, DD the day, Δ a space, hh hours, mm minutes, and ss seconds).

Δ: Space

--: None

The following describes the items in the event display start-time specification area:

Event display start-time text boxes

Used to specify the start time for displaying the JP1 events. If the user enters the event arrival time for the JP1 events that the user wants to display in the text box, and then clicks the Display button, issued JP1 events arriving at or after the specified arrival time are displayed in the event list. By default, the base time for the day on which the user logged in to JP1/IM - Manager is displayed.

You can set the base time in the Base time fields in the Specified display event period area of the Preferences window.

If you are not selecting the Use specified display event period check box, the default base time (09:00) applies.

However, if the user logs in before the day's base time, the base time of the previous date is displayed.

You cannot specify a time that meets any of the following conditions in the event display start-time text boxes:

A time later than the arrival time of the latest event received by JP1/IM - View

If JP1/IM - View has not received any events, a time later than the arrival time of the latest event registered in the integrated monitoring database

If the Use specified display event period check box has been selected, a time outside the specified time period

A time earlier than the arrival time of the oldest event registered in the integrated monitoring database

Display

Displays JP1 events arriving at or after the time specified in the event display start-time text boxes.

Cancel

Interrupts the acquisition of the JP1 events to be displayed.

This button is disabled if the retrieval of events has finished.

(Oldest Event button)

Displays the JP1 events registered in the integrated monitoring database with the oldest at the top. Note that if the Use specified display event period check box has been selected, events are displayed for the specified range with the oldest at the top.

(Previous Event button)

Displays events starting with the one that immediately precedes the oldest event (excluding dummy events) in the event list area.

When the repeated event monitoring suppression function is enabled, repeated events are not displayed as consolidated events and the event preceding the oldest event in the list area is displayed.

If no JP1 events are displayed in the event list, this button is disabled.

(Slider)

The user can specify the JP1 event display start-time by moving the slider to the desired position. Moving the slider to the left specifies an event display start-time that displays older JP1 events. Moving the slider to the right specifies an event display start-time that displays more recent JP1 events. The user can confirm the exact event display start-time by checking the text boxes above the slider.

When the most recent event is displayed, the slider is positioned at its rightmost position, and Most recent events appears above the slider.

(Next Event button)

Displays events starting with the one that immediately follows the newest event (excluding dummy events) in the event list area.

If no JP1 events are displayed in the event list, this button is disabled.

(Most Recent Event button)

Returns the events list to its original state before the user specified an event display start-time.

3.4 Search Events page

The Search Events page of the Event Console window displays the results of a JP1 event search performed in the Event Search Conditions window. Each time that an event matching the specified search conditions is retrieved, it is displayed. The following figure shows an example of the Event Console window with the Search Events page opened.

Figure 3‒7: Event Console window (Search Events page)

The following describes the items displayed on the Search Events page:

Event Search Conditions

Clicking this button allows the user to specify the JP1 event search conditions.

Cancel Search

Clicking this button cancels the JP1 event search.

Search for Next Event

When many JP1 events match the search conditions, a single search might not be able to retrieve all the results. When this button is clicked, another search is performed to display more results.

This button is not available in the following cases:

When no events are displayed in the event list on the Search Events page

When an error occurs while searching for an event, and JP1 events with the following event IDs are displayed at the top or bottom of the event list:

3F03, 3F04, 3F05, and 3F06

When the event search is canceled

When a search for older events ends because it has reached the beginning of the event database.

Event list

The event list on the Search Events page displays the results of a JP1 event search.

Note that the Source host item displayed on the Search Events page corresponds to the Source event server name item displayed in the Event Details window.

The user can use the event list to change the status of the displayed events. The maximum number of events whose status can be changed at one time is 2,000.

Search Events tab

If no event search is in progress, Search Events is displayed on the Search Events page tab. If an event search is in progress, Search Events (Searching) is displayed on the tab.

3.5 Tool Launcher window

The Tool Launcher window is used to start related programs, such as JP1 programs.

Any of the following operations displays the window:

In the Event Console window, the user chooses Tool Launcher from the Options menu.

In the Monitoring Tree window, the user chooses Tool Launcher from the Options menu.

In the Event Console window or Monitoring Tree window, the user clicks the button on the toolbar.

The following figure shows an example of the Tool Launcher window.

Figure 3‒8: Tool Launcher window

The following describes the items displayed in the Tool Launcher window:

Toolbar

Provides buttons for operations that are frequently used in the Tool Launcher window. Toolbar buttons are displayed only if the corresponding products are installed and can be linked.

Starts Network Node Manager, and displays a window for HP NNM version 7.5 or earlier.

Starts Windows Remote Controller, and displays the JP1/Remote Control Manager window or the JP1/Software Distribution window.

Starts the resource and distribution management function, and displays the JP1/Software Distribution Manager window.

Tree area

The functions that can be started are displayed in a tree structure. When the user double-clicks a program icon in the tree, the corresponding program window appears.

For details about the functions that can be started from the Tool Launcher window, see 8.3.2 Functions that can be operated from the Tool Launcher window in the JP1/Integrated Management 3 - Manager Administration Guide.

3.6 Event Details window

The Event Details window displays detailed attribute information about a JP1 event. Either of the following operations displays the window:

In the Event Console window, the user chooses Event Details from the View menu.

In the Related Events window, the user selects and right-clicks a JP1 event, and then chooses Event Details from the displayed pop-up menu.

The following figure shows an example of the Event Details window.

Figure 3‒9: Event Details window

If command buttons are enabled, the Execute Command button is displayed at the bottom of the Event Details window as shown below.

Figure 3‒10: Button displayed in the Event Details window (when command buttons are enabled)

If linkage with JP1/Service Support is enabled, the Register Incident button is displayed at the bottom of the Event Details window as shown below.

Figure 3‒11: Register Incident button displayed in the Event Details window (when linkage is enabled)

If the function for displaying performance reports of event-source hosts is enabled, the Display Performance button is displayed at the bottom of the Event Details window, as shown in the following figure.

Figure 3‒12:  Display Performance button displayed in the Event Details window (when the function for displaying performance reports of event-source hosts is enabled)

Note

Some of the items displayed in the Event Details window change if linkage with BJEX or JP1/AS is enabled. For information about the contents of the Event Details window when linkage with BJEX or JP1/AS is enabled, see 3.44.3 Event Details window.

The following describes the items displayed in the Event Details window:

Edit

Clicking this button displays the Edit Event Details window. The Edit button is displayed only if settings for the integrated monitoring database and memo entries have been specified. Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can use this button.

Previous

Clicking this button displays the detailed information about the JP1 event displayed one row above in the event list. Note that this button is disabled in the following cases:

When two or more events are selected in the Event Console window

When the JP1 event displayed at the top of the event list is selected

Next

Clicking this button displays the detailed information about the JP1 event displayed one row below in the event list. Note that this button is disabled in the following cases:

When two or more events are selected in the Event Console window

When the JP1 event displayed at the bottom of the event list is selected

Event attributes

This area displays the attribute names and values for a JP1 event. The attribute names that are displayed depend on the event.

Message

This area displays the message text of a JP1 event.

Message after the change/Message before the change

You can use the radio buttons to switch the message to be displayed between the message that was changed by the display message change function and the message before the change. If you select the Message after the change radio button, the changed display message is displayed. If you select the Message before the change radio button, the message before the change is displayed.

If the message of the JP1 event has not been changed (if the value of E.@JP1IM_CHANGE_MESSAGE is not 1), the radio buttons are unavailable with the Message before the change radio button selected.

If you move an event by using the Previous or Next button, the selected state of the radio buttons is kept. However, if the message of the JP1 event has not been changed, the Message before the change button is selected.

If the IM database has not been updated by using the jimdbupdate command after an upgrade installation was performed from version 10-50 or earlier, the radio buttons are unavailable with the Message before the change radio button selected.

Guide

This area displays the event guide information for the JP1 event for which detailed information is displayed. If no event guide information exists for the JP1 event, the following message appears:

KAVB1588-I

The Guide area is displayed only if the event guide function is enabled.

The event guide information to be displayed in this area must be specified in the event guide information file. For details about the event guide information file, see Event guide information file (jco_guide.txt) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Memo

This area displays memo entries set for the JP1 event. The Memo area is displayed only if settings for the integrated monitoring database and memo entries have been specified. For details, see 5.7 Setting memo entries in the JP1/Integrated Management 3 - Manager Configuration Guide.

Execute Command

Clicking this button displays the Execute Command window that can be used to execute commands. This button is displayed only when command buttons are enabled. Users that have JP1_Console_Admin or JP1_Console_Operator permission can use this button.

The procedure for enabling command buttons is described in the JP1/Integrated Management 3 - Manager Configuration Guide, but the relevant section differs according to the platform. If the platform is Windows, see 1.16 Setting up a command execution environment (for Windows). If the platform is UNIX, see 2.15 Setting up a command execution environment (for UNIX).

Monitor

Clicking this button opens the monitor window for the JP1 event for which detailed information is displayed. This button is disabled if no monitor window has been set for the JP1 event.

Action Log

Clicking this button opens the Action Log window if an automated action has been set for the JP1 event for which detailed information is displayed.

Register Incident

Clicking this button opens the Select the process work board as the registration target window of JP1/Service Support. This window can be used to register the displayed JP1 event as an incident.

This button is displayed only when linkage with JP1/Service Support is enabled.

For details about the settings for JP1/Service Support linkage, see the following descriptions:

Linkage with JP1/Service Support:

For details, see 10.1 Linking with JP1/Service Support in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

To specify the settings for launching a JP1/Service Support window:

For details, see 10.1.1 Enabling calling the JP1/Service Support window in the JP1/Integrated Management 3 - Manager Configuration Guide.

Relation definition file:

For details, see Definition file for manually registering incidents (incident.conf) in Chapter 2. Definition Files, and Configuration file for incident inheritance information (incident_info.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

This button is disabled when:

The JP1 user who has logged in to JP1/IM - Manager (Central Console) has only JP1_Console_User permission or no permission.

No JP1 event is selected in the Event Console window.

A event search is performed for a host to which JP1/IM - View is not connected and the details of a JP1 event registered on that host are displayed.

If event-source-host mapping is enabled, the attributes of JP1 events that can be registered as incidents change.

For details about the attributes of JP1 events that can be registered as incidents, see 10.1.1 Attributes of a JP1 event registered as an incident in JP1/Service Support during linkage in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Note

If the message KAVB0291-E is displayed in the Message area, the Register Incident button is disabled.

This symptom occurs if the detailed information to be displayed in the Event Details window cannot be received. This can happen when, for example, data in the JP1/Base event database wraps around, causing the relevant JP1 event information to be unavailable.

Display Performance

Clicking this button opens a report window in JP1/PFM - Web Console that shows the performance of the host where the event selected in the event list occurred at the time that the event occurred.

This button is displayed only when the function for displaying performance reports of event-source hosts is enabled. For details about this function, see 10.7 Linking with JP1/PFM in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Note that this button is disabled in the following cases:

No JP1 events are selected in the Event Console window.

More than one JP1 event is selected in the Event Console window.

A dummy event is selected.

3.7 Edit Event Details window

This window is used to edit and specify the memo entries of JP1 events when the memo entries setting function is enabled.

When the integrated monitoring database is used, the memo entries setting function allows the user to add notes to JP1 events saved in the integrated monitoring database that are displayed in the Event Console window. Users that have JP1_Console_Admin permission or JP1_Console_Operator permission can use this function.

Either of the following operations displays the window:

Clicking the Edit button in the Event Details window

Selecting a JP1 event in the Event Console window and selecting Edit Event Details from the Edit menu, or right-clicking the event and clicking Edit Event Details from the pop-up menu

The following figure shows an example of the Edit Event Details window.

Figure 3‒13: Edit Event Details window

If command buttons are enabled, the Execute Command button is displayed at the bottom of the Edit Event Details window as shown below.

Figure 3‒14: Button displayed in the Edit Event Details window (when command buttons are enabled)

If linkage with JP1/Service Support is enabled, the Register Incident button is displayed at the bottom of the Edit Event Details window as shown below.

Figure 3‒15: Register Incident button displayed in the Edit Event Details window (when linkage is enabled)

If the function for displaying performance reports of event-source hosts is enabled, the Display Performance button is displayed at the bottom of the Event Details window as shown below.

Figure 3‒16:  Button displayed in the Event Details window (when the function for displaying performance reports of event-source hosts is enabled)

Note

Some of the items displayed in the Event Details window change if linkage with BJEX or JP1/AS is enabled. For information about the window contents when linkage with BJEX or JP1/AS is enabled, see 3.44.3 Event Details window.

The following describes the items displayed in the Edit Event Details window:

Event attributes

This area displays the attribute names and values for a JP1 event. The attribute names that are displayed depend on the event.

Message

This area displays the message text of a JP1 event.

Message after the change/Message before the change

You can use the radio buttons to switch the message to be displayed between the message that was changed by the display message change function and the message before the change. If you select the Message after the change radio button, the changed display message is displayed. If you select the Message before the change radio button, the message before the change is displayed.

If the message of the JP1 event has not been changed (if the value of E.@JP1IM_CHANGE_MESSAGE is not 1), the radio buttons are unavailable with the Message before the change radio button selected.

If the IM database has not been updated by using the jimdbupdate command after an upgrade installation was performed from version 10-50 or earlier, the radio buttons are unavailable with the Message before the change radio button selected.

Guide

This area displays the event guide information for the JP1 event for which detailed information is displayed. If no event guide information exists for the JP1 event, the following message appears:

KAVB1588-I

The Guide area is displayed only if the event guide function is enabled.

The event guide information to be displayed in this area must be specified in the event guide information file. For details about the event guide information file, see Event guide information file (jco_guide.txt) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Memo

This area is used to display and edit memo entries for the displayed JP1 event. A character string of no more than 512 bytes can be entered in this area.

The following buttons are available in the Memo area.

Clear

Deletes the character string entered in the Memo area.

Apply

Stores the character string entered in the Memo area as a memo entry for the displayed JP1 event. The button is disabled when the memo entry has been stored.

Execute Command

Clicking this button displays the Execute Command window that can be used to execute commands. This button is displayed only when command buttons are enabled. Users that have JP1_Console_Admin or JP1_Console_Operator permission can use this button.

The procedure for enabling command buttons is described in the JP1/Integrated Management 3 - Manager Configuration Guide, but the relevant section differs according to the platform. If the platform is Windows, see 1.16 Setting up a command execution environment (for Windows). If the platform is UNIX, see 2.15 Setting up a command execution environment (for UNIX).

Monitor

Clicking this button opens the monitor window for the JP1 event for which detailed information is displayed. This button is disabled when no monitor window has been set for the JP1 event.

Action Log

Clicking this button opens the Action Log window if an automated action has been set for the JP1 event for which detailed information is displayed.

Register Incident

Clicking this button opens the Select the process work board as the registration target window of JP1/Service Support. This window can be used to register the displayed JP1 event as an incident.

This button is displayed only when linkage with JP1/Service Support is enabled.

For details about the settings for enabling the linkage, see the following descriptions:

To specify the settings for launching a JP1/Service Support window:

For details, see 10.1.1 Enabling calling the JP1/Service Support window in the JP1/Integrated Management 3 - Manager Configuration Guide.

Relation definition file:

For details, see Definition file for manually registering incidents (incident.conf) in Chapter 2. Definition Files, and Configuration file for incident inheritance information (incident_info.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

This button is disabled when:

The JP1 user who has logged in to JP1/IM - Manager (Central Console) has only JP1_Console_User permission or no permission.

No JP1 event is selected in the Event Console window.

A event search is performed for a host to which JP1/IM - View is not connected and the details of a JP1 event registered on that host are displayed.

Note

If the message KAVB0291-E is displayed in the Message area, the Register Incident button is disabled.

This symptom occurs if the detailed information to be displayed in the Event Details window cannot be received. This can happen when, for example, data in the JP1/Base event database wraps around, causing the relevant JP1 event information to be unavailable.

Display Performance

Clicking this button opens a report window in JP1/PFM - Web Console that shows the performance of the host where the event selected in the event list occurred at the time that the event occurred.

This button is displayed only when the function for displaying performance reports of event-source hosts is enabled. For details about this function, see 10.7 Linking with JP1/PFM in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Note that this button is disabled in the following cases:

No JP1 events are selected in the Event Console window.

More than one JP1 event is selected in the Event Console window.

A dummy event is selected.

3.8 Related Events (Summary) window

When suppression of monitoring of repeated events or consolidated display of repeated events is enabled, the Related Events (Summary) window lists the repeated events in the consolidation event.

The Related Events (Summary) window is displayed in either of the following cases:

The user selects a consolidation event in the Event Console window (Monitor Events or Severe Events page), and selects View then Display Related Event List from the menu bar.

The user right-clicks a consolidation event in the Event Console window (Monitor Events or Severe Events page) and chooses Display Related Event List from the pop-up menu.

Note that the Related Events (Summary) window is displayed only when consolidation events exist.

The following figure shows an example of the Related Events (Summary) window.

Figure 3‒17: Related Events (Summary) window

Figure 3‒18: Related Events (Summary) window when suppression of monitoring of repeated events is enabled

Note

Some of the items displayed in the Related Events (Summary) window change if linkage with BJEX or JP1/AS is enabled. For information about the contents of the Related Events (Summary) window when linkage with BJEX or JP1/AS is enabled, see 3.44.5 Related Events windows.

The following describes the items displayed in the Related Events (Summary) window:

Display Items

This area displays the consolidation event selected in the Event Console window (Monitor Events or Severe Events page). The items displayed in Display Items are the same as the items displayed in the Event Console window when the suppression of monitoring of repeated events or consolidated display of repeated events is enabled. As in the Event Console window, the user can change the status of the consolidation event. When the Related Events (Summary) window has been opened from the Severe Events page, the user can delete the consolidation event.

Information is displayed in the Display Items area as follows:

If the event status is changed, the corresponding status icon is displayed in the leftmost column. If suppression of monitoring of repeated events is enabled, the status change applies to the oldest 100 repeated events displayed in the Related Events list (response status icons are also displayed). The status change is not applied to the 101st and subsequent repeated events.

If consolidated display of repeated events is enabled, the status change is applied to all repeated events (response status icons are also displayed).

If the status of the consolidation start event displayed in the Related Events list is changed and the corresponding status icon is displayed, the status icon is also displayed in the leftmost column of the Display Items area.

When the repeated event monitoring suppression function is enabled, an exclamation mark (!) is displayed in the leftmost column of the Display Items area if the oldest 100 repeated events do not all have the same status. If these events have the same status, no exclamation mark (!) is displayed.

When consolidated display of repeated events is enabled, an exclamation mark (!) is displayed in the leftmost column of the Display Items area if repeated events do not all have the same status.

If the consolidation event is deleted, Del is displayed as the consolidation status in the Display Items area, and the displayed items are dimmed. In addition, all the repeated events displayed in the Related Events area are deleted.

If the repeated event monitoring suppression function is enabled, the oldest 100 repeated events displayed in the Related Events list are deleted. Even if repeated events that follow the 100th repeated event are deleted, the number of consolidated repeated events that are displayed in Display Items is not reduced.

If consolidated display of repeated events is enabled, all repeated events displayed in the Related Events list are deleted.

If the consolidation start event displayed in the Related Events list is deleted, Del is displayed as the consolidation status of the consolidation event displayed in the Display Items area, and the displayed items are dimmed.

If the display items in the Preferences window are changed, the items displayed in the Display Items area are also changed.

Display window

The name of the page from which the Related Events (Summary) window was opened is displayed in the following format:

Display window: page-name

The following table lists the page names that can be displayed after Display window.

Table 3‒10: Page names that can be displayed after "Display window"

No.

Page name

Description

1

Monitor Events

Displayed when the Related Events (Summary) window is opened from the Monitor Events page of the Event Console window.

2

Severe Events

Displayed when the Related Events (Summary) window is opened from the Severe Events page of the Event Console window.

Related Events list

The Related Events list displays the consolidation start event and the repeated events for the consolidation event selected in the Event Console window (Monitor Events or Severe Events page). The items displayed in the Related Events list are the same as the items displayed in the Event Console window when suppression of monitoring of repeated events or consolidated display of repeated events is enabled. However, nothing is displayed in the Summary Status column. The user can change the status of the repeated events in the same way as in the Event Console window.

Note that the Related Events list only shows the 100 oldest repeated events.

If the Related Events (Summary) window has been opened from the Severe Events page, the user can delete the consolidation start event and the repeated events for the consolidation event.

Information is displayed in the Related Events list as follows:

If the event status is changed, the corresponding status icon is displayed in the leftmost column.

If selected repeated events are deleted, they are not displayed in the Related Events list.

The Coloring settings in the Preferences window are not applied to the Related Events list. The background colors defined for severity levels (Emergency, Alert, Critical, Error, and Warning) are not added.

If the display items in the Preferences window are changed, the items displayed in the Related Events list are also changed.

The user can refresh the information displayed in the Related Events (Summary) window by closing and re-opening the window.

The user can change the consolidation event displayed in the Display Items area by selecting a new consolidation event in the Event Console window, choosing View from the menu bar, and then choosing Display Related Event List.

If the status of an event displayed in the Related Events (Summary) window is changed in another window, the change is not applied to the Related Events (Summary) window. The user can display the latest information by closing and re-opening the Related Events (Summary) window.

When the consolidation start event or repeated events cannot be displayed

The following dummy events (events that are not registered in the event database) are displayed dimmed:

Dummy event for the message KAVB0352-E (when the consolidation start event or repeated events cannot be acquired because of an exception occurring in JP1/IM - Manager or JP1/Base)

Dummy event for the message KAVB0341-W (when the event database does not contain the consolidation start event or repeated events)

Dummy event for the message KAVB0342-W (when the consolidation start event or repeated events are blocked by the event receiver filters)

Related information

Information about the consolidation start event and repeated events displayed in the Related Events (Summary) window is displayed after this label. In the Related Events (Summary) window, Repeated events is displayed.

Number of displayed events

The total number of the consolidation start event and repeated events is displayed after this label.

{0}/{1} events acquired

The progress of acquiring the consolidation start event and repeated events is displayed. {0} indicates the number of acquired events (including the consolidation start event), and {1} indicates the total number of the consolidation start event and repeated events. The value {0} is incremented each time an event is added to the Related Events list.

If the acquisition of the consolidation start event and repeated events stops because of an error, the following message is displayed:

Acquisition of related events stopped.

Events that cannot be displayed:

If 101 or more repeated events have been consolidated, the 101st and subsequent repeated events cannot be displayed in the Related Events list. For the repeated events that cannot be displayed, the arrival time of the 101st event and the arrival time of the last event are displayed. If 100 or fewer repeated events have been consolidated, all of the events are displayed in the Related Events list, and the Events that cannot be displayed area does not appear.

To view repeated events after the 100th repeated event, use a time as a search condition to search for repeated events that arrived within the two times displayed in the Events that cannot be displayed area.

For details about event searches, see 6.8 Searching for JP1 events in the JP1/Integrated Management 3 - Manager Administration Guide.

arrival-time-1

The time that the 101st repeated event arrived. The value is displayed in MM/DD hh:mm:ss format.

arrival-time-2

The time that the last repeated event arrived. The value is displayed in MM/DD hh:mm:ss format.

3.9 Related Events (Correlation) window

The Related Events (Correlation) window lists the correlation source events for a correlation event when the correlation event generation function is used.

The Related Events (Correlation) window opens in the following cases:

When the user selects a correlation event in the Event Console window (Monitor Events, Severe Events, or Search Events page), chooses View from the menu bar, and then chooses Display Related Event List

When the user right-clicks a correlation event in the Event Console window (Monitor Events, Severe Events, or Search Events page), and selects Display Related Event List from the pop-up menu

When the user uses the following procedure:

In the Event Console window (Monitor Events, Severe Events, or Search Events page), the user selects a correlation event into which some events have been consolidated.

From the View menu, the user chooses Display Related Event List to display the Related Events (Summary) window.

In the Related Events (Summary) window, the user right-clicks a correlation event and selects Display Related Event List from the pop-up menu.

The following figure shows an example of the Related Events (Correlation) window.

Figure 3‒19: Related Events (Correlation) window

Note

Some of the items displayed in the Related Events (Correlation) window change if linkage with BJEX or JP1/AS is enabled. For information about the contents of the Related Events (Correlation) window when linkage with BJEX or JP1/AS is enabled, see 3.44.5 Related Events windows.

The following describes the items displayed in the Related Events (Correlation) window:

Display Items

This area displays the correlation event selected in the Event Console window (Monitor Events, Severe Events, or Search Events page) or in the Related Events (Summary) window. The items displayed in the Display Items area are the same as the items displayed in the Event Console window. If the display items in the Preferences window are changed, the items displayed in the Display Items area are also changed.

For the correlation event displayed in the Display Items area, as in the Event Console window, the user can display detailed information or change the status. If the event status is changed, the corresponding status icon is displayed in the leftmost column.

If the correlation event displayed in the Display Items area was selected on the Search Events page, the event might exist on a host different from the host on which the user has logged in with JP1/IM - View. If the displayed correlation event exists on a different host, the user cannot perform the following operation:

Changing the event status

Registering incidents in JP1/Service Support

To change the event status to Delete, the user must open the Related Events (Correlation) window from the Severe Events page, and check the information displayed after the Display window label to confirm that either of the following is displayed:

Severe Events

Severe Events - Related Events (Summary)

When the correlation event is deleted, the background color changes to gray.

Information is displayed in the Display Items area as follows:

The Coloring settings in the Preferences window are not applied to the Display Items area. The background colors defined for severity levels (Emergency, Alert, Critical, Error, and Warning) are not added.

If the display items in the Preferences window are changed, the items displayed in the Related Events list are also changed.

Display window

The name of the page from which the Related Events (Correlation) window was opened is displayed in the following format:

Display window: page-name

The following table lists the page names that can be displayed after Display window.

Table 3‒11: Page names that can be displayed after "Display window"

No.

Page name

Description

1

Monitor Events

Displayed when the Related Events (Correlation) window is opened from the Monitor Events page of the Event Console window.

2

Severe Events

Displayed when the Related Events (Correlation) window is opened from the Severe Events page of the Event Console window.

3

Search Events

Displayed when the Related Events (Correlation) window is opened from the Search Events page of the Event Console window.

4

page-name - Related Events (Summary)

Displayed when the Related Events (Correlation) window is opened from the Related Events list after the Related Events (Summary) window has been opened from a correlation event into which events are consolidated in the Event Console window.

In page-name, either Monitor Events or Severe Events is displayed.

Related Events list

The Related Events list displays the correlation source events for the correlation event displayed in the Display Items area. The items displayed in the Related Events list are the same as the items displayed in the Event Console window. If the display items in the Preferences window are changed, the items displayed in the Related Events list are also changed.

For the correlation source events displayed in the Related Events list, as in the Event Console window, the user can display detailed information or change the status. If the event status is changed, the corresponding status icon is displayed in the leftmost column.

If the host that issued the correlation event is different from the host on which the user has logged in with JP1/IM - View, the correlation source events are acquired from the host that issued the correlation event.

If the correlation event displayed in the Display Items area was selected on the Search Events page, the event might exist on a host different from the host on which the user has logged in with JP1/IM - View. If the displayed correlation event exists on a different host, the user cannot perform the following operation on the correlation source events displayed in the Related Events list:

Changing the event status

Registering incidents in JP1/Service Support

To change the event status to Delete, the user must open the Related Events (Correlation) window from the Severe Events page, and check the information displayed after the Display window: label to confirm that either of the following is displayed:

Severe Events

Severe Events - Related Events (Summary)

When the correlation source events are deleted, their background color changes to gray.

Information is displayed in the Display Items area as follows:

The Coloring settings in the Preferences window are not applied to the Display Items area. The background colors defined for severity levels (Emergency, Alert, Critical, Error, and Warning) are not added.

If the display items in the Preferences window are changed, the items displayed in the Related Events list are also changed.

A change in the status of the correlation event displayed in the Display Items area is not applied to any correlation source event displayed in the Related Events list. Likewise, a change in the status of a correlation source event displayed in the Related Events list is not applied to the correlation event displayed in the Display Items area. This is because a correlation event and its correlation source events indicate different phenomena.

The user can change the correlation event displayed in the Display Items area by selecting a new correlation event in the Event Console window, choosing View from the menu bar, and then choosing Display Related Event List.

In the Related Events (Correlation) window opened from the Related Events (Summary) window, if a consolidation event displayed in the Related Events (Summary) window is changed, the Related Events (Correlation) window closes automatically.

If the status of an event displayed in the Related Events (Correlation) window is changed in another window, the change is not applied to the Related Events (Correlation) window. The user can display the latest information by closing and re-opening the Related Events (Correlation) window.

When correlation source events cannot be displayed in the Related Events list

The following dummy events are displayed:

Dummy event for the message KAVB0352-E

This message appears when the correlation source events cannot be acquired because of an exception occurring in JP1/IM - Manager or JP1/Base

Dummy event for the message KAVB0341-W

This message appears when the event database does not contain the correlation source events.

Dummy event for the message KAVB0342-W

This message appears when the correlation source events are blocked by the event receiver filters.

Related information

Information about the correlation source events displayed in the Related Events (Correlation) window is displayed after this label. In Related Events (Correlation) window, Correlation source event (generation-condition-name) is displayed.

Number of displayed events

The total number of correlation source events is displayed after this label.

{0}/{1} events acquired

The progress of acquiring the correlation source events is displayed. {0} indicates the number of acquired events, and {1} indicates the total number of the correlation source events. The value {0} is incremented each time an event is added to the Related Events list.

If acquisition of correlation source events stops because of an error, the following message is displayed:

Acquisition of related events stopped.

3.10 Severe Event Definitions window

The Severe Event Definitions window is used to define which JP1 events are severe events. That is, it is used to specify severe event filter settings. To define severe events, the user must have JP1_Console_Admin permission. If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The Severe Event Definitions window is displayed when the user chooses Options from the menu bar of the Event Console window and then Severe Event Definitions.

When the user sets filter conditions and clicks the OK button in this window, the filter conditions are converted into a filter condition statement and the statement takes effect immediately. The maximum length of the statement is 64 KB. If the filter condition statement is longer than the maximum length, an error dialog box displaying the message KAVB0246-E appears when the OK button is clicked. If the error dialog box appears, the filter condition settings must be reviewed. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

If no conditions (items under Conditions) have been specified for one or more of the pass-conditions groups set in this window, all JP1 events will be displayed (acquired). On the other hand, if no conditions (items under Conditions) have been specified for one or more of the exclusion-conditions groups set in this window, no JP1 events will be displayed (acquired). At least one condition must be specified for each condition group in order to filter events.

When the integrated monitoring database is used, if the user changes the definition of severe events, an event reporting the changes made to the definition of severe events (3F15) is issued.

The following figure shows an example of the Severe Event Definitions window.

Figure 3‒20: Severe Event Definitions window

Note

Some of the items displayed in the Severe Event Definitions window change if linkage with BJEX or JP1/AS is enabled. For information about the contents of the Severe Event Definitions window when linkage with BJEX or JP1/AS is enabled, see 3.44.8 Filter condition definition windows.

The following describes the items displayed in the Severe Event Definitions window.

The user can set a condition by selecting a check box and specifying a value.

Show List (or Hide List)

Clicking the Show List button displays the list of condition groups. When the list is displayed, the button changes to the Hide List button, which, if clicked, hides the list.

Pass-conditions groups

This area displays the pass-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of 30 condition groups can be set. When 30 condition groups have been specified, the Add and Copy buttons are disabled.

Exclusion-conditions groups

This area displays the exclusion-conditions groups. If the user selects a condition group from the list, the name of the selected condition group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of 30 condition groups can be set. When 30 condition groups have been specified, the Add and Copy buttons are disabled.

Add

Clicking this button adds a new condition group. For pass-conditions groups, the default name Condition group n (n is a number) is assigned to the new pass-condition group that is added. For exclusion-conditions groups, the default name Exclusion-condition group n (n is a number) is assigned to the new exclusion-conditions group that is added. Each time a new condition group is added, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Copy

Clicking this button copies the selected condition group. When the user selects a condition group and clicks this button, a new condition group in which the same conditions as those defined in the selected condition group is created. The new condition group that is created is assigned the default name Copy original-condition-group-name, and is added to the list of condition groups. After creating a copy of a condition group, if the user creates another copy of the same condition group, a number is added after the string Copy in CopyN original-condition-group-name (N is a number). The first number used is 2, which is incremented each time the same condition group is copied. Note that, each time a new condition group is added to the list, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Delete

Clicking this button deletes the selected condition group. When this button is clicked, a message dialog box displaying the following message appears:

KAVB0257-I Are you sure you want to delete this condition group?

Clicking the Yes button in the message dialog box deletes the selected condition group.

Condition group name

This box is used to specify the name of a condition group. Specify a character string of 1 to 50 bytes.

If the user selects an existing condition group in the Pass-conditions groups or Exclusion-conditions groups area and specifies a new name, the condition group is renamed. The same name cannot be specified for a pass-conditions group and an exclusion-conditions group.

If the user attempts to specify a condition group name that already appears in the Pass-conditions groups or Exclusion-conditions groups area, a message dialog box displaying the following message appears:

KAVB0256-E The specified condition group name already exists.

Clear

Clicking this button clears all condition settings displayed under Conditions.

Read From Selected Event

Clicking this button applies the attribute values of the JP1 event selected in the Event Console window to the corresponding items under Conditions. The following describes how the attribute values are applied:

When an event attribute value includes a control character (such as a linefeed or tab character)

The part before the first control character is applied. If an option condition can be specified for the event attribute, First characters is selected.

When an event attribute value does not include a control character

The entire event attribute value is applied. If an option condition can be specified for the event attribute, Match is selected.

If the information of the selected JP1 event is mapped in the Event-Information Mapping Definitions window, the attribute values for the display items and program-specific extended attribute values that have been mapped are not applied. For details about the Event-Information Mapping Definitions window, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Event source host name

The Event source host name field appears when the event source host mapping function is enabled.

This field specifies the name of the host where the event that triggered the JP1 event occurred. How to specify multiple hosts is the same as the Source host field.

Alphabetic characters are case sensitive. However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (unless Regular expression is selected in the drop-down list on the right).

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If the integrated monitoring database and the IM Configuration Management database are enabled, you can specify a business group name in path format as an event source host name. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

For details on the event source host mapping function, see 4.9 Mapping of the event source hosts in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Source host

Specifies the name of a host (event server name) that issues a JP1 event. Multiple host names require a comma as a separator. A maximum of 100 host names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive. However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (if Regular expression is not selected in the drop-down list on the right).

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

For Source host, if the integrated monitoring database and the IM Configuration Management database are enabled, a business group name can also be specified in path format. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match and is not Does not match, a business group name specified in path format is treated as a host name.

Event level

Specifies the severity levels of the JP1 events to be defined as severe events from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

Object type

Specifies the object type of a JP1 event. The character string can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Object name

Specifies the object name of a JP1 event. Multiple object names require a comma as a separator. A maximum of 100 object names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object type

Specifies the root object type of a JP1 event. The root object type can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object name

Specifies the root object name of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Occurrence

Specifies the occurrence type of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

User name

Specifies the user name of a JP1 event.

Multiple user names require a comma as a separator. A maximum of 100 user names can be specified. If a user name that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Message

Specifies the message text of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression. We recommend First characters or Is contained. If Regular expression is selected, make sure that control characters used in the message text are not included in the expression.

Product name

Specifies the name of the program that issues a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID

Specifies the event ID of a JP1 event. Multiple event IDs require a comma as a separator.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match and Does not match.

Action

Specifies filtering based on whether the automated action defined for the JP1 event has been executed.

Extended attribute

Displays the window for setting the condition that determines whether to use the program-specific extended attribute value to perform filtering. To set the condition, select the Extended attribute check box. If you select this check box, the Configure button becomes available. If you click the Configure button, the Event Search Conditions (Program-Specific Information in Extended Attribute) window is displayed, and you can set the condition.

For details about this window, see 3.26 Event Search Conditions (Program-Specific Information in Extended Attribute) window.

3.11 System Environment Settings window

The System Environment Settings window is used to specify the basic JP1/IM optional settings, such as the event filter conditions and buffer size.

To display the System Environment Settings window, the user must have JP1_Console_Admin permission.

If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The System Environment Settings window is displayed when the user chooses Options and then System Environment Settings. The System Environment Settings window has three pages: General, Communication, and Display. The user displays each page by choosing the corresponding tab.

For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

3.11.1 General page

The following figure shows an example of the General page of the System Environment Settings window.

Figure 3‒21: General page of System Environment Settings window (basic mode) in version 10-50 and later

Figure 3‒22: General page of System Environment Settings window (basic mode) in version 10-10 and earlier

The following describes the items displayed on the General page of the System Environment Settings window.

Editing list

Clicking this button displays the Event Acquisition Conditions List window, which can be used to edit an event acquisition filter.

If the event acquisition filter is operating in Compatible mode, this button is disabled.

A filter is being applied

The currently used event acquisition filter is displayed in the box.

The drop-down list can be used to change the event acquisition filter. If the user selects an event acquisition filter from the drop-down list and then clicks Apply, the event acquisition conditions of the selected filter will be used.

If the current event acquisition filter is operating in Compatible mode, the drop-down list is disabled and Existing filter condition is displayed.

Configure

Clicking this button displays a window for setting or changing the event acquisition filter conditions (the conditions for acquiring events from the event service).

When the user selects an event acquisition filter from the drop-down list under A filter is being applied and clicks the Configure button, the Event acquisition conditions window or the Event Acquisition Settings (for compatibility) window appears.

The Event Acquisition Settings (for compatibility) window appears when the event acquisition filter is operating in Compatible mode.

Common exclusion-conditions groups

A list of common exclusion-conditions groups is displayed in basic or extended mode.

Double-clicking an item selected in the list displays either the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window. The displayed window can be used to edit the selected item.

The differences between basic mode and extended mode are the number of conditions groups that can be set and the number of columns displayed in the list. For details about how to set common exclusion-conditions, see 5.2.4(3) Setting common exclusion-conditions in the JP1/Integrated Management 3 - Manager Configuration Guide.

Basic mode:

A maximum of 30 condition groups can be set.

The displayed columns are Apply and Conditions group name.

Extended mode (if the version of JP1/IM - Manager is 10-00 or later):

The maximum number of conditions groups depends on the version of JP1/IM - Manager. The maximum number is 1,024 when the version of JP1/IM - Manager is from 10-00 to 11-10, or 2,500 when the version of JP1/IM - Manager is 11-50 or later.

The displayed columns are Apply, ID, Conditions group name, and Comment as shown in the following figure.

Figure 3‒23: General page of System Environment Settings window (extended mode) in version 10-50 and later

The Display page appears in versions 10-50 and later of JP1/IM - Manager.

Figure 3‒24: General page of System Environment Settings window (extended mode) in versions 10-00 and 10-10

Extended mode (if the version of JP1/IM - Manager is 09-50 or earlier):

A maximum of 1,024 condition groups can be set.

The displayed columns are Apply, Type, ID, Conditions group name, and Comment.

Figure 3‒25: General page of System Environment Settings window (extended mode) in version 09-50 and earlier

The items in a column can be sorted.

If the user clicks a column header once, the Δ icon is displayed in the column header. If the user clicks the column header again, the icon is displayed. If the user clicks the column header a third time, no icon is displayed. If the Δ icon or the icon is displayed, and the user clicks another column header, the current sorting is canceled and the list is sorted on the other column.

If neither the Δ icon nor the icon is displayed, the items are sorted in the order they were registered.

If the Δ icon is displayed, the items are sorted by name in the ascending order.

If the icon is displayed, the items are sorted by name in the discending order.

Apply

If the check box in this column is selected for an item (common exclusion-conditions group in basic mode, common exclusion-conditions group in extended mode, or additional common exclusion-conditions group in extended mode), the item is applied.

Type

No icon is displayed for a common exclusion-condition that prevents an event from being collected. The icon is displayed for an additional common exclusion-condition that prevents an event from being collected.

The icon is displayed for a common exclusion-condition that excludes a collected event from action execution. The icons and are displayed for an additional common exclusion-condition that excludes a collected event from action execution.

ID

The IDs of common exclusion-conditions groups in extended mode are displayed.

Condition group name

The condition group names of common exclusion-conditions groups in basic mode, common exclusion-conditions groups in extended mode, and additional common exclusion-conditions groups in extended mode are displayed.

The user can change condition group names in the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window.

Comment

The comments on common exclusion-conditions groups in extended mode and additional common exclusion-conditions groups in extended mode are displayed.

Configure

Clicking this button displays the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window. The displayed window can be used to edit the conditions for the selected common exclusion-conditions group in basic or extended mode.

Event buffer

Specifies how many events extracted from the event service can be stored in a JP1/IM - Manager buffer. The range of specifiable values is from 10 to 2,000. The default is 2,000.

If the specified value is too small, the Event Console window might not be able to display all events.

If the specified value is too large when JP1/IM - View is started, the Event Console window might take longer to appear.

Before setting the event buffer, the user must estimate the amount of required memory for Central Console, and must check the amount of free space on the machine resource. For details about the formula for estimating the amount of required memory, see the Release Notes for JP1/IM - View.

Apply

Clicking this button applies the settings.

When the version of JP1/IM - Manager is 11-10-01 or later, JP1/IM - Manager checks whether any environment-dependent character is included in common exclusion-conditions groups (extended) or additional common exclusion-conditions. If such a character is found, the settings are not applied.

3.11.2 Communication page

The following figure shows an example of the Communication page of the System Environment Settings window.

Figure 3‒26: System Environment Settings window (Communication page)

The following describes the items displayed on the Communication page of the System Environment Settings window.

Num. of retries

Specifies the number of times JP1/IM - View automatically retries connection when JP1/IM - View fails to connect to the event service or JP1/IM - View is disconnected from the event service. The range of specifiable values is from 0 to 100. The default is 3.

Interval

Specifies in milliseconds the interval at which JP1/IM - View automatically retries connection when JP1/IM - View fails to connect to the event service or JP1/IM - View is disconnected from the event service. The range of specifiable value is from 1 to 86,400,000. The default is 10,000.

jcochstat command

Specifies whether to allow the user to use the jcochstat command.

The jcochstat command can be used to change the event status. However, if it is inconvenient to have the user change the event status, the administrator can prevent the user from using this command.

If the Permit status change check box is selected, the user can use the jcochstat command.

3.11.3 Display page

The following figure shows an example of the Display page of the System Environment Settings window.

Figure 3‒27: Display page of System Environment Settings window

The following describes the items displayed on the Display page of the System Environment Settings window.

Range of events to be collected at login

Set whether to use the event collection range setting function in the Event Monitoring and Severe Events pages.

Enable the Monitor Events page check box

Select the Enable the Monitor Events page check box to use the event collection range setting function in the Event Monitoring page. The check box is cleared by default.

When you select this check box, the day(s) and hours radio buttons become available. The day(s) radio button is selected by default.

Enable the Severe Events page check box

Select the Enable the Severe Events page check box to use the event collection range setting function in the Severe Events page. The check box is cleared by default.

When you select this check box, the day(s) and hours radio buttons and the Enable check box for Do not collect Processed events become available. The day(s) radio button is selected by default. The Enable check box for Do not collect Processed events is selected by default.

day(s) radio button

When you select this radio button, the day(s) text box and Base time text box become available.

day(s) text box

Specify how many days of events to collect at login. You can specify a value from 1 to 31. The default is 1.

Base time text box

Specify the start time of the days specified in the day(s) text box. You can specify a value from 0:00 to 23:59. The default is 9:00.

hours radio button

When you select this radio button, the hours text box becomes available.

hours text box

Specify how many hours of events to collect at login. You can specify a value from 1 to 744. The default is 1.

Do not collect Processed events

To prevent the Severe Events page from acquiring processed events at login, select the Enable check box in this area.

3.12 Event Acquisition Settings window

The Event Acquisition Settings window is used to set the event acquisition filter conditions (the conditions for acquiring events from the event service).

Any of the following operations displays the Event Acquisition Settings window:

In the System Environment Settings window, the user uses the Event acquisition conditions drop-down list to select an event acquisition filter, and then clicks the Configure button.

In the Event Acquisition Conditions List window, the user selects a filter in the list, and then clicks the Edit button.

In the Event Acquisition Conditions List window, the user clicks Add.

In the Event Acquisition Conditions List window, the user selects and double-clicks a filter in the list.

Note that a user must have JP1_Console_Admin permission to display the Event Acquisition Settings window. If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When the user sets filter conditions and clicks the OK button in this window, the filter conditions are converted into a filter condition statement. The statement takes effect when Apply is clicked in the System Environment Settings window. The maximum length of the event acquisition filter is 64 KB when exclusion-conditions groups have been set. When they have not been set, the maximum length is 60 KB. If the event acquisition filter is longer than the maximum length, an error dialog box displaying the message KAVB0246-E appears when the OK button is clicked. If the error dialog box appears, the filter condition settings must be reviewed. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

If no conditions (items under Conditions) have been specified for one or more of the pass-conditions groups set in this window, all JP1 events will be displayed (acquired). On the other hand, if no conditions (items under Conditions) have been specified for one or more of the exclusion-conditions groups set in this window, no JP1 events will be displayed (acquired). At least one condition must be specified for each condition group in order to filter events.

If JP1/IM - Manager on the connected host uses an event acquisition filter in Compatible mode, the Event Acquisition Settings (for compatibility) window appears instead of the Event Acquisition Settings window.

For acquiring events for which specific severity level has been defined and JP1/SES events

For the Event Acquisition Settings (for compatibility) window, a filter for acquiring the following types of events can be created at one time, for the Event Acquisition Settings window, multiple condition groups are needed:

To acquire both Error-level events and JP1/SES events, the user sets condition groups as follows:

To acquire Error-level events, the user creates Condition group 1, and then in the Event level area, selects the Specify the severity radio button and the Error check box.

To acquire JP1/SES events, the user creates Condition group 2, and then in the Event level area, selects the JP1/SES events radio button.

The following figure shows an example of the Event Acquisition Settings window.

Figure 3‒28: Event Acquisition Settings window

The following describes the items displayed in the Event Acquisition Settings window.

Filter name

If an event acquisition filter is being added, the user enters the name of the filter in this text box.

Any characters other than control characters can be used. A character string from 1 to 50 bytes can be specified.

If an event acquisition filter is being edited, the name of the filter selected from the list of filters is displayed. If the user renames the event acquisition filter, the new name is displayed. Note that a new filter is not created with the new name.

The same filter name cannot be assigned to multiple filters.

Space characters before and after a filter name are recognized as part of the name. Therefore, filter names that either begin or end with a space, that neither begin nor end with a space, and that both begin and end with a space are different despite identical filter names.

Filter ID

The user selects the filter ID of an event acquisition filter from the drop-down list.

If a new event acquisition filter is being added, an unused filter ID in the event acquisition filter list is automatically assigned in ascending order.

If an event acquisition filter is being edited, the filter ID selected from the list of filters is displayed in the text box. If the user changes the ID of the event acquisition filter, the new ID is displayed. Note, however, that a new filter has not been created with the new ID.

The same filter ID cannot be assigned to multiple filters.

Show List (or Hide List)

Clicking the Show List button displays the list of condition groups. When the list is displayed, the button changes to the Hide List button, which, if clicked, hides the list.

Pass-conditions groups

This area displays the pass-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of 30 condition groups can be set. When 30 condition groups have been specified, the Add and Copy buttons are disabled.

Exclusion-conditions groups

This area displays the exclusion-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of 30 condition groups can be set. When 30 condition groups have been specified, the Add and Copy buttons are disabled.

Add

Clicking this button adds a new condition group. For pass-conditions groups, the default name Condition group n (n is a number) is assigned to the new pass-conditions group that is added. For exclusion-conditions groups, the default name Exclusion-condition group n (n is a number) is assigned to the new exclusion-conditions group that is added. Each time a new condition group is added, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Copy

Clicking this button copies the selected condition group. When the user selects a condition group and clicks this button, a new condition group in which the same conditions as those defined in the selected condition group is created. The new condition group that is created is assigned the default name Copy original-condition-group-name, and is added to the list of condition groups. After creating a copy of a condition group, if the user creates another copy of the same condition group, a number is added after the string Copy in CopyN original-condition-group-name (N is a number). The first number used is 2, which is incremented each time the same condition group is copied. Note that, each time a new condition group is added to the list, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Delete

Clicking this button deletes the selected condition group. When this button is clicked, a message dialog box displaying the following message appears:

KAVB0257-I

Clicking the Yes button in the message dialog box deletes the selected condition group.

Condition group name

This box is used to specify the name of a condition group. Any characters other than control characters can be used. A character string from 1 to 50 bytes can be specified.

If the user selects a condition group that already appears in the Pass-conditions groups or Exclusion-conditions group area and specifies a new name, the condition group is renamed. The same name cannot be specified for a pass-conditions group and an exclusion-conditions group.

If the user attempts to specify a condition group name that already appears in the Pass-conditions groups or Exclusion-conditions group area, a dialog box displaying the following message appears:

KAVB0256-E The specified condition group name already exists.

Clear

Clicking this button clears all condition settings displayed under Conditions.

Read From Selected Event

Clicking this button applies the attribute values of the JP1 event selected in the Event Console window to the corresponding items under Conditions. The following describes how the attribute values are applied:

When an event attribute value includes a control character (such as a linefeed or tab character)

The part before the first control character is applied. If an option condition can be specified for the event attribute, First characters is selected.

When an event attribute value does not include a control character

The entire event attribute value is applied. If an option condition can be specified for the event attribute, Match is selected.

If the information of the selected JP1 event is mapped in the Event-Information Mapping Definitions window, the attribute values for the display items and program-specific extended attribute values that have been mapped are not applied. For details about the Event-Information Mapping Definitions window, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Source host

Specifies the name of a host (event server name) that issues a JP1 event. No business groups can be specified. Multiple host names require a comma as a separator. A maximum of 100 host names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive regardless of the -ignorecasehost option specification of the jcoimdef command.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event level

Specifies the severity levels of the JP1 events to be acquired.

The user can acquire all events for which a severity level has been defined by selecting the All events for which severity has been defined radio button.

If the user wants to acquire only events for specific severity levels, the user can select the Specify the severity radio button and then select the check boxes for the desired severity levels from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

If the user wants to acquire JP1/SES events, the user can select the Acquire the JP1/SES events radio button.

Note that if the user enables the function for changing the severity level when the integrated monitoring database is used, the column header is displayed as Original severity level.

Object type

Specifies the object type of a JP1 event. The character string can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Object name

Specifies the object name of a JP1 event. Multiple object names require a comma as a separator. A maximum of 100 object names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object type

Specifies the root object type of a JP1 event. The root object type can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object name

Specifies the root object name of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Occurrence

Specifies the occurrence type of a JP1 event.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

User name

Specifies the user name of a JP1 event.

Multiple user names require a comma as a separator. A maximum of 100 user names can be specified. If a user name that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Message

Specifies the message text of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression. We recommend First characters or Is contained. If Regular expression is selected, make sure that control characters used in the message text are not included in the expression.

Product name

Specifies the name of the program that issues a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID

Specifies the event ID of a JP1 event. Multiple event IDs require a comma as a separator.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match and Does not match.

Extended attribute

Displays the window for setting the condition whether to use the program-specific extended attribute value to perform filtering. To set the condition, select the Extended attribute check box. If you select this check box, the Configure button becomes available. If you click the Configure button, the Event Search Conditions (Program-Specific Information in Extended Attribute) window is displayed, and you can set the condition.

For details about this window, see 3.26 Event Search Conditions (Program-Specific Information in Extended Attribute) window.

3.13 Event Acquisition Settings (for compatibility) window

The Event Acquisition Settings (for compatibility) window is displayed when the event acquisition filter is used in Compatible mode and the user clicks the Configure button in the Event acquisition conditions area of the System Environment Settings window.

The Event Acquisition Settings (for compatibility) window is used to set the filter conditions for acquiring events from the event service. The following figure shows an example of the Event Acquisition Settings (for compatibility) window.

Figure 3‒29: Event Acquisition Settings (for compatibility) window

The following describes the items displayed in the Event Acquisition Settings (for compatibility) window.

JP1/SES events

Specifies whether to acquire JP1/SES events. When the Acquire check box is selected, JP1/SES events are acquired.

Event level

Specifies the severity levels of the JP1 events to be acquired from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

When the Event level check box is not selected, all events for which a severity level has been defined are acquired.

Event ID

Specifies the event ID of a JP1 event. Multiple event IDs require a comma as a separator.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match and Does not match.

Note that the condition settings specified in this window are passed to the event service as a statement defining either of the following conditions:

(JP1/SES events) AND (events with the specified event IDs)

(Events of the specified severity levels) AND (events with the specified event IDs)

3.14 Event Acquisition Conditions List window

The Event Acquisition Conditions List window lists event acquisition filters. This window can be used to add, edit, copy, or delete an event acquisition filter.

This window is displayed when the user clicks the Editing list button in the System Environment Settings window.

The new settings specified in the Event Acquisition Conditions List window are saved when the user clicks the OK button in the Event Acquisition Conditions List window, and then clicks the Apply button in the System Environment Settings window.

If the Apply button is not clicked in the System Environment Settings window, the new settings are abandoned.

For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

The following figure shows an example of the Event Acquisition Conditions List window.

Figure 3‒30: Event Acquisition Conditions List window (basic mode)

The following describes the items displayed in the Event Acquisition Conditions List window.

A filter is being applied

The ID and name of the event acquisition filter that is currently being applied are displayed.

Filter list

This area displays a list of event acquisition filters that have been created.

When the user selects and double-clicks an item in the list, the Event Acquisition Settings window opens so that the selected filter can be edited. The user can select only one item.

A maximum of 50 event acquisition filters can be registered in the filter list.

The user can sort the filter list by selection status (Apply column), by filter ID (ID column), or by filter name (Filter name column). Sorting is performed by clicking the corresponding column header. If the user clicks a column header once, the Δ icon is displayed in the column header. If the user clicks the column header again, the icon is displayed. If the user clicks the column header a third time, no icon is displayed. If the Δ icon or the icon is displayed, and the user clicks another column header, the current sorting is canceled and the list is sorted on the other column.

The sort order of the filter list is indicated by an icon displayed in the header of the column on which the list was sorted:

No icon: The event acquisition filters are sorted in the order they were added to the list.

Δ: The event acquisition filters are sorted in ascending order.

: The event acquisition filters are sorted in descending order.

Apply

The event acquisition filter whose radio button in the Apply column is selected is the filter that is currently applied.

ID

The IDs of event acquisition filters are displayed in this column. The user can change the ID of an event acquisition filter by using the Event Acquisition Settings window.

Filter name

The names of event acquisition filters are displayed in this column. The user can change the name of an event acquisition filter by using the Event Acquisition Settings window.

Add

Clicking this button allows the user to add a new event acquisition filter. When this button is clicked, the Event Acquisition Settings window opens, where the user can set a new event acquisition filter. A maximum of 50 event acquisition filters can be created. When 50 event acquisition filters have been registered in the list, the Add button is disabled.

Edit

Clicking this button allows the user to edit the selected event acquisition filter. When the user selects an event acquisition filter and then clicks the Edit button, the Event Acquisition Settings window opens, where the user can edit the settings of the selected filter. This button is available when at least one event acquisition filter is selected in the Filter list area.

Copy

Clicking this button copies the selected event acquisition filter. When the user selects an event acquisition filter and then clicks the Copy button, a new event acquisition filter in which the same conditions as those defined in the selected filter is created and added to the list in the Filter list area.

When a new event acquisition filter is copied, an unused filter ID in the event acquisition filter list is automatically assigned in ascending order.

The new event acquisition filter that is created is assigned the default name Copy original-filter-name, and added to the list. After creating a copy of an event acquisition filter, if the user creates another copy of the same event acquisition filter, a number is added after the string Copy in CopyN original-filter-name format (N is a number). The first number used is 2, which is incremented each time the same event acquisition filter is copied.

When the Copy button is clicked, the new filter that has been created is selected as the filter that is currently applied.

When 50 event acquisition filters have been registered in the list, the Copy button is disabled.

Delete

Clicking this button deletes the selected event acquisition filter.

If this button is clicked when only one event acquisition filter has been selected, a dialog box displays the KAVB0250-I message.

If this button is clicked when multiple event acquisition filters have been selected, a dialog box displays the KAVB1149-Q message.

Clicking the Yes button in this dialog box deletes the selected event acquisition filter from the list in the Filter list area.

Common exclusion-conditions groups

A list of common exclusion-conditions groups is displayed in basic or extended mode.

Double-clicking an item selected in the list displays either the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window. The displayed window can be used to edit the selected item.

The differences between basic mode and extended mode are the number of conditions groups that can be set and the number of columns displayed in the list. For details about how to switch from basic mode to extended mode, see 5.2.4(3) Setting common exclusion-conditions in the JP1/Integrated Management 3 - Manager Configuration Guide.

Basic mode:

A maximum of 30 condition groups can be set.

The displayed columns are Apply, ID, and Conditions group name.

Extended mode (if the version of JP1/IM - Manager is 10-00 or later):

The maximum number of conditions groups depends on the version of JP1/IM - Manager. The maximum number is 1,024 when the version of JP1/IM - Manager is from 10-00 to 11-10, or 2,500 when the version of JP1/IM - Manager is 11-50 or later.

The displayed columns are Apply, Type, ID, Conditions group name, and Comment as shown in the following figure. The items in a column can be sorted.

Extended mode (if the version of JP1/IM - Manager is earlier than 10-00):

A maximum of 1,024 condition groups can be set.

The displayed columns are Apply, ID, Conditions group name, and Comment as shown in the following figure.

The items in a column can be sorted.

If the user clicks a column header once, the Δ icon is displayed in the column header. If the user clicks the column header again, the icon is displayed. If the user clicks the column header a third time, no icon is displayed. If the Δ icon or the icon is displayed, and the user clicks another column header, the current sorting is canceled and the list is sorted on the other column.

If neither the Δ icon nor the icon is displayed, the items are sorted in the order they were registered.

If the version of JP1/IM - Manager is 10-00 or later, additional common exclusion-conditions groups are displayed below the common exclusion-conditions groups. In each category, exclusion-conditions groups are displayed in the order they were registered. Note that additional common exclusion-conditions groups might not be displayed below the common exclusion-conditions groups if any of the following operations is performed: Adding a common exclusion-conditions group, copying a common exclusion-conditions group (or additional common exclusion-conditions group), and changing the type of an additional common exclusion-conditions group.

If the Δ icon is displayed, the items are sorted by name in ascending order.

If the icon is displayed, the items are sorted by name in discending order.

Apply

If the check box in this column is selected for an item (common exclusion-conditions group in basic mode, common exclusion-conditions group in extended mode, or additional common exclusion-conditions group in extended mode), the item is applied.

Type

No icon is displayed for a common exclusion-condition that prevents an event from being collected. The icon is displayed for an additional common exclusion-condition that prevents an event from being collected.

The icon is displayed for a common exclusion-condition that excludes a collected event from action execution. The icons and are displayed for an additional common exclusion-condition that excludes a collected event from action execution.

ID

The common exclusion-conditions group ID is displayed. The ID of a common exclusion-conditions group can be changed in either the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window. However, the ID of an additional common exclusion-conditions group cannot be changed.

Condition group name

The condition group names of common exclusion-conditions groups in basic mode, common exclusion-conditions groups in extended mode, and additional common exclusion-conditions groups in extended mode are displayed. Condition group names can be changed in either the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window.

Comment

The comments on common exclusion-conditions groups in extended mode and additional common exclusion-conditions groups in extended mode are displayed.

Add

Clicking this button adds a new common exclusion-conditions group. When the Add button is clicked, either the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window is displayed. The displayed window can be used to add a new common exclusion-conditions group in basic or extended mode. However, the displayed window cannot be used to add an additional common exclusion-conditions group.

A maximum of 30 common exclusion-conditions groups can be added. If the number of registered common exclusion-conditions groups reaches 30, the Add button is disabled.

In extended mode, the total maximum number of common exclusion-conditions groups and additional common exclusion-conditions groups is 2,500. If the total number of registered common exclusion-conditions groups and additional common exclusion-conditions groups reaches 2,500, the Add button is disabled.

Edit

Click this button to edit the selected common exclusion-conditions group in basic mode, common exclusion-conditions group in extended mode, or additional common exclusion-conditions group in extended mode.

When the user selects a common exclusion-conditions group (or an additional common exclusion-conditions group) and clicks the Edit button, either the Common Exclusion-Conditions Settings window or the Common Exclusion-Condition Settings (Extended) window is displayed. The displayed window can be used to edit a common exclusion-conditions group in basic mode, common exclusion-conditions group in extended mode, or additional common exclusion-conditions group in extended mode. Note that the ID of an additional common exclusion-conditions group cannot be changed.

Copy

Click this button to copy the selected common exclusion-conditions group in basic mode, common exclusion-conditions group in extended mode, or additional common exclusion-conditions group in extended mode. Note that an exclusion-conditions group created by copying an additional common exclusion-conditions group in extended mode becomes a common exclusion-conditions group in extended mode.

When the user selects a common exclusion-conditions group (or an additional common exclusion-conditions group) and clicks the Copy button, a common exclusion-conditions group that has the same conditions that the selected one is created and is added to the Common exclusion-conditions groups list.

When a new common exclusion-conditions group is copied, an unused ID in the common exclusion-conditions group list is automatically assigned in ascending order.

The new common exclusion-conditions group that is created is assigned the default name Copy original-conditions-group-name. After creating a copy of a common exclusion-conditions group, if the user creates another copy of the same common exclusion-conditions group, a number is added after the string Copy in CopyN original-conditions-group-name (N is a number). The first number used is 2, which is incremented each time the same event acquisition filter is copied.

When the Copy button is clicked, the new common exclusion-conditions group that has been created is selected.

When 30 common exclusion-conditions groups have been registered in the list, the Copy button is disabled.

In extended mode, when 2,500 common exclusion-conditions groups have been registered in the list, the Copy button is disabled.

Delete

Click this button to delete the selected common exclusion-conditions groups in basic mode, common exclusion-conditions groups in extended mode, or additional common exclusion-conditions groups in extended mode.

If this button is clicked when only one common exclusion-conditions group has been selected, a dialog box displays the KAVB0257-I message.

If this button is clicked when multiple common exclusion-conditions groups have been selected, a dialog box displays the KAVB1151-Q message.

Clicking the Yes button in this dialog box deletes the selected common exclusion-conditions groups from the Common exclusion-conditions groups list.

Type

Click this button to change the type of the selected common exclusion-conditions group in extended mode. The type can be changed only from the additional common exclusion-conditions group to the (normal) common exclusion-conditions group.

The type cannot be changed from the (normal) common exclusion-conditions group to the additional common exclusion-conditions group.

When the user clicks this button, a message box asks the user whether to change the type. Clicking the OK button in this message box changes the type of the selected common exclusion-conditions groups (from the additional type to the normal type).

Note that if the type is changed, the ID of the common exclusion-conditions group is changed.

The new ID to be assigned is the largest of the already defined IDs plus 1. If the new ID exceeds the maximum, the smallest available ID is assigned.

If the type is changed from the additional type to the normal type by mistake, the change can be canceled by clicking the Close button in the System Environment Settings window before the Apply button is clicked.

3.15 Common Exclusion-Conditions Settings window

The Common Exclusion-Conditions Settings window is used to set the event acquisition filter conditions (the conditions for acquiring events from the event service). Note that the window to be used to set common exclusion-conditions in extended mode is the Common Exclusion-Condition Settings (Extended) window. For details about this window, see 3.16 Common Exclusion-Condition Settings (Extended) window.

Any of the following operations displays the Common Exclusion-Conditions Settings window:

If no filter conditions are set:

In the Event Acquisition Conditions List window, click the Add button in the Common exclusion-conditions groups area.

If at least one filter is registered:

In the System Environment Settings window, select an item in the Common exclusion-conditions groups list and click the Configure button.

In the Event Acquisition Conditions List window, select an item in the Common exclusion-conditions groups list and click the Edit button.

In the System Environment Settings window, select and double-click an item in the Common exclusion-conditions groups list.

Note that the user must have JP1_Console_Admin permission to display the Common Exclusion-Conditions Settings window. If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When the user specifies common exclusion-conditions and then clicks the OK button in this window, the specified conditions are converted into a filter condition statement. The statement takes effect when the Apply button is clicked in the System Environment Settings window. If the error dialog box appears, the filter condition settings must be reviewed. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

When no conditions (items under Conditions) have been specified for the common exclusion-conditions group set in this window, if the common exclusion-conditions group is applied, no JP1 events will be displayed (acquired). At least one condition must be specified in order to filter events.

The following figure shows an example of the Common Exclusion-Conditions Settings window.

Figure 3‒31: Common Exclusion-Conditions Settings window

The following describes the items displayed in the Common Exclusion-Conditions Settings window.

Common exclusion-conditions group ID

This drop-down list is used to select a common exclusion-conditions group ID. The drop-down list lists IDs from 0 to 29.

If a new common exclusion-condition is being added, an unused filter ID in the common exclusion-condition group list is automatically assigned in ascending order.

If the window has been displayed for the purpose of editing the common exclusion-condition selected in the common exclusion-condition group list, the common exclusion-condition group ID is displayed in this text box.

Common exclusion-conditions group name

Specifies the name of a common exclusion-conditions group. A character string from 1 to 50 bytes can be specified.

If the user selects an existing group in the Common exclusion-conditions groups area and specifies a new name, the common exclusion-conditions group is renamed.

If the user attempts to specify the name of an existing common exclusion-conditions group, the following message appears:

KAVB0256-E The specified condition group name already exists.

Clear

Clicking this button clears all condition settings displayed under Conditions.

Read From Selected Event

Clicking this button applies the attribute values of the JP1 event selected in the Event Console window to the corresponding items under Conditions. The following describes how the attribute values are applied:

When an event attribute value includes a control character (such as a linefeed or tab character)

The part before the first control character is applied. If an option condition can be specified for the event attribute, First characters is selected.

When an event attribute value does not include a control character

The entire event attribute value is applied. If an option condition can be specified for the event attribute, Match is selected.

If the information of the selected JP1 event is mapped in the Event-Information Mapping Definitions window, the attribute values for the display items and program-specific extended attribute values that have been mapped are not applied. For details about the Event-Information Mapping Definitions window, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Source host

Specifies the name of a host (event server name) that issues a JP1 event. Business groups cannot be specified. Multiple host names require a comma as a separator. A maximum of 100 host names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive regardless of the -ignorecasehost option specification of the jcoimdef command.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event level

Specifies the severity levels of the JP1 events to be acquired.

The user can acquire all events for which a severity level has been defined by selecting the All events for which severity has been defined radio button.

If the user wants to acquire only events for specific severity levels, the user can select the Specify the severity radio button and then select the check boxes for the desired severity levels from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

If the user wants to acquire JP1/SES events, the user can select the JP1/SES events radio button.

Note that if the user enables the function for changing the severity level when the integrated monitoring database is used, the column header is displayed as Original severity level.

Object type

Specifies the object type of a JP1 event. The character string can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Object name

Specifies the object name of a JP1 event. Multiple object names require a comma as a separator. A maximum of 100 object names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object type

Specifies the root object type of a JP1 event. The root object type can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object name

Specifies the root object name of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Occurrence

Specifies the occurrence type of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

User name

Specifies the user name of a JP1 event.

Multiple user names require a comma as a separator. A maximum of 100 user names can be specified. If a user name that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Message

Specifies the message text of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression. We recommend First characters or Is contained. If Regular expression is selected, make sure that control characters used in the message text are not included in the expression.

Product name

Specifies the name of the program that issues a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID

Specifies the event ID of a JP1 event. Multiple event IDs require a comma as a separator.

A maximum of 100 event IDs can be specified.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match and Does not match.

Extended attribute

Displays the window for setting the condition whether to use the program-specific extended attribute value to perform filtering. To set the condition, select the Extended attribute check box. If you select this check box, the Configure button becomes available. If you click the Configure button, the Event Search Conditions (Program-Specific Information in Extended Attribute) window is displayed, and you can set the condition.

For details about this window, see 3.26 Event Search Conditions (Program-Specific Information in Extended Attribute) window.

3.16 Common Exclusion-Condition Settings (Extended) window

The Common Exclusion-Condition Settings (Extended) window is displayed when common exclusion-conditions groups are to be manipulated in extended mode. This window is used to set the JP1 event exclusion-conditions and their validity period for an event acquisition filter that is applied to JP1 events received from the event service.

Note that the window displayed when common exclusion-conditions groups are to be manipulated in basic mode is the Common Exclusion-Conditions Settings window. For details about this window, see 3.15 Common Exclusion-Conditions Settings window.

The Common Exclusion-Condition Settings (Extended) window has the Common exclusion-conditions page and the Conditions Apply Period page.

To display this window:

In the System Environment Settings window, select an item in the Common exclusion-conditions groups list, and then click the Configure button.

In the System Environment Settings window, double-click a common exclusion-conditions group in the Common exclusion-conditions groups list.

In the Event Acquisition Conditions List window, click the Add button in the Common exclusion-conditions groups area.

In the Event Acquisition Conditions List window, select an item in the Common exclusion-conditions groups list, and then click the Edit button.

In the Event Acquisition Conditions List window, double-click a common exclusion-conditions group in the Common exclusion-conditions groups list.

In a Related Events window, right-click a single JP1 event and then select Exclude by Common Exclusion-Conditions from the pop-up menu.

In the Event Console window, select a single JP1 event, and from the View menu, select Exclude by Common Exclusion-Conditions. Alternatively, right-click a JP1 event and select Exclude by Common Exclusion-Conditions from the pop-up menu.

Note that displaying the Common Exclusion-Condition Settings (Extended) window requires JP1_Console_Admin permission. If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The information set on the pages of the Common Exclusion-Condition Settings (Extended) window is converted into a filter condition statement when the OK button is clicked#. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

#: The setting takes effect when:

The user clicks the Apply button in the System Environment Settings window

The user clicks the OK button after using the Exclude by Common Exclusion-Conditions menu command to set event exclusion-conditions

When the version of JP1/IM - Manager is 11-10-01 or later, JP1/IM - Manager checks whether any environment-dependent character is included in the definitions. If such a character is found, the settings are not applied.

The following figure shows the Common Exclusion-Condition Settings (Extended) window.

Figure 3‒32: Common Exclusion-Condition Settings (Extended) window

The following describes the items displayed in the Common Exclusion-Condition Settings (Extended) window.

Common exclusion-conditions group ID

This drop-down list can be used to select a common exclusion-conditions group ID in extended mode. The drop-down list lists IDs from 0 to 2499.

The IDs of common exclusion-conditions groups that have not been used in the Common exclusion-conditions groups list are displayed in this drop-down list in ascending order of numeric values.

When the user edits a common exclusion-condition in extended mode, the common exclusion-conditions group ID selected in the Common exclusion-conditions groups list is displayed in this drop-down list. If the Common Exclusion-Condition Settings (Extended) window is opened by choosing Exclude by Common Exclusion-Conditions, a blank is displayed.

This drop-down list is disabled when the Common Exclusion-Condition Settings (Extended) window is opened by choosing Exclude by Common Exclusion-Conditions or opened in order to edit the definition of additional common exclusion-conditions.

Common exclusion-conditions group name

This text box is used to specify the name of a common exclusion-conditions group. Specify a character string of 1 to 50 bytes (when Shift-JIS encoded). All characters other than control characters (0x00 to 0x1F and 0x7F to 0x9F) can be used.

When the Common Exclusion-Condition Settings (Extended) window is opened by clicking the Add button, the system automatically displays Common exclusion-conditions group n in this text box. The number n is the smallest number that has not been used in already defined common exclusion-conditions group names in the range from 1 to the maximum number of condition groups that can be defined.

If an existing common exclusion-conditions group is selected in the Common exclusion-conditions groups area when you change the name in this text box, the existing group is renamed.

If you specify a name of a common exclusion-conditions group that already appears in the Common exclusion-conditions groups area, a dialog box displaying the following message appears:

KAVB0256-E The specified condition group name already exists.

If the Common Exclusion-Condition Settings (Extended) window is opened by choosing Exclude by Common Exclusion-Conditions, Additional common exclusion-conditions group n is displayed as the initial value. The initial value can be changed by using the common-exclusion-conditions auto-input definition file. The number n is the smallest number that has not been used in already defined common exclusion-conditions group names in the range from 1 to the maximum number of condition groups that can be defined. The user can change the displayed name.

Comment

This text box can be used to specify a comment on a common exclusion-condition in extended mode. You can specify a character string that has 1,024 or fewer bytes (when Shift-JIS encoded). All characters other than control characters (0x00 to 0x1F and 0x7F to 0x9F) can be used.

When the Common Exclusion-Condition Settings (Extended) window is opened by choosing Exclude by Common Exclusion-Conditions, the following items are displayed in this text box: the name of the JP1 user that registered the definition, the date on which the common exclusion-condition was registered (in YYYY/MM/DD format), and the time at which the condition was registered (in hh:mm:ss format). The displayed character string can be changed.

Target for exclusion

This is used to specify the exclusion target. Select the Do not acquire events radio button to prevent a JP1 event from being collected when the event satisfies a common exclusion-condition. Select the Acquire events but do not execute automatic actions radio button to exclude a JP1 event from action execution when the event satisfies a common exclusion-condition.

Common exclusion-conditions page

This page is used to set common exclusion-conditions in extended mode.

Conditions Apply Period page

This page is used to set the validity period for common exclusion-conditions that are set in extended mode.

3.16.1 Common exclusion-conditions page

The Common exclusion-conditions page is used to set common exclusion-conditions in extended mode.

Note that if no common exclusion-conditions are set in extended mode on this page (that is, no event conditions are displayed in the Event conditions list), all JP1 events will be filtered out. To perform filtering, make sure that at least one condition is set.

Figure 3‒33: Common exclusion-conditions page

The following describes the items displayed on the Common exclusion-conditions page.

Event conditions list

A list of common exclusion-conditions in extended mode is displayed. Conditions that are higher in the list have higher priority.

The Attribute name column displays the attribute name of each event condition. If an extended attribute is specified for a condition, E is prefixed to the character string that the user specified as an attribute name. For example, if TEST is specified as the name of an extended attribute, E.TEST is displayed.

The Attribute value column displays the value or values of each attribute. If there are multiple values, each value is separated by a comma (,).

The Condition column displays one of the following event condition comparison methods: First characters, Match, Does not match, Is contained, Is not contained, Regular expression, Period, and Time.

Read From Selected Event

Click this button to reflect the attribute values of the JP1 event selected in the Event Console window into the Event conditions list. The following table describes how attribute values are reflected into the list. The byte counts in the table are for Shift-JIS-encoded character strings.

Table 3‒12: Behavior when the Read From Selected Event button is clicked

Event attribute values

Behavior

Length

Control character#1

4,096 or fewer bytes

Not included

All event attribute values are reflected into the list.

For an attribute for which an optional condition can be specified, Match is selected.

Included

The character string before the first control character is reflected into the list.

For an attribute for which an optional condition can be specified, First characters is selected.

4,097 or more bytes

Not included

The first 4,096 bytes#2 are reflected into the list.

For an attribute for which an optional condition can be specified, First characters is selected.

Included in the first 4,096 bytes

The character string before the first control character is reflected into the list.

For an attribute for which an optional condition can be specified, First characters is selected.

Included in the 4,097th and following bytes

The first 4,096 bytes#2 are reflected into the list.

For an attribute for which an optional condition can be specified, First characters is selected.

#1:

Whether the event attribute values include control characters such as line breaks and tabs.

#2:

If the boundary between the 4,096th and 4,097th bytes splits a multi-byte character, the character is not reflected into the list.

Note that display items of the selected JP1 event might be mapped to extended attributes in the Event-Information Mapping Definitions window. In this case, neither the values of the display items nor the values of the mapped extended attributes are reflected into the Event conditions list. For details about event-information mapping definitions, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Add

Click this button to add the event condition selected in the lower list to the Event conditions list. Added event conditions are displayed at the bottom of the Event conditions list. The event conditions that have already been in the Event conditions list are not added. A maximum of 256 event conditions can be added.

Delete

Click this button to delete the selected event condition.

Up

Click this button to move the event condition selected in the Event conditions list up by one line. Use this button to change the priority of the event conditions.

Down

Click this button to move the event condition selected in the Event conditions down by one line. Use this button to change the priority of the event conditions.

Area for editing event conditions

This area is used to edit event conditions in common exclusion-conditions in extended mode. The pattern of this area changes according to the selected attribute. The patterns that can be displayed are described below.

Note that if the Common Exclusion-Condition Settings (Extended) window is opened by choosing Exclude by Common Exclusion-Conditions, the attribute names and values for the JP1 event selected in the source window are automatically set as conditions. The attribute names and values that are set automatically can be set by using the common-exclusion-conditions auto-input definition file. The behavior of the system when an attribute value is longer than 4,096 bytes (when Shift-JIS encoded) or includes control characters is the same as when the Read From Selected Event button is clicked. For details about this file, see Common-exclusion-conditions auto-input definition file (common_exclude_filter_auto_list.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference. In the drop-down list on the right, Match is selected as the comparison method for the specified character string if the total length of the attribute values does not exceed 4,096 bytes. If 4,096 bytes (when Shift-JIS encoded) is exceeded or the attribute value contains a control character, First characters is selected.

Character string editing

This pattern applies when one of the following attributes is selected:

Event source host name

Source host

Object name

Root object name

Occurrence

User name

Message

Product name

Source user name

Source group name

Source IP address

Object ID

Return code

When specifying an IPv6 address for Source IP address, alphabetic characters must be lower case, as shown below:

0011:2233:4455:6677:8899:aabb:ccdd:eeff

You cannot specify an IP address in abbreviated form like the one shown below:

2012:7:8::a:b

If the integrated monitoring database and IM Configuration Management database are enabled, you can specify a business group name in path format for Source host and Event source host name. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

Note that Event source host name can be specified only if event source host mapping is enabled. If this mapping is disabled, conditions for Event source host name can be specified by specifying JP1_SOURCEHOST as the attribute name when the area for editing event conditions is in the Extended-attribute editing pattern.

A character string of 64 kilobytes or less (when Shift-JIS encoded) can be specified. Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is not selected in the drop-down list on the right when ON is set for the -ignorecasehost option of the jcoimdef command, the case of alphabetic characters is ignored for the following attributes:

Source host

Event source host name

Severity-level editing

This pattern applies when the following attribute is selected:

Event level

Which events are filtered out depends on the selected radio button.

If All events for which severity has been defined is selected:

All events for which severity (an event level) is defined are filtered out.

If Specify the severity is selected:

Events assigned a specific severity are filtered out.

You can select Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug as the severity.

If JP1/SES events is selected:

JP1/SES events are filtered out.

Note that if you enable the severity changing function, Original Severity Level is displayed instead of Severity. When this function is enabled, the previous severity level is automatically input when you click the Read From Selected Event button or the Exclude by Common Exclusion-Conditions menu command.

For details on the severity changing function, see 5.13 Setting the severity changing function in the JP1/Integrated Management 3 - Manager Configuration Guide.

Character string editing (with input candidates)

This pattern applies when you select the following attributes:

Object type

Root object type

Specify a character string of no more than 64 kilobytes (when Shift-JIS encoded). Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID editing

This pattern applies when the following attribute is selected:

Event ID

You can specify a maximum of eight hexadecimal digits as an event ID. When specifying multiple event IDs, the entire string must not exceed 64 kilobytes. You cannot specify control characters. The range of specifiable values is from 0 to 7FFFFFFF.

You can specify a maximum of 100 event IDs by using a comma (,) as a separator.

From the drop-down list on the right, select Match or Does not match as a condition for the specified event IDs.

Date and time editing (range specification)

This pattern applies when you select the following attributes:

Start timeframe

End timeframe

The way in which you specify the date and time depends on the selected radio button.

If Specify date and time range is selected:

Specify the year, month, day, hour, minute, and second that serves as the base time of the range. Use the Specify date and time range option when specifying the range as an accumulated number of seconds.

You can enter the current time by clicking the Current Time button.

The way in which the period is specified depends on the selected radio button.

• If the Period radio button is selected:

Specify the target range for the event condition as a period. From the drop-down list on the right, you can select XX days after, XX hours after, XX minutes after, XX days before, XX hours before, or XX minutes before.

• If the Time radio button is selected:

Specify the end of the target range for the event condition as a date and time.

If Specify character string is selected:

Specify a character string of no more than 64 kilobytes (when Shift-JIS encoded). Use the Specify character string option when specifying the range as a character string. Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Date and time editing

This pattern applies when you select the following attributes:

Registered timeframe

Arrived timeframe

Specify the year, month, day, hour, minutes, and seconds.

You can enter the current time by clicking the Current Time button.

The way in which the period is specified depends on the selected radio button.

If the Period radio button is selected:

Specify the target range for the event condition as a period. From the drop-down list on the right, you can select XX days after, XX hours after, XX minutes after, XX days before, XX hours before, or XX minutes before.

If the Time radio button is selected:

Specify the end of the target range for the event condition as a date and time.

Extended-attribute editing

This pattern applies when the following attribute is selected:

Extended attribute

Specify a condition for the program-specific extended attribute.

Depending on the selected radio button, the item that can be specified differs.

When Attribute name is selected:

Specify a condition for the program-specific extended attribute by using an attribute name.

In the Attribute name text box, you can enter a character string of no more than 32 bytes. The character string can contain upper-case alphabetic characters, numerals, and underscores (_). The first character must be an upper case alphabetic character. If you enter a lower-case character, it is converted to an upper-case character. You cannot specify common information as an extended attribute.

When Item name is selected:

Specify a condition for the program-specific extended attribute by using an item name.

Specify a condition by selecting an item name from the Item name drop-down list. The displayed item names are program-specific extended attributes specified for the standard file and the extended file of the definition file for extended event attributes.

In the Condition text box, specify a character string of no more than 64 kilobytes (when Shift-JIS encoded). Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\. Note that \, and \\ each count as one byte.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Numeric value editing

This pattern applies when you select the following attributes:

Registered reason

Source process ID

Source user ID

Source group ID

Specify a decimal integer of no more than 64 kilobytes. You can specify a value in the range from -2,147,483,648 to 2,147,483,647.

From the drop-down list on the right, select Match or Does not match as a condition for the specified numeric value.

When Match or Does not match is selected as the condition, you can only specify integers from 0 to 9 and hyphens (-).

You can specify a maximum of 100 numeric values by using a comma (,) as a separator.

Apply

Click this button to apply the settings.

3.16.2 Conditions Apply Period page

The Conditions Apply Period page is used to set the period during which the common exclusion-conditions in extended mode are applied. The Arrived time attribute (B.ARRIVEDTIME), which is a basic attribute for JP1 events, is used as the base time for the period. The period specified on the Period settings and Time settings areas is compared with the base time to determine the conditions apply period for the common exclusion-conditions in extended mode. For details about the applicable period, see 4.2.7 Common exclusion-conditions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Note that if the Common Exclusion-Condition Settings (Extended) window is opened by choosing Exclude by Common Exclusion-Conditions, no initial settings are specified.

Figure 3‒34: Conditions Apply Period page

The following describes the items displayed on the Conditions Apply Period page.

Period settings

To set the period during which the common exclusion-conditions in extended mode will be applied, select the Enable check box in this area. If only the start day is specified, the conditions will always be applied indefinitely from the specified day. If only the end day is set, the conditions will always be applied until the specified day. If the Enable check box is not selected, the conditions will always be applied.

A time period from 1970/01/01 to 2099/12/31 can be specified.

Time settings

This area can be used to specify detailed settings about the period during which the common exclusion-conditions in extended mode will be applied. For example, the days of the week and the time period on the days that the conditions will be applied can be set. The start time cannot be omitted. If the end time is omitted, a 24-hour period from the start time will be set.

The start time and end time can be specified in the range from 00:00 to 23:59.

If you specify an end time that is earlier than the start time, the system uses the specified time on the following day as the end time. Similarly, if you specify the same end and start time, the system uses the specified time on the following day as the end time.

The Conditions Apply Period includes the start time but not the end time. For example, if you specify 21:00 and 03:00 on Monday as the start and end times respectively, the common exclusion-conditions apply from 21:00:00 on Monday to 02:59:59 on Tuesday.

3.17 Repeated Event Condition Settings window

The Repeated Event Condition Settings window can be used to edit and register repeated event conditions that are used for suppression of monitoring of repeated events.

This window has the Basic Settings page and the Options page.

To display this window:

In the event list of the Event Console window, select one of a large number of identical events, and from the View menu, select Suppress by Repeated Event Conditions. Alternatively, right-click one of the events and select Suppress by Repeated Event Conditions from the pop-up menu.

In the Related Events window, right-click a JP1 event and select Suppress by Repeated Event Conditions from the pop-up menu.

In the List of Repeated Event Conditions window, click the Add button.

In the List of Repeated Event Conditions window, select a repeated event condition, and then click the Edit button.

In the List of Repeated Event Conditions window, select and double-click an item from the repeated event conditions.

If you do not set any conditions for an event condition set in this window, all JP1 events will match the condition.

If you want to display the Repeated Event Condition Settings window, you must have JP1_Console_Admin permission. If the reference/operation permission function for business groups is enabled, you might be unable to display the window, depending on the combination of the JP1 resource group and JP1 permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When you click the OK button after setting the parameters in the Basic Settings and Options pages, the condition you set is added in the List of Repeated Event Conditions window#.

#: The settings take effect when:

The user clicks the Apply button in the List of Repeated Event Conditions window

The user clicks the OK button after using the Suppress by Repeated Event Conditions menu command to set repeated event conditions

The following figure shows the Repeated Event Condition Settings window.

Figure 3‒35: Repeated Event Condition Settings window

The following describes the items displayed in the Repeated Event Condition Settings window.

Repeated event condition name

Use this text box to specify the name of the repeated event condition being edited or registered. Specify a name containing 1 to 50 bytes (when Shift-JIS encoded). You can use any characters except control characters (0x00 to 0x1F and 0x7F to 0x9F).

When the Repeated Event Condition Settings window opens, an initial value is already input. The initial value differs depending on whether the window is opened by selecting Suppress by Repeated Event Conditions or opened from the List of Repeated Event Conditions window. If opened from the List of Repeated Event Conditions window, the initial value is Repeated event condition n. If opened by selecting Suppress by Repeated Event Conditions, the initial value is Additional repetition event condition n. The initial value can be changed by using the auto-input definition file for the repeated event condition. To prevent condition names from repeating, the number n is the smallest unused number from 1 to the maximum number of defined event conditions. You can edit this character string.

If you specify the same name as an existing event condition name, the message KAVB0252-E is displayed in a dialog box.

Comment

Use this text box to enter a comment for the repeated event condition. Specify a character string containing 1,024 or fewer bytes (when Shift-JIS encoded). You can use any characters except control characters (0x00 to 0x1F and 0x7F to 0x9F). This text box is blank if you open the Repeated Event Condition Settings window from the List of Repeated Event Conditions window. If you open the window by selecting Suppress by Repeated Event Conditions from a right-click menu, this text box displays the name of the JP1 user who added the condition, and the date and time when it was added. The date and time are displayed in YYYY/MM/DD hh:mm:ss format and use the time zone of the JP1/IM - View host. You can edit the contents of this text box.

Basic Settings page

Displays the page in which you can specify repeated event conditions and suppression settings.

Options page

Displays the page in which you can define duplicate attribute value conditions, specify when suppression starts and ends, and configure alerts that notify that suppression will continue.

3.17.1 Basic Settings page

The Basic Settings page is used to specify repeated event conditions and suppression settings.

Figure 3‒36: Basic Settings page (in JP1/IM - Manager version 10-50 or later)

Figure 3‒37: Basic Settings page (in JP1/IM - Manager version 10-10)

In JP1/IM - Manager version 10-10, a Suppress actions of the repeated events check box is displayed instead of the Suppress actions for the following events check box in the Suppression items area.

The following describes the items displayed on the Basic Settings page.

List of repeated event conditions

This list box displays a list of repeated event conditions. Conditions that are higher in the list have higher priority.

The Attribute name column displays the names of the attributes of the event conditions. For program-specific extended attributes specified by users, the string E. is prefixed to the attribute names. For example, if TEST is specified, E.TEST is displayed.

The Attribute value column displays one or more attribute values. Multiple attribute values are separated by commas (,).

The Condition column displays the comparative operator for the event condition (First characters, Match, Does not match, Is contained, Is not contained, Regular expression, Period, or Time).

Read From Selected Event

When this button is clicked, the attribute value of the JP1 event selected in the Event Console window is automatically input to the condition list. The following table describes how the system behaves when this button is clicked. The byte counts in the table are for Shift-JIS converted character strings.

Table 3‒13: How the system behaves when the Read From Selected Event button is clicked

Event attribute value

Behavior

Length

Control characters#1

4,096 or fewer bytes

Not included

All event attribute values are applied.

For an attribute for which an optional condition can be specified, Match is selected.

Included

The characters before the first control character are used as the condition value in the condition list.

For an attribute for which an optional condition can be specified, First characters is selected.

4,097 or more bytes

Not included

The first 4,096 bytes#2 are used as the condition value in the condition list.

For an attribute for which an optional condition can be specified, First characters is selected.

Included in the first 4,096 bytes

The characters before the first control character are used as the condition value in the condition list.

For an attribute for which an optional condition can be specified, First characters is selected.

Included after the 4,096th byte

The first 4,096 bytes#2 are used as the condition value in the condition list.

For an attribute for which an optional condition can be specified, First characters is selected.

#1:

This column indicates whether control characters are included in the event attribute value. Control characters here include line breaks and tabs.

#2:

If the 4,096th byte is in the middle of a multi-byte character, the string before the multi-byte character is used as the condition value in the condition list.

If the information about the selected JP1 event is mapped in the event-information mapping definitions, the attribute values and program-specific extended attribute values for the mapped display items are not input to the condition list. For details about the event-information mapping definitions, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information)in the JP1/Integrated Management 3 - Manager Administration Guide.

Add

Click this button to add a new event condition. You can add only event conditions that have not yet been set. The new event condition is added at the bottom of the event condition list. The list can contain a maximum of 256 event conditions.

Delete

Click this button to delete the selected event condition.

Up

Click this button to move the event condition selected event condition one line up.

Use this button to change the priority of the event conditions.

Down

Click this button to move the selected event condition one line down.

Use this button to change the priority of the event conditions.

Event condition editing

This pattern of area is used to edit a condition for suppressing monitoring of repeated events. The area to be displayed differs depending on the selected attribute. The following describes the areas that can be displayed.

If the Repeated Event Condition Settings window that is displayed was opened by selecting Suppress by Repeated Event Conditions, the attribute names and values for the JP1 event selected when the window was opened are automatically set as conditions. The attribute names and values that will be automatically set can be specified by using the auto-input definition file for the repeated event condition. The behavior of the system when an attribute value is longer than 4,096 bytes (when Shift-JIS encoded) or includes control characters is the same as when the Read From Selected Event button is clicked. For details about the auto-input definition file for the repeated event condition, see Auto-input definition file for the repeated event condition (event_storm_auto_list.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Character string editing

This pattern applies when one of the following attributes is selected:

Event source host name

Source host

Object name

Root object name

Occurrence

User name

Message

Product name

Source user name

Source group name

Source IP address

Object ID

Return code

When specifying an IPv6 address for Source IP address, alphabetic characters must be lower case, as shown below:

0011:2233:4455:6677:8899:aabb:ccdd:eeff

You cannot specify an IP address in abbreviated form like the one shown below:

2012:7:8::a:b

If the integrated monitoring database and IM Configuration Management database are enabled, you can specify a business group name in path format for Source host and Event source host name. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

Note that Event source host name can be specified only if the mapping of the event source host is enabled. If the mapping of the event source host is disabled, conditions for Event source host name can be specified by specifying JP1_SOURCEHOST as the attribute name when the area for editing event conditions is in the Extended-attribute editing pattern.

A character string of 64 kilobytes or less (when Shift-JIS encoded) can be specified. Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is not selected in the drop-down list on the right when ON is set for the -ignorecasehost option of the jcoimdef command, the case of alphabetic characters is ignored for the following attributes:

Source host

Event source host name

Severity-level editing

This pattern applies when the following attribute is selected:

Event level

Which events are filtered out depends on the selected radio button.

If All events for which severity has been defined is selected:

All events for which severity (an event level) is defined are filtered out.

If Specify the severity is selected:

Events assigned a specific severity are filtered out.

You can select Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug.

If JP1/SES events is selected:

JP1/SES events are filtered out.

Note that if you enable the severity changing function, Original Severity Level is displayed instead of Severity. When this function is enabled, the previous severity level is automatically input when you click the Suppress by Repeated Event Conditions button or the Exclude by Common Exclusion-Conditions menu command.

For details on the severity changing function, see 5.13 Setting the severity changing function in the JP1/Integrated Management 3 - Manager Configuration Guide.

Character string editing (with input candidates)

This pattern applies when you select the following attributes:

Object type

Root object type

Specify a character string of no more than 64 kilobytes (when Shift-JIS encoded). Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID editing

This pattern applies when the following attribute is selected:

Event ID

You can specify a maximum of eight hexadecimal digits as an event ID. When specifying multiple event IDs, the entire string must not exceed 64 kilobytes. You cannot specify control characters. The range of specifiable values is from 0 to 7FFFFFFF.

You can specify a maximum of 100 event IDs by using a comma (,) as a separator.

From the drop-down list on the right, select Match or Does not match as a condition for the specified event IDs.

Date and time editing (range specification)

This pattern applies when you select the following attributes:

Start timeframe

End timeframe

The way in which you specify the date and time depends on the selected radio button.

If Specify date and time range is selected:

Specify the year, month, day, hour, minute, and second that serves as the base time of the range. Use the Specify date and time range option when specifying the range as an accumulated number of seconds.

You can enter the current time by clicking the Current Time button.

The way in which the period is specified depends on the selected radio button.

• If the Period radio button is selected:

Specify the target range for the event condition as a period. From the drop-down list on the right, you can select XX days after, XX hours after, XX minutes after, XX days before, XX hours before, or XX minutes before.

• If the Time radio button is selected:

Specify the end of the target range for the event condition as a date and time.

If Specify character string is selected:

Specify a character string of no more than 64 kilobytes (when Shift-JIS encoded). Use the Specify character string option when specifying the range as a character string. Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Date and time editing

This pattern applies when you select the following attributes:

Registered timeframe

Arrived timeframe

Specify the year, month, day, hour, minutes, and seconds.

You can enter the current time by clicking the Current Time button.

The way in which the period is specified depends on the selected radio button.

If the Period radio button is selected:

Specify the target range for the event condition as a period. From the drop-down list on the right, you can select XX days after, XX hours after, XX minutes after, XX days before, XX hours before, or XX minutes before.

If the Time radio button is selected:

Specify the end of the target range for the event condition as a date and time.

Extended-attribute editing

This pattern applies when the following attribute is selected:

Extended attribute

Specify a condition for the program-specific extended attribute.

Depending on the selected radio button, the item that can be specified differs.

When Attribute name is selected:

Specify a condition for the program-specific extended attribute by using an attribute name.

In the Attribute name text box, you can enter a character string of no more than 32 bytes. The character string can contain upper-case alphabetic characters, numerals, and underscores (_). The first character must be an upper case alphabetic character. If you enter a lower-case character as the first character, it will be converted to an upper-case character. You cannot specify common information as an extended attribute.

When Item name is selected:

Specify a condition for the program-specific extended attribute by using an item name.

Specify a condition by selecting an item name from the Item name drop-down list. The displayed item names are program-specific extended attributes specified for the standard file and the extended file of the definition file for extended event attributes.

In the Condition text box, specify a character string of no more than 64 kilobytes (when Shift-JIS encoded). Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\. Note that \, and \\ each count as one byte.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Numeric value editing

This pattern applies when you select the following attributes:

Registered reason

Source process ID

Source user ID

Source group ID

Specify a decimal integer of no more than 64 kilobytes, using integers from 0 to 9 and hyphens (-). You can specify values in the range from -2,147,483,648 to 2,147,483,647.

You can specify a maximum of 100 numeric values by using a comma (,) as a separator.

From the drop-down list on the right, select Match or Does not match as a condition for the specified numeric value.

Apply

Click this button to apply the settings.

Suppression items

Specify options for suppressing monitoring of repeated events.

Suppress display of the repeated events list

To prevent the list of repeated events from being displayed, select the Suppress display of the repeated events list check box. If you do not want to prevent this list from being displayed, clear the check box. The check box is selected by default.

Suppress actions for the following events

If you do not want repeated events to trigger automated actions, select the Suppress actions for the following events check box. Then, specify the range of events for which to suppress automated actions by selecting the All repeated events or Repeated events other than repeated start events radio button. The following table describes the difference between these options:

Table 3‒14: Difference between action suppression options

Selected option

Events for which automated actions are suppressed

All repeated events

Actions are suppressed for all events that match the repeated event conditions you are editing.

Repeated events other than repeated start events

Actions are suppressed for all events that match the repeated event conditions you are editing, except the event that caused the system to begin suppressing repeated events.

If you want repeated events to trigger automated actions, clear the check box. The check box is cleared by default.

For details on the events for which the execution of automated actions is suppressed, see 4.5.8 Suppressing the execution of automated actions and response actions triggered by a large number of events in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Make sure that you select either or both of the above check boxes. If you click the OK button without selecting at least one of these check boxes, message KAVB0002-E will be displayed in a dialog box.

In JP1/IM - Manager version 10-10, a Suppress actions of the repeated events check box appears instead of the Suppress actions for the following events check box in the Suppression items area. When you select the Suppress actions of the repeated events check box, JP1/IM - Manager behaves as if you have selected the Suppress actions for the following events check box and the All repeated events suppression option.

3.17.2 Options page

In the Options page, you can specify duplicate attribute value conditions, when suppression starts and ends, and whether to notify the user when suppression continues.

Figure 3‒38: Options page (JP1/IM - Manager version 10-50 or later)

Figure 3‒39: Options page (JP1/IM - Manager version 10-10)

In JP1/IM - Manager version 10-10, the Options page is laid out differently and the Checks for suppression to continue and Processing for when suppression continues areas do not appear.

The following describes the items displayed on the Options page.

Conditions for same attribute values

Use this area to specify duplicate attribute value conditions as repeated event conditions.

From the drop-down list, select an attribute that you want to add to a selected duplicate attribute value condition to designate it as a repeated event condition. By default, no duplicate attribute value conditions are assigned to the repeated event condition.

Add

When you click the Add button, the selected duplicate attribute value condition is added to the end of the Attribute name list. This list displays duplicate attribute value conditions that have been set as repeated event conditions. This list can display a maximum of three duplicate attribute value conditions. When three duplicate attribute value conditions are displayed, the Add button is disabled. If you select Extended attribute (common information/specific information) in the drop-down list and then click the Add button, the Extended Attribute (Common Information/Specific Information) Settings window opens. For details about this window, see 3.18 Extended Attribute (Common Information/Specific Information) Settings window.

Delete

If one or more duplicate attribute value conditions are selected in the Attribute name list, the Delete button is enabled. When this button is clicked, the selected duplicate attribute value conditions are deleted.

Threshold

Specify the threshold values for repeated event conditions. The Enable check box is cleared by default.

Enable

Select this check box to set a threshold.

If this check box is selected, the x events and y seconds boxes are enabled.

x events

Specify the number of events that occur within the specified length of time. You can specify a number from 1 to 200. This text box is blank by default.

y seconds

Specify the number of seconds as the length of time in which the number of events that occur will be monitored. You can specify a number from 1 to 60. This text box is blank by default.

End monitoring period

Specify the end monitoring period for repeated event conditions. You can specify a value from 1 to 86,400 seconds. The default is 300 seconds.

Suppression start event

If you want a suppression start event to be issued, select the Issue check box. When you select this check box, the system issues a suppression start event (event ID: 00003F58) reporting that suppression has started. If you do not want a suppression start event to be issued, clear the check box. This check box is cleared by default.

Suppression end event

If you want a suppression end event to be issued, select the Issue check box. When you select this check box, the system issues a suppression end event (event ID: 00003F59) reporting that suppression has ended. If you do not want a suppression end event to be issued, clear the check box. This check box is cleared by default.

Checks for suppression to continue

In this area, specify whether you want JP1/IM - Manager to check if monitoring is still being suppressed for repeated events at an interval defined as a length of time (in seconds) or number of events. You can also specify whether you want JP1/IM - Manager to cancel suppression or issue a JP1 notification event if it determines that monitoring is still being suppressed.

Specify these items in conjunction with the items in the Processing for when suppression continues area.

This area does not appear in version 10-10 of JP1/IM - Manager.

Enable

Select this check box to have JP1/IM - Manager check whether monitoring is still being suppressed for repeated events. Clear the check box if you do not want JP1/IM - Manager to perform this check. When you select this check box, the items under Timing of checks to decide whether suppression will continue and in the Processing for when suppression continues area become available. This check box is cleared by default.

Timing of checks to decide whether suppression will continue

Select how you want JP1/IM - Manager to determine when to check whether monitoring is still being suppressed for repeated events. When you select Time or Number of events, the text box associated with that option becomes available. The following table shows the differences between these options:

Table 3‒15: Differences between timing options

Selected option

When checks for continued suppression take place

Time

After suppression of events that match the repeated event condition you are editing starts, JP1/IM - Manager checks whether suppression is ongoing each time the number of seconds specified in the text box elapses. For example, if you select Time and enter 3600 in the text box, the system makes the determination every 3,600 seconds (that is, once an hour).

Number of events

After suppression of events that match the repeated event condition you are editing starts, each time JP1/IM - Manager collects the specified number of those events, JP1/IM - Manager checks whether monitoring of the event is still being suppressed. For example, if you select Number of events and enter 100 in the text box, the system makes the determination after every 100 events that match the repeated event condition.

In the Time text box, you can specify a value from 1 to 86,400 (seconds). In the Number of events text box, you can specify a value from 1 to 1,000,000. By default, the Time option is selected and the text box is empty.

For details on the timing of checks to determine whether suppression is ongoing in situations where no threshold is set for the repeated event condition, see 4.4.7 Issuing notifications when the suppression of repeated-event display continues in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

For details on the timing of these checks when a threshold is set for the repeated event condition, see 4.5.7 Issuing notifications when the suppression of monitoring of a large number of events continues in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Processing for when suppression continues

Use this area to specify how JP1/IM - Manager behaves when it determines that monitoring is still being suppressed for repeated events after the specified time (number of seconds) or number of events. JP1/IM - Manager can issue a JP1 event to notify the user, or cancel suppression for the repeated event.

This area becomes available when you select the Enable check box in the Checks for suppression to continue area. Specify these items in conjunction with the items in the Checks for suppression to continue area.

This area does not appear in JP1/IM - Manager version 10-10.

Actions to take when suppression continues

Select the processing that you want to occur when JP1/IM - Manager determines that the suppression of repeated events is ongoing. You can select Issue an event to notify that suppression will continue or Terminate suppression. The following table shows the differences between these options.

Table 3‒16: Differences between processing options

Selected option

Processing when suppression has continued

Issue an event to notify that suppression will continue

If JP1/IM - Manager determines that suppression is ongoing for events that match the repeated event condition you are editing, it issues a notification event for continued suppression (event ID: 00003F65). For example, suppose that you specify every 100 events as the Timing of checks to decide whether suppression will continue in the Checks for suppression to continue area. In this case, the notification event is issued each time JP1/IM - Manager collects 100 events that match the repeated event condition you are editing.

Terminate suppression

JP1/IM - Manager cancels suppression upon determining that suppression is ongoing for events that match the repeated event condition you are editing. For example, suppose that you configure JP1/IM - Manager to check whether suppression is still in progress every 3,600 seconds (hourly) in Timing of checks to decide whether suppression will continue in the Checks for suppression to continue area. In this case, JP1/IM - Manager will cancel suppression if it has collected an event that matches the repeated event condition you are editing in the 3,600 seconds after suppression began. When you select Terminate suppression, the Issue an event to notify that suppression will be terminated check box becomes available. If you select this check box, JP1/IM - Manager will issue an event notifying that suppression is canceled (event ID: 00003F60).

By default, Issue an event to notify that suppression will continue is selected.

3.18 Extended Attribute (Common Information/Specific Information) Settings window

The Extended Attribute (Common Information/Specific Information) Settings window is used to specify the name of a common extended attribute or a specific (program-specific or user-specific) extended attribute.

To open this window, in the Repeated Event Condition Settings window, open the Options page. Then, from the Conditions for same attribute values drop-down list, select Extended attribute (common information/specific information), and click the Add button.

Figure 3‒40: Extended Attribute (Common Information/Specific Information) Settings window

The following describes the items displayed in the Extended Attribute (Common Information/Specific Information) Settings window.

Attribute name

Specify the name of the extended attribute.

The name you can specify is a character string that begins with a half-width upper-case alphabetic character and can have half-width upper-case alphabetic characters, numeric characters, and underscores (_). The length of the character string must be no more than 32 bytes. If you specify an invalid attribute name, the message KAVB0509-E will be displayed in a dialog box. If you specify an attribute name that is already specified in a duplicate attribute value condition of a repeated event condition, the message KAVB0255-E appears in a dialog box.

3.19 List of Repeated Event Conditions window

The List of Repeated Event Conditions window is used to display a list of repeated event conditions, which are used for suppressing monitoring of repeated events.

To display this window, in the Event Console window, from the Options menu, select Repeated Event Condition Settings.

To use the List of Repeated Event Conditions window, you must have JP1_Console_Admin permission. You cannot use this window if you log in to a Central Console in which suppression of monitoring of repeated events is disabled.

The following figure shows the List of Repeated Event Conditions window.

Figure 3‒41: List of Repeated Event Conditions window

The following describes the items displayed in the List of Repeated Event Conditions window.

List of repeated event conditions

This area lists repeated event conditions. The higher a repeated event condition is listed, the higher its priority.

A maximum of 2,500 repeated event conditions can be listed. You can select multiple conditions in the list.

(Pencil icon)

A pencil icon appears for a repeated event condition that was added or edited. This icon disappears when the condition is applied to Central Console by clicking the Apply button.

Apply

Select the check box in this column for a repeated event condition that you want to manipulate.

Type

The icon is displayed in this column for additional repetition event conditions. No icon is displayed for other conditions.

Repeated event condition name

The name of a repeated event condition is displayed in this column.

Comment

The comment specified for a repeated event condition is displayed in this column.

Add

Click this button when you want to add a repeated event condition to the List of repeated event conditions. When you click this button, the Repeated Event Condition Settings window opens. For details about this window, see 3.17 Repeated Event Condition Settings window. When you click the OK button in the Repeated Event Condition Settings window, the repeated event condition is appended to the end of the List of repeated event conditions. If no more repeated event conditions can be added, the Add button is disabled.

Edit

Click this button when you want to edit the repeated event condition selected in the List of repeated event conditions. When you click this button, the Repeated Event Condition Settings window opens, displaying the details of the selected condition. For details about this window, see 3.17 Repeated Event Condition Settings window. When you click the OK button in the Repeated Event Condition Settings window, the changes are applied. This button becomes available when a repeated event condition is selected in the List of repeated event conditions area.

Copy

Click this button when you want to create a copy of the repeated event condition selected in the List of repeated event conditions. When you click this button, a copy of the selected condition is appended to the end of that list. The string Copy is prefixed to the appended condition. For example, if you created a copy of ABC (which is the name of the repeated event condition that is to be copied), Copy ABC is appended. If Copy ABC already exists, a number beginning with 2 is suffixed to Copy (for example, Copy2 ABC). The suffixed number can be incremented (2, 3, 4, ...) to prevent duplication of condition names. The Copy button is available when a repeated event condition is selected in the List of repeated event conditions. It becomes unavailable when the maximum number of repeated event conditions has been reached. The button is unavailable when no repeated event conditions is selected or when multiple repeated event conditions are selected.

Delete

Click this button when you want to delete the repeated event conditions selected in the List of repeated event conditions. Multiple conditions can be deleted at once. When you click this button, the message KAVB0253-Q is displayed in a dialog box. When you click the Yes button in this dialog box, the selected conditions are deleted. If no repeated event conditions are displayed in the list, the Delete button is disabled. The Delete button is enabled when at least one condition is selected.

Change Type

Click this button when you want to change the type of the repeated event conditions selected in the List of repeated event conditions. The type of multiple conditions can be changed at once. When you click the Change Type button, the message KAVB1148-Q is displayed in a dialog box. When you click the Yes button in this dialog box, the type of the selected conditions is changed. Note that the possible type change is from additional repetition event conditions to repeated event conditions only. The contents of the Apply, Repeated event condition name, and Comment columns do not change. If you select repeated event conditions, they will not be changed to additional repetition event conditions. If there are no additional repetition event conditions in the List of repeated event conditions, the Change Type button is disabled. The Change Type button is enabled when at least one additional repetition event condition is selected. If you inadvertently change the type of a condition from additional repetition event condition to repeated event condition, you can cancel the change by clicking the Close button in the List of Repeated Event Conditions window instead of Apply.

Up

Click this button when you want to move the repeated event conditions selected in the List of repeated event conditions one line up. The Up button is enabled unless any of the following conditions exist:

No repeated event condition is selected.

The repeated event condition on the top line is selected.

Discontinuous event conditions are selected.

Down

Click this button when you want to move the repeated event conditions selected in the List of repeated event conditions one line down. The Down button is enabled unless any of the following conditions exist:

No repeated event condition is selected.

The repeated event condition on the bottom line is selected.

Discontinuous event conditions are selected.

Apply

The settings displayed in the List of Repeated Event Conditions window are applied to Central Console. While suppression of monitoring of repeated events is enabled, suppression continues for repeated events that are not affected by changes to repeated event conditions. Suppression ends for repeated events that are affected by changes to repeated event conditions. Repeated event conditions are assumed to be changed when:

The state of a check box in the Apply column was changed in the List of repeated event conditions area.

The Edit button is clicked to open the Repeated Event Condition Settings window, and then the OK button is clicked.

The repeated event conditions are deleted.

3.20 View Severity Change Definitions window

The View Severity Change Definitions window displays a list of severity change definitions associated with the function for changing the severity level.

This window is displayed when the user clicks Severity Change Definitions in the Options menu in the Event Console window.

To use the View Severity Change Definitions window, you must have JP1_Console_Admin permission. You cannot use this window if you log in to an instance of Central Console in which the severity changing function is disabled.

The following figure shows the View Severity Change Definitions window:

Figure 3‒42: View Severity Change Definitions window

The following describes the items displayed in the View Severity Change Definitions window.

View severity change definitions

This area displays a list of severity change definitions. The higher a severity change definition is listed, the higher its priority.

A maximum of 1,000 severity change definitions can be listed. You can select multiple definitions in the list.

Apply

The operations you perform in this window apply to severity change definitions whose check boxes you select in this column.

Type

The icon is displayed in this column for additional severity changing definitions. No icon is displayed for other types of definition.

Severity change definition name

The name of the severity change definition.

Comment

A comment set for the severity change definition.

Add

Click this button to add a severity change definition to the View severity change definitions list. When you click this button, the Severity Change Definition Settings window appears. For details about this window, see 3.21 Severity Change Definition Settings window (Add Severity Change Definition Settings window). When you click the OK button in the Severity Change Definition Settings window, the severity change definition is added to the end of the View severity change definitions list. The Add button becomes unavailable when the maximum number of definitions is reached.

Edit

Click this button to edit a severity change definition selected in the View severity change definitions list. When you click this button, the Severity Change Definition Settings window appears with the details of the selected definition displayed. For details about this window, see 3.21 Severity Change Definition Settings window (Add Severity Change Definition Settings window). The changes take effect when you click the OK button in the Severity Change Definition Settings window. This button becomes available when a severity change definition is selected in the View severity change definition area.

Copy

Click this button when you want to create copies of the severity change definitions selected in the View severity change definitions area. When you click this button, copies of the selected definitions are added to the end of the list. The names of the new definitions are the original names prefixed with the string Copy. For example, if you copy a definition named ABC, the copy is named Copy ABC. If Copy ABC already exists, a number (starting from 2) is added after Copy. This number is incremented (2, 3, 4, and so on) to ensure that definition names are not repeated. The Copy button is available when a severity change definition is selected in the View severity change definitions area, unless no more severity change definitions can be added. The Copy button becomes unavailable when the maximum number of definitions is reached. The button is unavailable when no severity change definition is selected or when multiple definitions are selected.

Delete

Click this button to delete the severity change definitions selected in the View severity change definitions area. You can delete multiple definitions in one operation. When you click this button, the message KAVB0253-Q appears in a dialog box. When you click the Yes button in this dialog box, the selected definitions are deleted. If no severity change definitions are displayed in the list, the Delete button is unavailable. The Delete button is available when at least one definition is selected.

Change Type

Click this button to change the type of the severity change definitions selected in the View severity change definitions area. You can changing the type of multiple definitions in one operation. When you click the Change Type button, the message KAVB1148-Q appears in a dialog box. Click the Yes button in this dialog box to change the selected definitions from additional severity changing definitions to severity change definitions. The contents of the Apply, Severity change definition name, and Comment columns do not change. You cannot change a severity change definition to an additional severity changing definition. The Change Type button is unavailable if there are no additional severity changing definitions in the View severity change definitions area. The button becomes available when at least one additional severity changing definition is selected. If you inadvertently change a definition from an additional severity changing definition to a severity change definition, you can undo the change by clicking the Close button in the View Severity Change Definitions window instead of Apply.

Up

Click this button to move the severity change definitions selected in the View severity change definitions area up one line. The Up button is unavailable if any of the following apply:

- No severity change definitions are selected.

- The selected severity change definition is already at the top of the list.

- The selected severity change definitions are not in sequence.

Down

Click this button to move the severity change definitions selected in the View severity change definitions area down one line. The Down button is unavailable if any of the following apply:

- No severity change definitions are selected.

- The selected severity change definition is already at the bottom of the list.

- The selected severity change definitions are not in sequence.

Apply

Applies the settings displayed in the View Severity Change Definitions window to Central Console.

3.21 Severity Change Definition Settings window (Add Severity Change Definition Settings window)

In the Severity Change Definition Settings window (Add Severity Change Definition Settings window), you can edit and register severity change definitions associated with the severity changing function. Depending on how you display the window, the Severity Change Definition Settings or Add Severity Change Definition Settings window appears.

To display these windows:

Severity Change Definition Settings window

Click the Add button in the View Severity Change Definitions window.

Select a severity change definition in the View Severity Change Definitions window and click the Edit button.

In the View Severity Change Definitions window, select and double-click an item in the severity change definitions list.

Add Severity Change Definition Settings window

In the event list of the Event Console window, select an event associated with a severity change definition, and from the View menu, select Add Severity Change Definition Settings. Alternatively, right-click the event and select Add Severity Change Definition Settings from the pop-up menu.

If you do not set any conditions for an event condition set in this window, all JP1 events will match the condition.

You must have JP1_Console_Admin permission to display the Severity Change Definition Settings (or Add Severity Change Definition Settings) window. If the reference/operation permission function for business groups is enabled, a user might be unable to display the window depending on his or her combination of JP1 resource groups and JP1 permission levels. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When you click the OK button after setting a severity change definition in this window, the definition is added to the View Severity Change Definitions window#.

#: The new settings take effect when:

The user clicks the Apply button in the View Severity Change Definitions window

The user clicks the OK button after using the Add Severity Change Definition Settings menu command to set severity change definitions

The figures below show the Severity Change Definition Settings window and the Add Severity Change Definition Settings window.

Figure 3‒43: Severity Change Definition Settings window

Figure 3‒44: Add Severity Change Definition Settings window

The following describes the items displayed in these windows:

Severity change definition name

Use this text box to enter the name of the severity change definition. Specify a character string of 1 to 50 bytes (where the number of bytes indicates, for Windows, the length of the character string encoded in Shift-JIS, or for UNIX, the length of the character string encoded in a language encoding with which JP1/IM - Manager operates). You can use any characters except control characters (0x00 to 0x1F and 0x7F to 0x9F).

An initial value is already input when you open the Severity Change Definition Settings window. The initial value depends on whether the window was opened by selecting the Add Severity Change Definition Settings menu command or opened from the View Severity Change Definitions window. If the window was opened from the View Severity Change Definitions window, the initial value is Severity change definition n. If the window was opened by selecting Add Severity Change Definition Settings, the initial value is value-set-in-auto-input-definition-file-for-severity-change-definition n. You can change the initial value by using the auto-input definition file for the severity change definition. So as not to repeat the name of an existing severity change definition, the number n is the smallest unused number in the range from 1 to the maximum number of severity change definitions. You can edit this character string.

If you specify the same name as an existing severity change definition, the message KAVB0252-E is displayed in a dialog box.

Comment

Use this text box to enter a comment for the severity change definition. Specify a character string up to 1,024 bytes long (where the number of bytes indicates, for Windows, the length of the character string encoded in Shift-JIS, or for UNIX, the length of the character string encoded in a language encoding with which JP1/IM - Manager operates). You can use any characters except control characters (0x00 to 0x1F and 0x7F to 0x9F). This text box is blank if you open the Severity Change Definition Settings window from the View Severity Change Definitions window. If you open the window by selecting the Add Severity Change Definition Settings command from the pop-up menu, this text box displays the name of the JP1 user who added the definition, and the date and time when the definition was added. The date and time is displayed in YYYY/MM/DD hh:mm:ss format using the time zone of the JP1/IM - View host. You can edit the contents of this text box.

Event conditions

Displays a list of event conditions for severity change definitions. Conditions that are higher in the list have higher priority.

The Attribute name column displays the names of the attributes of the event conditions. For program-specific extended attributes specified by users, the string E. is prefixed to the attribute names. For example, if TEST is specified, E.TEST is displayed.

The Attribute value column displays one or more attribute values. Multiple attribute values are separated by commas (,).

The Condition column displays the comparative operator for the event condition (First characters, Match, Does not match, Is contained, Is not contained, or Regular expression).

Read From Selected Event

When you click this button, the attribute values of the JP1 event selected in the Event Console window are automatically input to the condition list. The following table describes how the system behaves when this button is clicked. The byte counts in the table are for character strings encoded by Shift-JIS if JP1/IM - Manager runs on Windows or for character strings encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX.

Table 3‒17: How the system behaves when the Read From Selected Event button is clicked

Event attribute value

Behavior

Length

Control characters#1

4,096 or fewer bytes

Not included

All event attribute values are applied.

For attributes for which an optional condition can be specified, Match is selected.

Included

The characters before the first control character are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

4,097 or more bytes

Not included

The first 4,096 bytes#2 are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

Included in the first 4,096 bytes

The characters before the first control character are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

Included after the 4,096th byte

The first 4,096 bytes#2 are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

#1

This column indicates whether control characters are included in the event attribute value. Control characters include linefeeds and tabs.

#2

If the 4,096th byte is part of a multi-byte character, the string before the multi-byte character is used as the condition value in the condition list.

If information about the selected JP1 event is mapped in an event-information mapping definition, the attribute values and program-specific extended attribute values for the mapped display items are not input to the condition list. For details about event-information mapping definitions, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Add

Click this button to add a new event condition. Event conditions that are not already set for the definition are added to the bottom of the event condition list. The list can contain a maximum of 256 event conditions.

Delete

Click this button to delete the selected event condition.

Up

Click this button to move the selected event condition up one line.

Use this button to change the priority of the event conditions.

Down

Click this button to move the selected event condition down one line.

Use this button to change the priority of the event conditions.

Event condition editing area

This area is used to edit the event conditions of the severity change definitions. What form this area takes depends on the selected attribute. Each type of area is described below.

Note that if the window was opened by selecting the Add Severity Change Definition Settings menu command, the attribute names and values for the JP1 event that was selected when the window was opened are automatically set as conditions. You can specify which attribute names and values are to be automatically set by using the auto-input definition file for the severity change definition. When an attribute value is longer than 4,096 bytes (where the number of bytes indicates, for Windows, the length of the character string encoded in Shift-JIS, or for UNIX, the length of the character string encoded in a language encoding with which JP1/IM - Manager operates) or when an attribute value includes a control character, the system behaves in the same way as when the Read From Selected Event button is clicked. For details about the auto-input definition file for the severity change definition, see Auto-input definition file for the severity change definition (chsev_auto_list.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Character string editing

This pattern applies when one of the following attributes is selected:

Event source host name

Source host

Object name

Root object name

Occurrence

User name

Message

Product name

Destination event server name

Source user name

Source group name

Object ID

Return code

If the integrated monitoring database and IM Configuration Management database are enabled, you can specify a business group name in path format for Source host and Event source host name. In this case, either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

Note that Event source host name can be specified only if the mapping of the event source host is enabled. If the mapping of the event source host is disabled, conditions for Event source host name can be specified by specifying JP1_SOURCEHOST as the attribute name when the area for editing event conditions is in the Extended-attribute editing pattern.

Specify a character string of no more than 4 kilobytes (where the number of bytes indicates, for Windows, the length of the character string encoded in Shift-JIS, or for UNIX, the length of the character string encoded in a language encoding with which JP1/IM - Manager operates). Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is not selected in the drop-down list on the right when ON is set for the -ignorecasehost option of the jcoimdef command, the case of alphabetic characters is ignored for the following attributes:

Source host

Event source host name

To specify a character string that includes tabs, line breaks, or commas (,), use the representation shown in the following table.

Table 3‒18: Specification of a character string that includes tabs, line breaks, or commas for the editing of character strings

Number

Item

Representation

1

Tab (0x09)

\t

2

Linefeed (0x0a)

\n

3

Carriage return (0x0d)

\r

4

Comma (0x2c)

When used as a separator

,

When used as an ordinary character and Regular expression is selected in the drop-down list on the right

,

When used as an ordinary character and Regular expression is not selected in the drop-down list on the right

\,

The representation of tabs and line breaks used in the Severity Change Definition Settings window and the Add Severity Change Definition Settings window is different from the representation used in the severity changing definition file (jcochsev.conf). For details, see Severity changing definition file (jcochsev.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Original severity level editing

This pattern applies when the following attribute is selected:

Original Severity Level

You can select Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug. The original severity level is automatically input when you click the Read From Selected Event button or the Add Severity Change Definition Settings menu command.

Character string editing (with input candidates)

This pattern applies when you select the following attributes:

Object type

Root object type

Specify a character string of no more than 4 kilobytes (where the number of bytes indicates, for Windows, the length of the character string encoded in Shift-JIS, or for UNIX, the length of the character string encoded in a language encoding with which JP1/IM - Manager operates). Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

To specify a character string that includes tabs, line breaks, or commas (,), use the representation shown in the following table.

Table 3‒19: Specification of a character string that includes tabs, line breaks, or commas for the editing of character strings with input candidates

Number

Item

Representation

1

Tab (0x09)

\t

2

Linefeed (0x0a)

\n

3

Carriage return (0x0d)

\r

4

Comma (0x2c)

When used as a separator

,

When used as an ordinary character and Regular expression is selected in the drop-down list on the right

,

When used as an ordinary character and Regular expression is not selected in the drop-down list on the right

\,

The representation of tabs and line breaks used in the Severity Change Definition Settings window and the Add Severity Change Definition Settings window is different from the representation used in the severity changing definition file (jcochsev.conf). For details, see Severity changing definition file (jcochsev.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Event ID editing

This pattern applies when the following attribute is selected:

Event ID

You can specify a maximum of eight hexadecimal digits as an event ID. When specifying multiple event IDs, the entire string must not exceed 4 kilobytes. You cannot specify control characters. The range of specifiable values is from 0 to 7FFFFFFF.

You can specify a maximum of 100 event IDs by using a comma (,) as a separator.

From the drop-down list on the right, select Match or Does not match as a condition for the specified event IDs.

Extended-attribute editing

This pattern applies when the following attribute is selected:

Extended attribute

Specify a condition for the program-specific extended attribute.

Depending on the selected radio button, the item that can be specified differs.

When Attribute name is selected:

Specify a condition for the program-specific extended attribute by using an attribute name.

In the Attribute name text box, you can enter a character string of no more than 32 bytes. The character string can contain upper-case alphabetic characters, numerals, and underscores (_). The first character must be an upper case alphabetic character. If you enter a lower-case character as the first character, it is converted to an upper-case character. You cannot specify common information as an extended attribute.

When Item name is selected:

Specify a condition for the program-specific extended attribute by using an item name.

Specify a condition by selecting an item name from the Item name drop-down list. The displayed item names are program-specific extended attributes specified for the standard file and the extended file of the definition file for extended event attributes.

In the Condition text box, specify a character string of no more than 4 kilobytes (where the number of bytes indicates, for Windows, the length of the character string encoded in Shift-JIS, or for UNIX, the length of the character string encoded in a language encoding with which JP1/IM - Manager operates). Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\. Note that \, and \\ each count as one byte.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Numeric value editing

This pattern applies when you select the following attributes:

Registered reason

Source process ID

Source user ID

Source group ID

Specify a decimal integer of no more than 4 kilobytes, using integers from 0 to 9 and hyphens (-). You can specify values in the range from -2,147,483,648 to 2,147,483,647.

You can specify a maximum of 100 numeric values by using a comma (,) as a separator.

From the drop-down list on the right, select Match or Does not match as a condition for the specified numeric value.

Apply

Click this button to apply the settings.

New severity level

Specify the new severity level for the severity change definition.

You can select Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug.

3.22 Display Message Change Definitions window

The Display Message Change Definitions window displays a list of display message change definitions associated with the display message change settings function.

This window is displayed when you click Display Message Change Definitions in the Options menu in the Event Console window.

To use the Display Message Change Definitions window, you must have the JP1_Console_Admin permission. You cannot use this window if you log in to an instance of Central Console in which the display message change settings function is disabled.

The following figure shows the Display Message Change Definitions window.

Figure 3‒45: Display Message Change Definitions window

The following describes the items displayed in the Display Message Change Definitions window.

Display message change definitions

This area displays a list of display message change definitions. The higher a display message change definition is listed, the higher its priority.

A maximum of 3,000 display message change definitions can be listed.

You can select multiple definitions in the list.

Apply

The operations you perform in this window apply to display message change definitions whose check boxes you select in this column.

Type

The icon is displayed in this column for additional display message change definitions. No icon is displayed for other types of definition.

Display message change definition name

The name of the display message change definition.

Comment

A comment set for the display message change definition.

Add

Click this button to add a display message change definition to the Display message change definitions list. When you click this button, the Display Message Change Definition Settings window appears. For details about this window, see 3.23 Display Message Change Definition Settings window (Add Display Message Change Definition Settings window). When you click the OK button in the Display Message Change Definition Settings window, the display message change definition is added to the end of the Display message change definitions list. The Add button becomes unavailable when the maximum number of definitions is reached.

Edit

Click this button to edit a display message change definition selected in the Display message change definitions list. When you click this button, the Display Message Change Definition Settings window appears with the details of the selected definition displayed. For details about this window, see 3.23 Display Message Change Definition Settings window (Add Display Message Change Definition Settings window). The changes take effect when you click the OK button in the Display Message Change Definition Settings window. This button becomes available when a display message change definition is selected in the Display message change definitions list.

Copy

Click this button when you want to create a copy of the display message change definition selected in the Display message change definitions list. When you click this button, a copy of the selected definition is added to the end of the list. The name of the new definition is the original name prefixed with the string Copy. For example, if you copy a definition named ABC, the copy is named Copy ABC. If Copy ABC already exists, a number (starting from 2) is added after Copy. This number is incremented (2, 3, 4, and so on) to ensure that definition names are not repeated. The Copy button is available when a display message change definition is selected in the Display message change definitions list, unless no more display message change definitions can be added. The Copy button becomes unavailable when the maximum number of definitions is reached. The button also becomes unavailable when no display message change definition is selected or when multiple definitions are selected.

Delete

Click this button to delete the display message change definitions selected in the Display message change definitions list. You can delete multiple definitions in one operation. When you click this button, the message KAVB0253-Q appears in a dialog box. When you click the Yes button in this dialog box, the selected definitions are deleted. If no display message change definitions are displayed in the list, the Delete button is unavailable. The Delete button is available when at least one definition is selected.

Change Type

Click this button to change the type of the additional display message change definitions selected in the Display message change definitions list. You can change the type of multiple additional display message change definitions in one operation. When you click the Change Type button, the message KAVB1148-Q appears in a dialog box. Click the Yes button in this dialog box to change the selected definitions from additional display message change definitions to display message change definitions. The contents of the Apply, Display message change definition name, and Comment columns do not change. You cannot change a display message change definition to an additional display message change definition. The Change Type button becomes unavailable if no additional display message change definitions are in the Display message change definitions list. The button becomes available when at least one additional display message change definition is selected. If you inadvertently change a definition from an additional display message change definition to a display message change definition, you can undo the change by clicking the Close button in the Display Message Change Definitions window instead of the Apply button.

Up

Click this button to move the display message change definitions selected in the Display message change definitions list up one line. The Up button is unavailable if one of the conditions below is satisfied. The Up button becomes available for other cases.

- No display message change definitions are selected.

- The selected display message change definition is already at the top of the list.

- The selected display message change definitions are not in sequence.

Down

Click this button to move the display message change definitions selected in the Display message change definitions list down one line. The Down button is unavailable if one of the conditions below is satisfied. The Down button becomes available for other cases.

- No display message change definitions are selected.

- The selected display message change definition is already at the bottom of the list.

- The selected display message change definitions are not in sequence.

Apply

Applies the settings displayed in the Display Message Change Definitions window to Central Console.

3.23 Display Message Change Definition Settings window (Add Display Message Change Definition Settings window)

In the Display Message Change Definition Settings window (Add Display Message Change Definition Settings window), you can edit and register display message change definitions associated with the display message change function. Depending on how you display the window, the Display Message Change Definition Settings or the Add Display Message Change Definition Settings window is displayed.

To display these windows:

Display Message Change Definition Settings window

Click the Add button in the Display Message Change Definitions window.

Select a display message change definition in the Display Message Change Definitions window, and then click the Edit button.

In the Display message change definitions list of the Display Message Change Definitions window, select an item, and then double-click the item.

Add Display Message Change Definition Settings window

In the event list of the Event Console window, select an event associated with a display message change definition, and then from the View menu, select Add Display Message Change Definition Settings. Alternatively, right-click the event, and then select Add Display Message Change Definition Settings from the pop-up menu.

If you do not set any conditions for an event condition set in this window, all JP1 events will match the condition.

You must have JP1_Console_Admin permission to display the Display Message Change Definition Settings (or Add Display Message Change Definition Settings) window. If the reference/operation permission function for business groups is enabled, a user might be unable to display the window depending on his or her combination of JP1 resource groups and JP1 permission levels. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When you click the OK button after setting a display message change definition in this window, the definition is added to the Display Message Change Definitions window#.

#: The new settings take effect in the following cases:

The user clicks the Apply button in the Display Message Change Definitions window

The user clicks the OK button after using the Add Display Message Change Definition Settings menu command to set display message change definitions

The figures below show the Display Message Change Definition Settings window and the Add Display Message Change Definition Settings window.

Figure 3‒46: Display Message Change Definition Settings window

Figure 3‒47: Add Display Message Change Definition Settings window

The following describes the items displayed in these windows:

Display message change definition name

Use this text box to enter the name of the display message change definition. Specify a character string of 1 to 50 bytes when the character string is encoded by Shift-JIS if JP1/IM - Manager runs on Windows, or when the character string is encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX. You can use any characters except control characters (0x00 to 0x1F and 0x7F to 0x9F).

An initial value is already input when you open the Display Message Change Definition Settings window. The initial value depends on whether the Display Message Change Definition Settings window was opened from the Display Message Change Definitions window or whether the Add Display Message Change Definition Settings window was opened by selecting the Add Display Message Change Definition Setting menu command. If the Display Message Change Definition Settings window was opened from the Display Message Change Definitions window, the initial value is Display message change definition n. If the Add Display Message Change Definition Settings window was opened by selecting the Add Display Message Change Definition Settings menu command, the initial value is value-set-in-automatic-input-definition-file-for-a-display-message-change-definition n. You can change the initial value by using the automatic input definition file for a display message change definition. To avoid repeating the name of an existing display message change definition, the number n is the smallest unused number in the range from 1 to the maximum number of display message change definitions. You can edit this character string.

If you specify the same name as an existing display message change definition, the message KAVB0252-E is displayed in a dialog box.

Comment

Use this text box to enter a comment for the display message change definition. Specify a character string containing 1,024 or fewer bytes when the character string is encoded by Shift-JIS if JP1/IM - Manager runs on Windows, or when the character string is encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX. You can use any characters except control characters (0x00 to 0x1F and 0x7F to 0x9F). This text box is blank if you open the Display Message Change Definition Settings window from the Display Message Change Definitions window. If you open the window by selecting the Add Display Message Change Definition Settings menu command from the pop-up menu, this text box displays the name of the JP1 user who added the definition, and the date and time when the definition was added. The date and time is displayed in YYYY/MM/DD hh:mm:ss format using the time zone of the JP1/IM - View host. You can edit the contents of this text box.

Event conditions

Displays a list of event conditions for display message change definitions. Conditions that are higher in the list have higher priority.

The Attribute name column displays the names of the attributes of the event conditions. For program-specific extended attributes specified by users, the string E. is prefixed to the attribute names. For example, if TEST is specified, E.TEST is displayed.

The Attribute value column displays one or more attribute values. Multiple attribute values are separated by commas (,).

The Condition column displays the comparative operator for the event condition (First characters, Match, Does not match, Is contained, Is not contained, or Regular expression).

Read From Selected Event

When you click this button, the attribute values of the JP1 event selected in the Event Console window are automatically input to the condition list. The table below describes how the system behaves when this button is clicked. The byte counts in the table are for character strings encoded by Shift-JIS if JP1/IM - Manager runs on Windows or for character strings encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX.

Table 3‒20: How the system behaves when the Read From Selected Event button is clicked

Event attribute value

Behavior

Length

Control characters#1

4,096 or fewer bytes

Not included

All event attribute values are applied.

For attributes for which an optional condition can be specified, Match is selected.

Included

The characters before the first control character are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

4,097 or more bytes

Not included

The first 4,096 bytes#2 are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

Included in the first 4,096 bytes

The characters before the first control character are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

Included after the 4,096th byte

The first 4,096 bytes#2 are used as the condition value in the condition list.

For attributes for which an optional condition can be specified, First characters is selected.

#1

This column indicates whether control characters are included in the event attribute value. Control characters include linefeeds and tabs.

#2

If the 4,096th byte is part of a multi-byte character, the string before the multi-byte character is used as the condition value in the condition list.

If information about the selected JP1 event is mapped in an event-information mapping definition, the attribute values and program-specific extended attribute values for the mapped display items are not input to the condition list. For details about event-information mapping definitions, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Add

Click this button to add a new event condition. Event conditions that are not already set for the definition are added to the bottom of the event condition list. The list can contain a maximum of 256 event conditions.

Delete

Click this button to delete the selected event condition.

Up

Click this button to move the selected event condition up one line.

Use this button to change the priority of the event conditions.

Down

Click this button to move the selected event condition down one line.

Use this button to change the priority of the event conditions.

Event condition editing area

This area is used to edit the event conditions of the display message change definitions. What form this area takes depends on the selected attribute. Each type of the area is described below.

Note that if the window was opened by selecting the Add Display Message Change Definition Settings menu command, the attribute names and values for the JP1 event that was selected when the window was opened are automatically set as conditions. You can specify which attribute names and values are to be automatically set by using the automatic input definition file for a display message change definition. The behavior of the system when an attribute value is longer than 4,096 bytes (when Shift-JIS encoded) or includes control characters is the same as when the Read From Selected Event button is clicked. For details about the automatic input definition file for a display message change definition, see Automatic input definition file for a display message change definition (chmsg_auto_list.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Character string editing

This pattern applies when one of the following attributes is selected:

- Event source host name

- Source host

- Object name

- Root object name

- Occurrence

- User name

- Message

- Product name

- Destination event server name

- Source user name

- Source group name

- Object ID

- Return code

If the integrated monitoring database and IM Configuration Management database are enabled, you can specify a business group name in path format for Source host and Event source host name. In this case, either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

Note that Event source host name can be specified only if the mapping of the event source host is enabled. If the mapping of the event source host is disabled, conditions for Event source host name can be specified by specifying JP1_SOURCEHOST as the attribute name when the area for editing event conditions is in the Extended-attribute editing pattern.

Specify a character string of no more than 4 kilobytes when the character string is encoded by Shift-JIS if JP1/IM - Manager runs on Windows, or when the character string is encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX. Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is not selected in the drop-down list on the right when ON is set for the -ignorecasehost option of the jcoimdef command, the case of alphabetic characters is ignored for the following attributes:

- Source host

- Event source host name

Event level editing

This pattern applies when the following attribute is selected:

- Event level

You can select Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug. The original severity level is automatically input when you click the Read From Selected Event button or the Add Display Message Change Definition Settings menu command.

Character string editing (with input candidates)

This pattern applies when you select the following attributes:

- Object type

- Root object type

Specify a character string of no more than 4 kilobytes when the character string is encoded by Shift-JIS if JP1/IM - Manager runs on Windows, or when the character string is encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX. Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID editing

This pattern applies when the following attribute is selected:

- Event ID

You can specify a maximum of eight hexadecimal digits as an event ID. When specifying multiple event IDs, the entire string must not exceed 4 kilobytes. You cannot specify control characters. The range of specifiable values is from 0 to 7FFFFFFF.

You can specify a maximum of 100 event IDs by using a comma (,) as a separator.

From the drop-down list on the right, select Match or Does not match as a condition for the specified event IDs.

Extended-attribute editing

This pattern applies when the following attribute is selected:

- Extended attribute

Specify a condition for the program-specific extended attribute.

Depending on the selected radio button, the item that can be specified differs.

When Attribute name is selected

Specify a condition for the program-specific extended attribute by using an attribute name.

In the Attribute name text box, you can enter a character string of no more than 32 bytes. The character string can contain upper-case alphabetic characters, numeric characters, and underscores (_). The first character must be an upper-case alphabetic character. If you enter a lower-case character as the first character, it is converted to an upper-case character. You cannot specify common information as an extended attribute.

When Item name is selected:

Specify a condition for the program-specific extended attribute by using an item name.

Specify a condition by selecting an item name from the Item name drop-down list. The displayed item names are program-specific extended attributes specified for the standard file and the extended file of the definition file for extended event attributes.

In the Condition text box, specify a character string of no more than 4 kilobytes when the character string is encoded by Shift-JIS if JP1/IM - Manager runs on Windows, or when the character string is encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX. Alphabetic characters are case sensitive.

You can specify a maximum of 100 character strings by using a comma (,) as a separator. However, only one character string can be specified if Regular expression is selected.

To specify a comma (,) or backslash (\) as an ordinary character, prefix it with a backslash (\). That is, to use a comma (,), enter \,. To use a backslash (\), enter \\. Note that \, and \\ each count as one byte.

From the drop-down list on the right, select a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Numeric value editing

This pattern applies when you select the following attributes:

- Registered reason

- Source process ID

- Source user ID

- Source group ID

Specify a decimal integer of no more than 4 kilobytes, using integers from 0 to 9 and hyphens (-). You can specify values in the range from -2,147,483,648 to 2,147,483,647.

You can specify a maximum of 100 numeric values by using a comma (,) as a separator.

From the drop-down list on the right, select Match or Does not match as a condition for the specified numeric value.

Apply

Click this button to apply the settings.

Message after the change

Specify the new message format for the display message change definition.

Enter a character string to be set for the changed display message. You can use any characters except control characters (0x00 to 0x1F and 0x7F to 0x9F).

If you use a variable to specify the message format, you can set the attribute information of the received JP1 event for the message. For details about the variables that can be specified, see Display message change definition file (jcochmsg.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The maximum size of the character string is 1,023 bytes when the character string is encoded by Shift-JIS if JP1/IM - Manager runs on Windows, or when the character string is encoded by the language encoding with which JP1/IM - Manager operates if JP1/IM - Manager runs on UNIX.

If a variable (such as $EVMSG) is used and the character string that includes the information of the converted variable exceeds 1,023 bytes, only the first 1,023 bytes are set for the message.

3.24 Preferences window

The Preferences window is used to specify whether the event list in the Event Console window is to be refreshed automatically. This window is also used to set the items to be displayed in the event list.

The Preferences window is displayed when the user chooses Options from the menu bar of the Event Console window and then chooses Preferences. The Preferences window has the Monitor Events, Event Attributes, and Command Execution pages.

Note

Some of the items displayed in the Preferences window change if linkage with BJEX or JP1/AS is enabled. For details on the contents of the Preferences window when linkage with BJEX or JP1/AS is enabled, see 3.44.6 Preferences window.

3.24.1 Monitor Events page

The Monitor Events page is used to specify event-monitoring related settings, such as whether to refresh the displayed information automatically, and the maximum number of events to be displayed.

The following figure shows the Monitor Events page.

Figure 3‒48: Monitor Events page

The following describes the items displayed in the Preferences window.

Automatic refresh

Specifies whether the information displayed on the Monitor Events and Severe Events pages is to be refreshed automatically.

Selecting Apply and specifying in seconds the refresh interval in the Interval text box enables automatic refreshes.

You can specify a value from 1 to 10,000 (seconds). The default is 5.

Selecting Do not apply disables automatic refresh.

Scroll buffer

Specifies the maximum number of events that can be displayed on the Monitor Events, Severe Events, and Search Events pages in the Event Console window.

You can specify a value from 10 to 2,000 (events). The default is 2,000.

The Scroll buffer value must be greater than the Num. of events to acquire at update value and the Num. of events to acquire in 1 search value.

If the Scroll buffer value is too small, the pages might not be able to display all the JP1 events.

If the current value is increased, the change is applied the next time the window is refreshed, whether automatically or manually.

If the specified value is too large when JP1/IM - View is started, the Event Console window might take longer to appear.

Before setting the scroll buffer, the user must estimate the amount of required memory for Central Console - View, and must check the amount of free space on the machine resource. For details about the formula for estimating the amount of required memory, see the Release Notes for JP1/IM - View.

Num. of events to acquire at update

Specifies the number of events that can be acquired from the event console service in one refresh operation for the Event Console window. A refresh operation is performed at the interval specified in the Automatic refresh area of the Preferences window, or whenever the user chooses View and then Refresh in the Event Console window.

When automatic refresh is enabled, refresh operations are repeated until no JP1 events remain in the event buffer of the event console service.

You can specify a value from 1 to 200 (events). The default is 20.

The Num. of events to acquire at update value must be smaller than the Scroll buffer value.

Num. of events to acquire in 1 search

Specifies the number of events that can be acquired in one event search operation.

You can specify a value from 1 to 2,000 (events). The default is 100.

The Num. of events to acquire in 1 search value must be smaller than the Scroll buffer value.

3.24.2 Event Attributes page

The Event Attributes page is used to specify the settings related to the display of events, such as display items and coloring.

The following figure shows the Event Attributes page.

Figure 3‒49: Event Attributes page (for version 10-50 or later)

Figure 3‒50: Event Attributes page (for version 10-10 or earlier)

The following describes the items displayed on the Event Attributes page.

Display items & order

Specifies the items that are to be displayed in the event list of the Event Console window.

The Display items & order list box displays the items that are displayed in the event list. The Available items list box displays the items that are not displayed in the event list. The items in the list boxes can be moved back and forth by using the -> and <- buttons.

The items in the event list are displayed in the same order used to display the items in the Display items & order list box. The user can change the display order of an item by selecting the item in the Display items & order list box and then clicking the Up or Down button.

In the Preferences window, the user can specify the display settings for the following items:

Event level, Registered time, Source host, User name, Message, Object type, Event ID, Start time, End time, Product name, Object name, Root object type, Root object name, Arrived time, Action, Occurrence, Serial number, Source process ID, Source user ID, Source group ID, Source user name, Source group name, Source serial number, Type, Action type, Original Severity Level#1, New Severity Level#1, Changed display message#2, New display message#2, Display message change definition name#2, Memo#3, Event source host name#4, Source IP address, Object ID, Return code, Relation Event serial number, Correlation event generation condition name, Suppressed event ID, Repeated event condition name, Monitoring ID, Monitoring name, Common exclude conditions group ID#5, Common exclude conditions group name#5, Common exclude conditions group target-for-exclusion#5, and Extended attribute#6

#1: Items that the user can set if the function for changing the severity level is enabled when the integrated monitoring database is used.

#2: An item that the user can set if the display message change function is enabled when the integrated monitoring database is used.

#3: An item that the user can set if the function for setting memo entries is enabled when the integrated monitoring database is used.

#4: An item that the user can set when the event source host mapping function is enabled in an environment that uses the integrated monitoring database.

#5: An item that the user can set when the integrated monitoring database is used.

#6: An item for which the user can set the program-specific extended attributes specified for the extended file of the definition file for extended event attributes.

Note that in the Event Console window and Related Events window, the event status is always displayed as the first item in the event list, regardless of the settings in the Preferences window.

Also note that if the function for displaying consolidated repeated events (Display most significant status) is enabled, the Summary Status column is displayed to the right of the Event status column. If this function is disabled, the Summary Status column continues to be displayed until the user logs in again.

Also note that if suppression of monitoring of repeated events or consolidated display of repeated events is enabled, the Summary Status column is displayed to the right of the Status column. If suppression of monitoring of repeated events or consolidated display of repeated events is disabled, the Summary Status column continues to be displayed until the user logs in again.

Display window

This option specifies whether to save the current configuration of the Event Console window when the user logs out from JP1/IM - View, and restore it when he or she logs in again. This includes the page that was last displayed in the Event Console window, the view filters selected in the Monitor Events and Severe Events pages, and the status of the view filter check boxes. To save these aspects of the Event Console window and restore them at login, select the Save the page that was displayed when the window was closed, and the application state of the view filter check box. The initial status of this check box is selected.

This check box is unavailable when:

The version of the connection-target JP1/IM - Manager is 10-10 or earlier

Column width

Specifies whether to save the column width of each item displayed in the event list of each page of the Event Console window when the user logs out from JP1/IM - View.

The column width of each item displayed in the event list can be changed by dragging. A change in a column width on one page (for example, Monitor Events) is applied to the other two pages (for example, Severe Events and Search Events). When the Save the status of the window when closing check box is selected, the column width status is saved when the user logs out.

Display font

Specifies in points the font size of JP1 events listed in the Event Console window. The specifiable value range is from 12 to 72.

Coloring

Specifies whether to add background colors to specific events displayed on the Monitor Events, Severe Events, and Search Events pages of the Event Console window. Background colors can be added to events that have the severity levels Emergency, Alert, Critical, Error, and Warning.

Select the Enable check box to add background colors to the Monitor Events and Search Events pages. To add background colors to the Severe Events page, select the Include the Severe Events page radio button. The Enable check box is selected by default. In addition, the initial status of the Include the Severe Events page radio button is selected.

In the following cases, the Include the Severe Events page radio button is unavailable:

When the version of JP1/IM - Manager to which you are connected is 10-50 or later and the Enable check box of the Coloring area is cleared

When the version of JP1/IM - Manager to which you are connected is 10-10 or earlier

For details about background colors, see 3.1 Overview of the Event Console window.

Display most significant status

Specifies whether to use consolidated display of repeated events.

Clicking the OK button in the Preferences window completes the consolidation of events being consolidated. If you are using the repeated event monitoring suppression function, the Enable check box is unavailable and cannot be selected on this page.

Enable

When this check box is selected, repeated events are consolidated. Consolidation is enabled for the events received after the settings in the Preferences window are applied. The events received before the settings are applied are not consolidated.

By default, this check box is not selected.

Timeout time

Specifies the number of seconds used as the timeout value for consolidating repeated events. You can specify a value from 1 to 3,600 (seconds). The default is 60.

When the difference between the arrival time of a consolidation start event and the arrival times of received events reaches the timeout value, the consolidation is completed.

Specified display event period

Specifies whether to use the function for displaying events that occurred during a specified period.

Display

When this check box is selected, events occurring during the specified period are displayed. If this check box is selected, the Use specified display event period check box appears on the Monitor Events page and the Severe Events page.

Base time

Specifies a time for displaying JP1 events. As the hour, you can specify a value from 00 to 23. The default value is 09 hours. As the minutes, you can specify a value from 00 to 59. The default value is 00 minutes.

Display period

Specifies a period for displaying JP1 events. You can specify a value from 1 to 31 (days). The default is 1 day.

3.24.3 Command Execution page

The Command Execution page is used to set the maximum number of lines that display command execution results.

The following figure shows the Command Execution page.

Figure 3‒51: Command Execution page

The following describes the items displayed on the Command Execution page.

Lines of execution results to display

Specifies the maximum number of lines available for displaying execution results in the Execute Command window.

You can specify a value from 100 to 10,000 (lines). The default is 10,000.

This area is enabled only when the logged-in user has JP1_Console_Admin permission or JP1_Console_Operator permission.

3.25 Event Search Conditions window

The Event Search Conditions window is used to specify the search conditions for JP1 events. The search results are displayed on the Search Events page of the Event Console window. The Event Search Conditions window is displayed when the user chooses View from the menu bar of the Event Console window and then chooses Search Events. The last search conditions specified in the Event Search Conditions window are saved and displayed when the window is displayed the next time.

When the user specifies search conditions and clicks the OK button, the specified conditions are converted into a filter condition statement that JP1/IM - View uses to perform the search. The maximum length of the filter condition statement is 64 KB. However, when the event service version of the host to be searched is 06-00 or earlier, the maximum length is 4 KB. If the filter condition statement is longer than the maximum length, an error dialog box displaying the message KAVB0246-E appears when the OK button is clicked. If the error dialog box appears, the filter condition settings must be reviewed. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

If no conditions (items under Conditions) have been specified for one or more of the pass-conditions groups set in this window, all JP1 events will be displayed (acquired). On the other hand, if no conditions (items under Conditions) have been specified for one or more of the exclusion-conditions groups set in this window, no JP1 events will be displayed (acquired). At least one condition must be specified for each condition group in order to filter events.

Restrictions on the search function by JP1/Base versions

If the version of the JP1/Base event service on the host to be searched is 06-51 or earlier, the following searches cannot be performed:

- A Search with Regular expression selected

If the version of the JP1/Base event service on the host to be searched is 06-00 or earlier, in addition to the above search, the following searches cannot be performed:

- A Search with Is contained or Is not contained selected

- A Search with multiple event statuses selected on the Severe Events page

If the version of the JP1/Base event service on the host to be searched is 08-00 or earlier, a search with exclusion-conditions specified cannot be performed.

Note

Some of the items displayed in the Event Search Conditions window change if linkage with BJEX or JP1/AS is enabled. For details on the contents of the Event Search Conditions window when linkage with BJEX or JP1/AS is enabled, see 3.44.7 Event Search Conditions window.

For information about the conditions required when searching for events, see 4.6.2 Event search conditions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The following figure shows an example of the Event Search Conditions window in an environment that does not use the integrated monitoring database:

Figure 3‒52: Event Search Conditions window

The following figure shows an example of the Event Search Conditions window in an environment that uses the integrated monitoring database:

Figure 3‒53: Event Search Conditions window (when using integrated monitoring database)

The following describes the items displayed in the Event Search Conditions window.

Search object

This area appears in environments that use the integrated monitoring database. You can specify the integrated monitoring database or the event database as the target of the search. The last database you searched is selected by default. If you are conducting a search for the first time, Integrated monitoring database is selected.

Search host

In this text box, specify one of the following values:

Name of the host on which JP1 events will be searched for (search-target event server name)

(If the function for restricting reference permissions and operation permissions is enabled (ON is set for the -bizmonmode option of the jcoimdef command)) Name of the host belonging to a business group that the logged-in JP1 user can view (host name (domain name) managed by IM configuration management)

For details about the jcoimdef command, see jcoimdef in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

IPv4 address

IPv6 address

The default is the name of the connected host. Note that when the integrated monitoring database is used, if the Event database radio button is selected in the Search object area, the host name specified last time as the name of the host to be searched is displayed. In addition, if the Integrated monitoring database radio button is selected in the Search object area, the user cannot specify Search host. Instead, the name of the host to which the user is logged in is specified.

If the user changes the radio button selection from Event database to Integrated monitoring database, and then selects the Event database radio button again, the name of the host specified the first time the user selected the Event database radio button is displayed in the Search host area.

Search direction

Specifies the direction of the JP1 event search.

When Past direction is selected, JP1/IM - View searches the event database (or the integrated monitoring database if the user has selected the Integrated monitoring database radio button in the Search object area) from the last (most recent) JP1 event to the first (oldest) JP1 event.

When Future direction is selected, JP1/IM - View searches the event database (or the integrated monitoring database if the user has selected the Integrated monitoring database radio button in the Search object area) from the first (oldest) JP1 event to the last (most recent) JP1 event.

The default is Past direction.

Show List (or Hide List)

Clicking the Show List button displays the list of condition groups. When the list is displayed, the button changes to the Hide List button, which, if clicked, hides the list.

Pass-conditions groups

This area displays the pass-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of five condition groups can be set. When five condition groups have been specified, the Add and Copy buttons are disabled.

Exclusion-conditions group

This area displays the exclusion-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of five condition groups can be set. When five condition groups have been specified, the Add and Copy buttons are disabled.

Add

Clicking this button adds a new condition group. For pass-conditions groups, the default name Condition group n (n is a number) is assigned to the new pass-conditions group that is added. For exclusion-conditions groups, the default name Exclusion-conditions group n (n is a number) is assigned to the new exclusion-conditions group that is added. Each time a new condition group is added, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Copy

Clicking this button copies the selected condition group. When the user selects a condition group and clicks this button, a new condition group in which the same conditions as those defined in the selected condition group is created. The new condition group that is created is assigned the default name Copy original-condition-group-name, and is added to the list of condition groups. After creating a copy of a condition group, if the user creates another copy of the same condition group, a number is added after the string Copy in CopyN original-condition-group-name (N is a number). The first number used is 2, which is incremented each time the same condition group is copied. Note that each time a new condition group is added to the list, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Delete

Clicking this button deletes the selected condition group. When this button is clicked, a message dialog box displaying the following message appears:

KAVB0257-I

Clicking the Yes button in the message dialog box deletes the selected condition group.

Condition group name

This box is used to specify the name of a condition group.

If the user selects an existing condition group in the Pass-conditions groups or Exclusion-conditions group area and specifies a new name, the condition group is renamed. The same name cannot be specified for a pass-conditions group and an exclusion-conditions group.

If the user attempts to specify a condition group name that already appears in the Pass-conditions groups or Exclusion-conditions group area, a message dialog box displaying the following message appears:

KAVB0256-E The specified condition group name already exists.

Clear

Clicking this button clears all condition settings displayed under Conditions. If no conditions are listed, this button is disabled.

Read From Selected Event

Clicking this button applies the attribute values of the JP1 event selected in the Event Console window to the corresponding items under Conditions. The following describes how the attribute values are applied:

When an event attribute value includes a control character (such as a linefeed or tab character)

The part before the first control character is applied. If an option condition can be specified for the event attribute, First characters is selected.

When an event attribute value does not include a control character

The entire event attribute value is applied. If an option condition can be specified for the event attribute, Match is selected.

If the information of the selected JP1 event is mapped in the Event-Information Mapping Definitions window, the attribute values for the display items and program-specific extended attribute values that have been mapped are not applied. For details about the Event-Information Mapping Definitions window, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Read Suppressed Event ID From Selected Event

If the repeated event monitoring suppression function is enabled, the Read Suppressed Event ID From Selected Event button is displayed.

If the JP1 event selected in the Event Console window is a repeated event, the Read Suppressed Event ID From Selected Event button is enabled.

When the Read Suppressed Event ID From Selected Event button is clicked, the Suppressed event ID conditions are set as follows:

The check box is selected.

The suppressed event ID of the JP1 event selected in the Event Console window (E.JP1_IMSUPPRESS_ID) is set in the text box.

Match is selected as an optional condition.

When the Read Suppressed Event ID From Selected Event button is clicked, the conditions other than Suppressed event ID are set as follows:

The check boxes are cleared.

If the event attribute value includes control characters such as line breaks and tabs:

The string up to the first control character is used as the value of the condition. If an optional condition can be specified for the event attribute, First characters is selected.

If the event attribute value does not include control characters such as line breaks and tabs:

The entire event attribute value is used. If an optional condition can be specified for the event attribute, Match is selected.

Note that if the information about the selected JP1 event is mapped in the event-information mapping definitions, the attribute values and program-specific extended attribute values of the mapped display item are not entered into the conditions list. For details about the event-information mapping definitions, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Event source host name

The Event source host name field appears if the event source host mapping function is enabled.

This field specifies the host name of the host where the event that triggered the JP1 event occurred. How to specify multiple hosts is the same as the Source host field.

Alphabetic characters are case sensitive. However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (unless Regular expression is selected in the drop-down list on the right).

From the drop-down list on the right, you can select a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If the integrated monitoring database and the IM Configuration Management database are enabled, a business group name in path format can be specified as an event source host name. In this case, Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, business group names in path format are treated as host names.

For details on the event source host mapping function, see 4.9 Mapping of the event source hosts in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Source host

Specifies the name of a host (event server name) that issues a JP1 event. Multiple host names require a comma as a separator. A maximum of 100 host names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive. However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (if Regular expression is not selected in the drop-down list on the right).

From the drop-down list on the right, you can select a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is selected, only one condition can be set.

For Source host, if the integrated monitoring database and the IM Configuration Management database are enabled, a business group name can also be specified in path format. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

Event level

Specifies the severity levels of the JP1 events to be defined as severe events from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

Object type

Specifies the object type of a JP1 event. The character string can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Object name

Specifies the object name of a JP1 event. Multiple object names require a comma as a separator. A maximum of 100 object names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is selected, only one condition can be set.

Root object type

Specifies the root object type of a JP1 event. The root object type can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object name

Specifies the root object name of a JP1 event.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Occurrence

Specifies the occurrence type of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

User name

Specifies the user name of a JP1 event.

Multiple user names require a comma as a separator. A maximum of 100 user names can be specified. If a user name that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is selected, only one condition can be set.

Message

Specifies the message text of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression. We recommend First characters or Is contained. If Regular expression is selected, make sure that control characters used in the message text are not included in the expression.

Product name

Specifies the name of the program that issues a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID

Specifies the event ID of a JP1 event. Multiple event IDs require a comma as a separator.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match and Does not match.

Start timeframe

Specifies the search range for JP1 events as a timeframe based on a start time. The search range is determined by using this base time and either a period or a specific time.

To use a period to specify the search range, the user first enters the base time after From:. Next, the user selects Period: and specifies a time period (in minutes, hours, or days) before or after the base time.

To use a time to specify the search range, the user first enters the base time after From:. Next, the user selects Time: and specifies a date and time.

The current date and time can be set as the base time by clicking the Current Time button.

End timeframe

Specifies the search range for JP1 events as a timeframe based on an end time. The search range is determined by using this base time and either a period or a specific time.

To use a period to specify the search range, the user first enters the base time after From:. Next, the user selects Period: and specifies a time period (in minutes, hours, or days) before or after the base time.

To use a time to specify the search range, the user first enters the base time after From:. Next, the user selects Time: and specifies a date and time.

The current date and time can be set as the base time by clicking the Current Time button.

Registered timeframe

Specifies the search range for JP1 events as a timeframe based on the time at which JP1 events were registered in the event database on the event-issuing host. The search range is determined by using this base time and either a period or a specific time.

To use a period to specify the search range, the user first enters the base time after From:. Next, the user selects Period: and specifies a time period (in minutes, hours, or days) before or after the base time.

To use a time to specify the search range, the user first enters the base time after From:. Next, the user selects Time: and specifies a date and time.

The current date and time can be set as the base time by clicking the Current Time button.

Arrived timeframe

Specifies the search range for JP1 events as a timeframe based on the times at which JP1 events arrived at the host where the search will be performed. The search range is determined by using this base time and either a period or a specific time.

To use a period to specify the search range, the user first enters the base time after From:. Next, the user selects Period: and specifies a time period (in minutes, hours, or days) before or after the base time.

To use a time to specify the search range, the user first enters the base time after From:. Next, the user selects Time: and specifies a date and time.

The current date and time can be set as the base time by clicking the Current Time button.

Status

Specifies the event statuses of JP1 events as search conditions. Multiple statuses can be specified. If the user selects Processed, only events whose status is set to Processed are retrieved. If the user selects Unprocessed, only events whose status is set to Unprocessed are retrieved. If the user selects Processing, only events whose status is set to Processing are retrieved. If the user selects Held, only events whose status is set to Held are retrieved.

Action

For JP1 events for which an automated action is defined, this item enables a search based on whether the defined automated action has been executed.

Extended attribute

When the user specifies specific extended attribute values as search conditions, clicking the Configure button displays the Event Search Conditions (Program-Specific Information in Extended Attribute) window.

Memo

If the function for setting memo entries is enabled, the Memo area is displayed. This area is unavailable if you select the event database in the Search object area.

In this area, the user specifies memo entries for JP1 events.

Alphabetic characters are case sensitive.

From the drop-down list on the right, select a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

For details on the function for setting memo entries, see 4.11 Setting memo entries in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

New severity level

If the function for changing the severity level is enabled, the New severity level area is displayed. This area is unavailable if the event database is selected in the Search object area.

In this area, you can specify whether to include JP1 events with new severity levels in the scope of the search. If you select the Target radio button, the search targets JP1 events whose severity level has changed. If you select the the Not target radio button, the search targets JP1 events whose severity level has not changed.

For details on the function for changing the severity level, see 5.13 Setting the severity changing function in the JP1/Integrated Management 3 - Manager Configuration Guide.

Original severity level

If the function for changing the severity level is enabled, the Original severity level area is displayed. This area is unavailable if the event database is selected in the Search object area.

In this area, you can specify the severity level of the JP1 event before the level was changed. You can select Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

New display message

If you enable the display message change function, the New display message area is displayed.

In addition, this area is always unavailable if you have not used the jimdbupdate command to update the IM database after performing an upgrade installation from version 10-50 or earlier.

Specify the condition whether to display the messages that are changed or the messages that are not changed. If you select the Target radio button, JP1 events whose messages to be displayed are changed, are to be searched. If you select the Not target radio button, JP1 events whose messages to be displayed are not changed, are to be searched.

For details about the display message change function, see 5.14 Setting the display message change function in the JP1/Integrated Management 3 - Manager Configuration Guide.

Changed display message

If you enable the display message change function, the Changed display message area is displayed.

In addition, this area is always unavailable if you have not used the jimdbupdate command to update the IM database after performing an upgrade installation from version 10-50 or earlier.

Specify the changed display message text for JP1 events.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

Repeated event

If the repeated event monitoring suppression function is enabled, the Repeated event area is displayed. This area is unavailable if the event database is selected in the Search object area.

In this area, you can specify whether to include repeated events in the search results. When you select the check box, the Target and Not target radio buttons become available. If you do not select the check box, the radio buttons remain unavailable. This area does not appear if you log in to an instance of JP1/IM - Manager in which the repeated event monitoring suppression function is disabled.

Specify whether to include repeated events in the search results. To include repeated events in the search results, select the Target radio button. To exclude repeated events, select the Not target radio button.

For details on the repeated event monitoring suppression function, see 5.3 Setting monitoring of repeated events to be prevented in the JP1/Integrated Management 3 - Manager Configuration Guide.

Suppressed event ID

If the repeated event monitoring suppression function is enabled, Suppressed event ID is displayed. This item is disabled if the event database is selected as the search-target database.

Specify the suppressed event ID of a JP1 event (E.JP1_IMSUPPRESS_ID). The same suppressed event ID is set for the repeated events that are consolidated into a single consolidation event. Therefore, you can specify a suppressed event ID to search for the repeated events related to a specific repeated event.

You can also specify multiple suppressed event IDs by using a comma (,) as a separator. You can specify a maximum of 100 suppressed event IDs. You cannot use a line break or tab.

From the list box on the right of this item, select one of the following options as the search condition to be applied to the specified character string: First characters, Match, Does not match, Is contained, Is not contained, or Regular expression. Note that you cannot specify multiple suppressed event IDs if you select Regular expression.

3.26 Event Search Conditions (Program-Specific Information in Extended Attribute) window

The Event Search Conditions (Program-Specific Information in Extended Attribute) window is used to set program-specific extended attributes for JP1 events as filter conditions.

This window is displayed when the user clicks the Configure button in the Extended attribute area of the Event Search Conditions window, the Severe Event Definitions window, the Event Acquisition Settings window, the Common Exclusion-Conditions Settings window, the Settings for View Filter window, or the Detailed Settings for Event Receiver Filter window. The following figure shows an example of the Event Search Conditions (Program-Specific Information in Extended Attribute) window.

Figure 3‒54: Event Search Conditions (Program-Specific Information in Extended Attribute) window

The following describes the items displayed in the Event Search Conditions (Program-Specific Information in Extended Attribute) window.

Conditions

This area displays a list of program-specific extended attribute conditions that are already set. Attribute names, attribute values, and conditions are listed.

A program-specific extended attribute condition is displayed for each line. A maximum of five conditions can be set.

When a program-specific extended attribute condition is double-clicked, the Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window opens.

Add

Clicking the Add button allows the user to add a new program-specific extended attribute condition. When the button is clicked, the Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window opens.

Edit

To edit an existing program-specific extended attribute condition that appears in the Conditions list, select the condition in the list and then click the Edit button. When the button is clicked, the Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window opens.

Delete

To delete a program-specific extended attribute condition that appears in the Conditions list, select the condition in the list and then click the Delete button.

3.27 Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window

The Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window is used to set a program-specific extended attribute condition as a filter condition.

This window can be used to set only one program-specific extended attribute condition.

As the program-specific extended attribute condition, one extended attribute name and one attribute value can be set.

This window is displayed when the user clicks the Add or Edit button in the Event Search Conditions (Program-Specific Information in Extended Attribute) window or when the user double-clicks a program-specific extended attribute condition in the Conditions list.

The following figure shows an example of the Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window.

Figure 3‒55: Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window

The following describes the items displayed in the Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window.

Attribute name

Specifies the name of a program-specific extended attribute.

This area becomes available if you select the Attribute name radio button.

The attribute name specified in this area can have a maximum of 32 bytes consisting of upper-case alphabetic characters, numeric characters, and underscores (_). The name must begin with an upper-case alphabetic character.

Only one condition can be set for one attribute.

Item name

Specifies the condition of a program-specific extended attribute by using an item name.

This area becomes available if you select the Item name radio button.

Specify the condition by selecting an item name from the Item name drop-down list. The displayed item names are program-specific extended attributes specified for the standard file and the extended file of the definition file for extended event attributes.

Note on specifying the suppressed event ID:

The suppressed event ID (E.JP1_IMSUPPRESS_ID) is not displayed in the Item name drop-down list if all of the following conditions exist:

The version of JP1/IM - Manager and JP1/IM - View is 11-01 or later.

The repeated event monitoring suppression function is enabled.

The Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window was opened from the Event Search Conditions window or the Settings for View Filter window.

To specify the suppressed event ID as an event condition in the Event Search Conditions window or the Settings for View Filter window, specify the suppressed event ID for Suppressed event ID in that window.

Attribute value

Specifies the program-specific extended attribute.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

3.28 Settings for View Filter window

The Settings for View Filter window is used to set the types of events to be displayed when a view filter is used.

The settings in this window take effect when:

You select Apply Filter Settings from the View menu in the Event Console window.

You select the View filter check box in the Monitor Events or Severe Events page of the Event Console window.

To display the Settings for View Filter window:

Select View Filter Settings from the View menu in the Monitor Events or Severe Events page of the Event Console window.

Click the View Filter Settings button on the Monitor Events or Severe Events page of the Event Console window.

In the View List of Filters window, the user clicks the Add button.

In the View List of Filters window, the user selects a view filter and then clicks the Edit button.

When the user specifies filter conditions and clicks OK in the Settings for View Filter window that has not been opened from the View List of Filters window, the specified conditions are converted into a filter condition statement. In this case, the filter condition statement takes effect immediately#. The maximum total size of filter condition statements is 1 MB for each JP1 user. If the creation of a new filter condition statement causes the maximum size to be exceeded, an error dialog box displaying the message KAVB0246-E appears when the OK button is clicked. If the error dialog box appears, the filter condition settings must be reviewed. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

#: When the Settings for View Filter window has been opened from the View List of Filters window, the settings are applied when the OK button is clicked in the View List of Filters window.

If no conditions (items under Conditions) have been specified for one or more of the pass-conditions groups set in this window, all JP1 events will be displayed (acquired). On the other hand, if no conditions (items under Conditions) have been specified for one or more of the exclusion-conditions groups set in this window, no JP1 events will be displayed (acquired). At least one condition must be specified for each condition group in order to filter events.

The following figure shows an example of the Settings for View Filter window.

Figure 3‒56: Settings for View Filter window

Note

Some of the items displayed in the Settings for View Filter window change if linkage with BJEX or JP1/AS is enabled. For details on the contents of the Settings for View Filter window when linkage with BJEX or JP1/AS is enabled, see 3.44.8 Filter condition definition windows.

The following describes the items displayed in the Settings for View Filter window.

Filter name

Specifies the name of a view filter. The name specified in the box can be from 1 to 50 bytes.

If an existing view filter is selected in the View list of filters area when you change the name in this text box, the existing view filter is renamed. If you specify a name of a view filter that already appears in the View list of filters area, a dialog box displaying the following message appears:

KAVB0259-E The specified filter name already exists.

Show List (or Hide List)

Clicking the Show List button displays the list of condition groups. When the list is displayed, the button changes to the Hide List button, which, if clicked, hides the list.

Pass-conditions groups

This area displays the pass-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of five condition groups can be set. When five condition groups have been specified, the Add and Copy buttons are disabled.

Exclusion-conditions groups

This area displays the exclusion-conditions groups. If the user selects a condition group from the list, the name of the condition group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of five condition groups can be set. When five condition groups have been specified, the Add and Copy buttons are disabled.

Add

Clicking this button adds a new condition group. For pass-conditions groups, the default name Condition group n (n is a number) is assigned to the new pass-conditions group that is added. For exclusion-conditions groups, the default name Exclusion-conditions group n (n is a number) is assigned to the new exclusion-conditions group that is added. Each time a new condition group is added, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Copy

Clicking this button copies the selected condition group. When the user selects a condition group and clicks this button, a new condition group in which the same conditions as defined those in the selected condition group is created. The new condition group that is created is assigned the default name Copy original-condition-group-name, and is added to the list of condition groups. After creating a copy of a condition group, if the user creates another copy of the same condition group, a number is added after the string Copy in CopyN original-condition-group-name (N is a number). The first number used is 2, which is incremented each time the same condition group is copied. Note that, each time a new condition group is added to the list, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Delete

Clicking this button deletes the selected condition group. When this button is clicked, a message dialog box displaying the following message appears:

KAVB0257-I

Clicking the Yes button in the message dialog box deletes the selected condition group.

Condition group name

This box is used to specify the name of a condition group.

If the user selects an existing condition group in the Pass-conditions groups or Exclusion-conditions group area and specifies a new name, the condition group is renamed. The same name cannot be specified for a pass-conditions group and an exclusion-conditions group.

If the user attempts to specify a condition group name that already appears in the Pass-conditions groups or Exclusion-conditions group area, a message dialog box displaying the following message appears:

KAVB0256-E The specified condition group name already exists.

Clear

Clicking this button clears all condition settings displayed under Conditions.

Read From Selected Event

Clicking this button applies the attribute values of the JP1 event selected in the Event Console window to the corresponding items under Conditions. The following describes how the attribute values are applied:

When an event attribute value includes a control character (such as a linefeed or tab character)

The part before the first control character is applied. If an option condition can be specified for the event attribute, First characters is selected.

When an event attribute value does not include a control character

The entire event attribute value is applied. If an option condition can be specified for the event attribute, Match is selected.

If the information of the selected JP1 event is mapped in the Event-Information Mapping Definitions window, the attribute values for the display items and program-specific extended attribute values that have been mapped are not applied. For details about the Event-Information Mapping Definitions window, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Read Suppressed Event ID From Selected Event

If the repeated event monitoring suppression function is enabled, the Read Suppressed Event ID From Selected Event button is displayed.

If the JP1 event selected in the Event Console window is a repeated event, the Read Suppressed Event ID From Selected Event button is enabled.

When the Read Suppressed Event ID From Selected Event button is clicked, the Suppressed event ID conditions are set as follows:

The check box is selected.

The suppressed event ID of the JP1 event selected in the Event Console window (E.JP1_IMSUPPRESS_ID) is set in the text box.

Match is selected as an optional condition.

When the Read Suppressed Event ID From Selected Event button is clicked, the conditions other than Suppressed event ID are set as follows:

The check boxes are cleared.

If the event attribute value includes control characters such as line breaks and tabs:

The string up to the first control character is used as the value of the condition. If an optional condition can be specified for the event attribute, First characters is selected.

If the event attribute value does not include control characters such as line breaks and tabs:

The entire event attribute value is used. If an optional condition can be specified for the event attribute, Match is selected.

Note that if the information about the selected JP1 event is mapped in the event-information mapping definitions, the attribute values and program-specific extended attribute values of the mapped display item are not entered into the conditions list. For details about the event-information mapping definitions, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Event source host name

The Event source host name appears when the event source host mapping function is enabled.

Specifies the name of the host on which an event that triggered issuance of a JP1 event occurred. How to specify multiple hosts is the same as the Source host field.

Alphabetic characters are case sensitive. However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (if Regular expression is not selected in the drop-down list on the right).

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

For Event source host name, if the integrated monitoring database and the IM Configuration Management database are enabled, a business group name can also be specified in path format. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

For details on the event source host mapping function, see 4.9 Mapping of the event source hosts in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Source host

Specifies the name of a host (event server name) that issues a JP1 event. Multiple host names require a comma as a separator. A maximum of 100 host names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (if Regular expression is not selected in the drop-down list on the right).

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

For Source host, if the integrated monitoring database and the IM Configuration Management database are enabled, a business group name can also be specified in path format. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

Event level

Specifies the severity levels of the JP1 events to be defined as severe events from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

Object type

Specifies the object type of a JP1 event. The character string can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Object name

Specifies the object name of a JP1 event. Multiple object names require a comma as a separator. A maximum of 100 object names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified characters string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object type

Specifies the root object type of a JP1 event. The root object type can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object name

Specifies the root object name of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Occurrence

Specifies the occurrence type of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

User name

Specifies the user name of a JP1 event.

Multiple user names require a comma as a separator. A maximum of 100 user names can be specified. If a user name that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Message

Specifies the message text of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression. We recommend First characters or Is contained. If Regular expression is selected, make sure that control characters used in the message text are not included in the expression.

Product name

Specifies the name of the program that issues a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID

Specifies the event ID of a JP1 event. Multiple event IDs require a comma as a separator.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match and Does not match.

Status

Specifies the event statuses of JP1 events as filter conditions. Multiple statuses can be specified. If the user selects Processed, only events whose status is set to Processed are retrieved. If the user selects Unprocessed, only events whose status is set to Unprocessed are retrieved. If the user selects Processing, only events whose status is set to Processing are retrieved. If the user selects Held, only events whose status is set to Held are retrieved.

Action

For JP1 events for which an automated action is defined, this item enables a search based on whether the defined automated action has been executed.

Extended attribute

Displays the window for setting the condition whether to use the program-specific extended attribute value to perform filtering. To set the condition, select the Extended attribute check box. If you select this check box, the Configure button becomes available. If you click the Configure button, the Event Search Conditions (Program-Specific Information in Extended Attribute) window is displayed, and you can set the condition.

For details about this window, see 3.26 Event Search Conditions (Program-Specific Information in Extended Attribute) window.

When the integrated monitoring database is used

The following items are displayed when the integrated monitoring database is used:

Memo

If the function for setting the memo entries is enabled, the Memo area is displayed.

In this area, the user specifies the memo entries for JP1 events.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified characters string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

For details on the function for setting memo entries, see 4.11 Setting memo entries in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

New severity level

If the function for changing the severity level has been enabled, the New severity level column is displayed.

The user specifies whether changes to the severity level are to be displayed. If the Target radio button is selected, JP1 events whose severity level has changed are displayed. If the Not target radio button is selected, JP1 events whose severity level has not changed are displayed.

For details on the severity changing function, see 5.13 Setting the severity changing function in the JP1/Integrated Management 3 - Manager Configuration Guide.

Original severity level

If the function for changing the severity level is enabled, the Original severity level area is displayed.

The user specifies the severity level of JP1 events in effect before the level was changed. The severity levels that can be selected are Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

New display message

If you enable the display message change function, the New display message area is displayed.

In addition, if you have not used the jimdbupdate command to update the IM database after performing an upgrade installation from version 10-50 or earlier, you cannot specify the setting.

Specify the condition whether to display the messages that are changed or the messages that are not changed. If you select the Target radio button, JP1 events whose messages to be displayed are changed, are displayed. If you select the Not target radio button, JP1 events whose messages to be displayed are not changed, are displayed.

For details about the display message change function, see 5.14 Setting the display message change function in the JP1/Integrated Management 3 - Manager Configuration Guide.

Changed display message

If you enable the display message change function, the Changed display message area is displayed.

Specify the changed display message text for JP1 events.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

Repeated event

Specifies whether to include repeated events in the display targets.

If this check box is selected, the Target and Not target radio buttons are enabled, and either of them can be selected. If this check box is cleared, neither of these radio buttons can be selected. Note that this area does not appear if the user logs in to a JP1/IM - Manager in which suppression of monitoring of repeated events is disabled.

Select either Target or Not target. Select Target to include repeated events in the display targets. Select Not target to exclude repeated events from the display targets.

Suppressed event ID

If the repeated event monitoring suppression function is enabled, Suppressed event ID is displayed.

Specify the suppressed event ID of a JP1 event (E.JP1_IMSUPPRESS_ID). The same suppressed event ID is set for the repeated events that are consolidated into a single consolidation event. Therefore, you can specify a suppressed event ID to search for the repeated events related to a specific repeated event.

You can also specify multiple suppressed event IDs by using a comma (,) as a separator. You can specify a maximum of 100 suppressed event IDs. You cannot use a line break or tab.

From the list box on the right of this item, select one of the following options as the search condition to be applied to the specified character string: First characters, Match, Does not match, Is contained, Is not contained, or Regular expression. Note that you cannot specify multiple suppressed event IDs if you select Regular expression.

3.29 View List of Filters window

The View List of Filters window displays a list of view filters. The list you create in this window appears in the Filter name drop-down list on the Monitor Events and Severe Events pages of the Event Console window.

The View List of Filters window is displayed when the user chooses View from the menu bar of the Event Console window and then View List of Filters.

When the user sets filter conditions in the Settings for View Filter window and clicks the OK button in the View List of Filters window, the filter conditions are converted into a filter condition statement, which then takes effect. The maximum total size of filter condition statements is 1 MB for each JP1 user. If the creation of a new filter condition statement causes the maximum size to be exceeded, an error dialog box displaying the message KAVB0246-E appears when the OK button is clicked. If the error dialog box appears, the filter condition settings must be reviewed. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

The following figure shows an example of the View List of Filters window.

Figure 3‒57: View List of Filters window

The following describes the items displayed in the View List of Filters window.

View list of filters

This area displays a list of view filters.

A maximum of 50 view filters can be set for each JP1 user. When 50 view filters have been set, the Add and Copy buttons are disabled.

Up

Clicking this button moves the view filter selected in the list up one line. You can improve the usability of the Filter name drop-down lists in the Monitor Events and Severe Events pages by moving frequently used view filters to the top of the list.

Down

Clicking this button moves the view filter selected in the list down one line.

Add

Clicking this button allows the user to add a new view filter. When this button is clicked, the Settings for View Filter window appears.

Edit

To edit a view filter that appears in the View list of filters list, selects the view filter and then click the Edit button. The Settings for View Filter window opens, where the user can edit the selected filter.

Copy

Clicking this button copies the selected view filter. When the user selects a view filter and then clicks the Copy button, a new view filter in which the same conditions as those defined in the selected filter is created and added to the list in the View list of filters area. The new view filter that is created is assigned the default name Copy original-filter-name, and is added to the list. After creating a copy of a view filter, if the user creates another copy of the same view filter, a number is added after the string Copy in CopyN original-filter-name (N is a number). The first number used is 2, which is incremented each time the same view filter is copied. The user can rename a view filter by clicking the Edit button.

Delete

Clicking this button deletes the selected view filter. When this button is clicked, a message dialog box displaying the following message appears:

KAVB0503-I

Clicking the Yes button in this dialog box deletes the selected event acquisition filter from the list in the View list of filters area.

3.30 Settings for Event Receiver Filter window

The Settings for Event Receiver Filter window is used to prohibit specific users from monitoring specific JP1 events. A maximum of 128 user filters can be set.

To display the Settings for Event Receiver Filter window, the user must have JP1_Console_Admin permission. If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The window is displayed when the user chooses Options from the menu bar of the Event Console window and then Event Receiver Filter Settings.

When the Apply button is clicked in the Settings for Event Receiver Filter window after filter conditions have been set in the Detailed Settings for Event Receiver Filter window, the filter conditions are converted into a filter condition statement. The statement takes effect immediately. The maximum total size of filter condition statements is 1 MB. If the creation of a new filter condition statement causes the maximum size to be exceeded, an error dialog box displaying the message KAVB0246-E appears when the OK button is clicked. If the error dialog box appears, the filter condition settings must be reviewed. For details about how to estimate the length of a filter condition statement, see the Release Notes for JP1/IM - View.

The following figure shows an example of the Settings for Event Receiver Filter window.

Figure 3‒58: Settings for Event Receiver Filter window

The following describes the items displayed in the Settings for Event Receiver Filter window.

Specifications

This area displays a list of event receiver filters that are already set. Each line of the list displays the name of a filter and the names of the users to which the filter applies.

A maximum of 128 event receiver filters can be set for each system (one instance of JP1/IM - Manager). When 128 event receiver filters have been set, the Add button is disabled.

Add

Clicking this button allows the user to add a new event receiver filter. When this button is clicked, the Detailed Settings for Event Receiver Filter window appears.

Edit

To edit an existing existing event receiver filter that appears in the Specifications list, select the filter in the list and then click the Edit button. The Detailed Settings for Event Receiver Filter window opens, where the user can edit the settings of the selected filter.

Delete

To delete an event receiver filter that appears in the Specifications list, select the filter in the list and then click the Delete button.

3.31 Detailed Settings for Event Receiver Filter window

The Detailed Settings for Event Receiver Filter window is used to specify the filter conditions of an event receiver filter. This window is displayed by performing the following operations:

In the Settings for Event Receiver Filter window, click the Add or Edit button.

In the Settings for Event Receiver Filter window, select an item in the Specifications list, and then double-click the item.

If no conditions (items under Conditions) have been specified for one or more of the pass-conditions groups set in this window, all JP1 events will be displayed (acquired). On the other hand, if no conditions (items under Conditions) have been specified for one or more of the exclusion-conditions groups set in this window, no JP1 events will be displayed (acquired). At least one condition must be specified for each condition group in order to filter events.

The following figure shows an example of the Detailed Settings for Event Receiver Filter window.

Figure 3‒59: Detailed Settings for Event Receiver Filter window

Note

Some of the items displayed in the Detailed Settings for Event Receiver Filter window change if linkage with BJEX or JP1/AS is enabled. For details on the contents of the Detailed Settings for Event Receiver Filter window when linkage with BJEX or JP1/AS is enabled, see 3.44.8 Filter condition definition windows.

The following describes the items displayed in the Detailed Settings for Event Receiver Filter window.

Filter name

Specifies the name of an event receiver filter. The conditions set for a filter are identified by the name specified in this area. The number of characters that you can enter is from 1 to 30,000 bytes.

The name specified here is listed in the Specifications area of the Settings for Event Receiver Filter window.

User name

Specifies the names of the users to which the restrictions imposed by the event receiver filter apply. Multiple user names require a comma as a separator. The number of characters that you can enter is from 1 to 30,000 bytes.

Show List (or Hide List)

Clicking the Show List button displays the list of condition groups. When the list is displayed, the button changes to the Hide List button, which, if clicked, hides the list.

Pass-conditions groups

This area displays the list of pass-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of 30 condition groups can be set. When 30 condition groups have been specified, the Add and Copy buttons are disabled.

Exclusion-conditions groups

This area displays the list of exclusion-conditions groups. If the user selects a condition group from the list, the name of the selected group is displayed in the Condition group name area, and the condition settings are displayed in the Conditions area. The user can edit these condition settings.

A maximum of 30 condition groups can be set. When 30 condition groups have been specified, the Add and Copy buttons are disabled.

Add

Clicking this button adds a new condition group. For pass-conditions groups, the default name Condition group n (n is a number) is assigned to the new pass-conditions group that is added. For exclusion-conditions groups, the default name Exclusion-condition group n (n is a number) is assigned to the new exclusion-conditions group that is added. Each time a new condition group is added, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Copy

Clicking this button copies the selected condition group. When the user selects a condition group and clicks this button, a new condition group in which the same conditions as those defined in the selected condition group is created. The new condition group that is created is assigned the default name Copy original-condition-group-name, and is added to the list of condition groups. After creating a copy of a condition group, if the user creates another copy of the same condition group, a number is added after the string Copy in CopyN original-condition-group-name (N is a number). The first number used is 2, which is incremented each time the same condition group is copied. Note that each time a new condition group is added to the list, the focus moves to the text box in the Condition group name area so that the user can assign a name.

Delete

Clicking this button deletes the selected condition group. When this button is clicked, a message dialog box displaying the following message appears:

KAVB0257-I

Clicking the Yes button in the message dialog box deletes the selected condition group.

Condition group name

This box is used to specify the name of a condition group. The number of characters that you can enter is from 1 to 50 bytes.

If the user selects an existing condition group in the Pass-conditions groups or Exclusion-conditions group area and specifies a new name, the condition group is renamed. The same name cannot be specified for a pass-conditions group and an exclusion-conditions group.

If the user attempts to specify a condition group name that already appears in the Pass-conditions groups or Exclusion-conditions group area, a message dialog box displaying the following message appears:

KAVB0256-E The specified condition group name already exists.

Clear

Clicking this button clears all condition settings displayed under Conditions.

Read From Selected Event

Clicking this button applies the attribute values of the JP1 event selected in the Event Console window to the corresponding items under Conditions. The following describes how the attribute values are applied:

When an event attribute value includes a control character (such as a linefeed or tab character)

The part before the first control character is applied. If an option condition can be specified for the event attribute, First characters is selected.

When an event attribute value does not include a control character

The entire event attribute value is applied. If an option condition can be specified for the event attribute, Match is selected.

If the information of the selected JP1 event is mapped in the Event-Information Mapping Definitions window, the attribute values for the display items and program-specific extended attribute values that have been mapped are not applied. For details about the Event-Information Mapping Definitions window, see 6.9.2 Displaying extended attributes of JP1 events (mapping of event information) in the JP1/Integrated Management 3 - Manager Administration Guide.

Source host

Specifies the name of a host (event server name) that issues a JP1 event. Multiple host names require a comma as a separator. A maximum of 100 host names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (if Regular expression is not selected in the drop-down list on the right).

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

For Source host, if the integrated monitoring database and the IM Configuration Management database are enabled, a business group name can also be specified in path format. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

Event level

Specifies the event severity levels from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

Object type

Specifies the object type of a JP1 event. The character string can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Object name

Specifies the object name of a JP1 event. Multiple object names require a comma as a separator. A maximum of 100 object names can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified characters string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object type

Specifies the root object type of a JP1 event. The root object type can be typed in the text box or selected from the drop-down list.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Root object name

Specifies the root object name of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Occurrence

Specifies the occurrence type of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

User name

Specifies the user name of a JP1 event.

Multiple user names require a comma as a separator. A maximum of 100 user names can be specified. If a user name that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Message

Specifies the message text of a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression. We recommend First characters or Is contained. If Regular expression is selected, make sure that control characters used in the message text are not included in the expression.

Product name

Specifies the name of the program that issues a JP1 event.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Event ID

Specifies the event ID of a JP1 event. Multiple event IDs require a comma as a separator.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match and Does not match.

Status

Specifies the event statuses of JP1 events. If the user selects Processed, only events whose status is set to Processed are filtered. If the user selects Unprocessed, only events whose status is set to Unprocessed are filtered.

Action

For JP1 events for which an automated action is defined, this item enables a search based on whether the defined automated action has been executed.

Extended attribute

Displays the window for setting the condition whether to use the program-specific extended attribute value to perform filtering. To set the condition, select the Extended attribute check box. If you select this check box, the Configure button becomes available. If you click the Configure button, the Event Search Conditions (Program-Specific Information in Extended Attribute) window is displayed, and you can set the condition.

For details about this window, see 3.26 Event Search Conditions (Program-Specific Information in Extended Attribute) window.

If the mapping of the event source host is enabled, the following item is also displayed:

Event source host name

Specifies the name of the host on which an event that triggered issuance of a JP1 event occurred. How to specify multiple hosts is the same as the Source host field.

Alphabetic characters are case sensitive. However, if ON is set for the -ignorecasehost option of the jcoimdef command, case is ignored (if Regular expression is not selected in the drop-down list on the right).

From the drop-down list on the right, the user selects a condition for the specified character strings from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

For Event source host name, if the integrated monitoring database and the IM Configuration Management database are enabled, a business group name can also be specified in path format. Either Match or Does not match can be selected as a condition. If these databases are disabled and the selected condition is not Match or Does not match, a business group name specified in path format is treated as a host name.

For details on the event source host mapping function, see 4.9 Mapping of the event source hosts in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

3.32 Action Parameter Definitions window

The Action Parameter Definitions window lists the settings of automated actions.

To display the Action Parameter Definitions window, the user must have the JP1_Console_Admin permission. If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The settings of an automated action can be specified in the Action Parameter Detailed Definitions window, which is opened from the Action Parameter Definitions window.

The Action Parameter Definitions window appears when the version of the automated action definition file is 09-00 or later (DESC_VERSION is 3 or 4).

If the version of the automated action definition file is 11-10 or earlier (DESC_VERSION is 3), the Action Parameter Definitions window does not show the following items:

The edit icon indicating that the automated action definition has been edited

The Apply check box

The ID display area

The Retain the conditions for which the definition was not changed check box

If the version of the automated action definition file is 8 or earlier, the Action Parameter Definitions (for compatibility) window appears. For details about the Action Parameter Definitions (for compatibility) window, see Action Parameter Definitions (for compatibility) window.

The Action Parameter Definitions window and the Action Parameter Definitions (for compatibility) window are not displayed in the following cases:

The automated action definition file contains an error.

The size of an automated action definition parameter in the automated action definition file exceeds the maximum.

If the Action Parameter Definitions window is not displayed because of an error in the automated action definition file, open the file with a text editor and correct the error. For details about the automated action definition parameters, see Automated action definition file (actdef.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The Action Parameter Definitions window is displayed when the user chooses Options from the menu bar of the Event Console window and then Automated Action Parameter Settings. The following figure shows an example of the Action Parameter Definitions window.

Figure 3‒60: Action Parameter Definitions window

The following describes the items displayed in the Action Parameter Definitions window.

Status monitoring

Specifies whether to monitor the action status.

Apply: The action status is monitored.

Do not apply: The action status is not monitored.

The default is Do not apply.

If an action is in an abnormal status (Fail or Error) when the action status is monitored, a JP1 event is issued or a notification command is executed to report the abnormal status. The method for reporting the abnormal status must be specified in the automatic action notification definition file (actnotice.conf). For details about the automatic action notification definition file (actnotice.conf), see Automatic action notification definition file (actnotice.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The Action Log window, the List of Action Results window, or the Action Log Details window can be used to check the status of an action. Also, the Event Console window can be used to check whether an action is in an abnormal status.

Changes to the action status monitoring conditions affect only the actions executed after the change. For actions before the change, the settings before the change are used.

Action parameters

This area displays the list of the automated action definitions that have been set. The list displays the following items: edit icon, Apply, ID, Group, Action name, Event ID, Type, Action, Target host, and Comment.

The priority of an automated action definition is based on the display order of the list. The definition displayed at the top of the list has the highest priority. For details about the priority, see 6.3.2 Precedence of execution conditions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

A maximum of 1,000 automated actions can be registered. The AND condition specified for the automated action definition one line above is used.

For details about the AND condition, see 6.3.3 Parameter groups and AND condition in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

edit icon

This icon indicates that the automated action definition has been edited.

Apply

This check box is used to specify whether to enable or disable the automated action. The automated action definition is enabled when the check box is selected.

ID

Displays the action ID. When conditions are joined with AND, this displays only the action ID of the first action execution condition of the AND-joined conditions.

Group

Displays the parameter group.

Action name

Display the action name.

Event ID

Display the event ID.

Target host

Displays the target host.

Comment

Displays the comment.

Up

Clicking this button moves the selected automated action definition up one line, changing the priority of the automated action definitions.

Down

Clicking this button moves the selected automated action definition down one line, changing the priority of the automated action definitions.

Add

Clicking this button allows the user to create a new automated action definition. When this button is clicked, the Action Parameter Detailed Definitions window appears.

When 1,000 or more automated actions have been defined, this button is disabled.

Edit

To edit an automated action definition that appears in the Action parameters area, select the definition in the list and then click the Edit button.

Delete

To delete an automated action definition that appears in the Action parameters area, select the definition in the list and then click the Delete button.

Retain the conditions for which the definition was not changed

Selecting this check box retains the suppression status and the status of satisfied conditions of the AND-joined conditions unless the action definition is edited. When this check box is selected and the Apply button is clicked, the suppression status and the status of satisfied conditions of the AND-joined conditions are initialized only when the action execution condition is edited. When this check box is cleared and the Apply button is clicked, the suppression status of all action execution conditions and the status of satisfied conditions of the AND-joined conditions are initialized.

Apply

Clicking this button applies the settings.

Action Parameter Definitions (for compatibility) window

If the user uses the action definition file version 8 or earlier, the Action name column does not appear in the Action parameters area. To set up the action definition file for version 8 or earlier, the user must use the Action Parameter Definitions (for compatibility) window. The following figure shows an example of the Action Parameter Definitions (for compatibility) window.

3.33 Action Parameter Detailed Definitions window

The Action Parameter Detailed Definitions window is used to set the conditions for executing an automated action and to set how the automated action will be executed. This window is displayed by performing the following operations:

In the Action Parameter Definitions window, click the Add button, or select an entry in the Action parameters list, and then click the Edit button.

In the Action Parameter Definitions window, select an item in the Action parameters list, and then double-click the item.

The settings specified in the Action Parameter Detailed Definitions window are applied when the Apply button is clicked in the Action Parameter Definitions window. These settings are converted into an automated action definition parameter in the automated action definition file and then applied. If the size of the automated action definition parameter exceeds the maximum, an error dialog box displaying the message KAVB5060-W, KAVB5068-W, or KAVB5069-W appears. If the error dialog box appears, the settings must be reviewed.

The maximum length of an automated action definition parameter depends on the version of JP1/IM on the connected host:

JP1/IM - Manager (08-01 or later): 5,706 bytes

For details about the automated action definition parameters, see Automated action definition file (actdef.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The Action Parameter Detailed Definitions window differs depending on the version of the action definition file.

If the version of the action definition file is 09-00 or later, see 3.33.1 Action Parameter Detailed Definitions window. If the version is 8 or earlier, see 3.33.2 Action Parameter Detailed Definitions (for compatibility) window.

3.33.1 Action Parameter Detailed Definitions window

The Action Parameter Detailed Definitions window has two pages: Action Condition and Execution Monitoring.

(1) Action Condition page

The following figure shows an example of the Action Condition page:

Figure 3‒61: Action Parameter Detailed Definitions window (Action Condition page)

The following describes the items displayed in the Action Parameter Detailed Definitions window.

Action ID

Specifies the action ID of the action execution condition. This is displayed when the version of the action definition file is 11-50 or later (DESC_VERSION is 4).

You can select an action ID from the drop-down list or enter it directly. The drop-down list shows unused action IDs in the range from 0 to 999, and unedited action IDs (only when the window was opened by clicking the Edit button).

Available values that you can enter are unused action IDs in the range from 0 to 2,147,483,647.

You cannot specify this when you set Parameter group to &.

Parameter group

Specifies the parameter group. A one-digit number from 0 to 9 or an ampersand (&), which indicates the AND condition, can be specified.

Action name

Specifies the action name. Strings of 1 to 50 bytes can be specified. Specifiable characters are characters other than the control characters (0x00 to 0x1F, 0x7F to 0x9F). Action n appears if the Action Parameter Detailed Definitions window is displayed by clicking the Apply button in the Action Parameter Definitions window. For n, the system selects the smallest available numeric value from 1 to 1,000 to create a name that does not duplicate an existing action name.

The action name cannot be omitted. Note, however, that if the user specifies & for Parameter group, an action name cannot be specified.

Comment

The user can specify a comment for the automated action definition by specifying a string of no more than 1,040 bytes. Specifying a comment is optional.

The following describes the items displayed on the Action Condition page.

Event ID

Specifies a specific event ID or all event IDs for use as a condition for executing the automated action.

To specify a specific event ID, the user selects the Specify ID radio button, and then enters the event ID in the text box. The event ID consists of a basic part and an extended part. Each part is a hexadecimal number of not more than 8 bytes. You can specify a value from 0 to 7FFFFFFF. The two parts are separated by a colon (:). The extended part can be omitted.

To specify all event IDs, the user selects the All IDs radio button.

Read From Selected Event

Clicking this button automatically enters an event condition by using the attribute value of the JP1 event selected from the event list. This button is available only if the user selects one JP1 event from the event list displayed when the Action Parameter Detailed Definitions window opens. The event conditions specified before the Read From Selected Event button is clicked are deleted. If the JP1 event selected in the event list scrolls out of the list, no condition is entered.

Event conditions list

This area displays the event conditions. Conditions that are higher in the list have higher priority.

The attribute name of an event condition is displayed in the Attribute name column. If the user specifies a specific extended attribute as the event condition, E. is prefixed to the attribute name, as in E.SEVERITY.

The attribute value is displayed in the Attribute value column. If multiple attribute values are specified, the values must be separated with a comma (,). These values are combined using the AND operator, and treated as a single condition.

The Condition column displays the comparative operator for the event condition (First characters, Match, Does not match, Is contained, Is not contained, or Regular expression).

Add

Clicking this button allows the user to add a new event condition. When this button is clicked, an event condition that has not been set is added at the bottom of the event condition list. A maximum of 256 event conditions can be added.

Delete

Clicking this button deletes a selected event condition.

Up

Clicking this button moves the selected event condition up one line. Use this button to change the priority of the event conditions.

Down

Clicking this button moves the selected event condition down one line. Use this button to change the priority of the event conditions.

Apply

Clicking this button applies the settings specified in the area for editing event conditions to the event conditions list. If the event condition is a regular expression that satisfies either of the following conditions, the KAVB0517-W message is displayed in a dialog box:

Regular expression that begins or ends with .*

Regular expression that includes a succession of .*

For details about the KAVB0517-W message, see 2.2 Messages related to Central Console - View (KAVB0001 to KAVB2000) in the JP1/Integrated Management 3 - Manager Messages.

Area for editing event conditions

This area allows the user to edit event conditions. The area that is displayed differs according to the attribute that is selected. Each area is described below.

Event ID editing

The area shown above is displayed for the following attribute:

Event ID

You can specify a maximum of eight hexadecimal digits as the event ID. When specifying multiple event IDs, the entire string must not exceed 4,096 bytes. Control characters cannot be specified. The range of specifiable values is from 0 to 7FFFFFFF.

If Regular expression is selected, alphabetic characters are case sensitive.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

A maximum of 100 event IDs, separated by a comma (,), can be specified. Note, however, that if Regular expression is selected from the drop-down list, multiple event IDs cannot be specified.

From the drop-down list on the right, the user selects a condition for the specified event ID from Match, Does not match, and Regular expression.

Numeric value editing

The area shown above is displayed for the following attributes:

Registered reason

Source process ID

Source user ID

Source group ID

A decimal integer that is no more than 4,096 bytes can be specified. You can specify a value from -2,147,483,648 to 2,147,483,648.

A maximum of 100 numeric values, separated by a comma (,), can be specified. Note, however, that if Regular expression is selected from the drop-down list, multiple event IDs cannot be specified.

If Regular expression is selected, alphabetic characters are case sensitive.

From the drop-down list, the user selects a condition for the specified character string from Match, Does not match, and Regular expression.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

If the user selects either Match or Does not match, only an integer from 0 to 9 or a hyphen (-) can be specified.

Date and time editing

The area shown above is displayed for the following attributes:

Registered timeframe

Arrived timeframe

A value of no more than 4,096 bytes in YYYYMMDDhhmmss format can be specified.

Multiple dates and times cannot be specified.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user can select only Regular expression as the condition for the specified date and time.

Character string editing

The area shown above is displayed for the following attributes:

Source user name

Source group name

Source IP address

Source host

Message

Product name

Object name

Root object name

Object ID

Occurrence

User name

Result code

Event source host name

To specify an IPv6 address for Source IP address, alphabetic characters must be lower case, as shown below:

0011:2233:4455:6677:8899:aabb:ccdd:eeff

The abbreviated form of an IP address like the one shown below cannot be specified:

2012:7:8::a:b

If the integrated monitoring database and IM Configuration Management database are enabled, a business group name in path format can be specified for Source host and Event source host name. Either Match or Does not match can be selected as a condition. If Match or Does not match is not selected when the integrated monitoring database and IM Configuration Management database are disabled, a business group name specified in path format is treated as a host name.

Note that Event source host name can be specified only if the mapping of the event source host is enabled. If the mapping of the event source host is disabled, conditions for Event source host name can be specified by specifying JP1_SOURCEHOST as the attribute name when the area for editing event conditions is in the Extended-attribute editing pattern.

A character string of no more than 4,096 bytes can be specified.

A maximum of 100 character strings, separated by a comma (,), can be specified. Note, however, that if Regular expression is selected from the drop-down list, multiple character strings cannot be specified.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

If Regular expression is not selected in the drop-down list on the right when ON is set for the -ignorecasehost option of the jcoimdef command, the case of alphabetic characters is ignored for the following attributes:

Source host

Event source host name

To specify a character string that includes tabs, line breaks, or commas (,), use the representation shown in the following table.

Table 3‒21: Specification of a character string that includes tabs, line breaks, or commas for the editing of character strings

Number

Item

Representation

1

Tab (0x09)

\t

2

Linefeed (0x0a)

\n

3

Carriage return (0x0d)

\r

4

Comma (0x2c)

When used as a separator

,

When used as an ordinary character and Regular expression is selected in the drop-down list on the right

,

When used as an ordinary character and Regular expression is not selected in the drop-down list on the right

\,

The representation of tabs and line breaks used in the Action Parameter Detailed Definitions window is different from the representation used in the automated-actions definition file (actdef.conf). For details, see Automated action definition file (actdef.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Editing of character strings with input candidates

The area shown above is displayed for the following attributes:

Object type

Root object type

A character string of no more than 4,096 bytes can be specified.

A maximum of 100 character strings, separated by a comma (,), can be specified. Note, however, that if Regular expression is selected from the drop-down list, multiple character strings cannot be specified.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, Is contained, Is not contained, and Regular expression.

To specify a character string that includes tabs, line breaks, or commas (,), use the representation shown in the following table.

Table 3‒22: Specification of a character string that includes tabs, line breaks, or commas for the editing of character strings with input candidates

Number

Item

Representation

1

Tab (0x09)

\t

2

Linefeed (0x0a)

\n

3

Carriage return (0x0d)

\r

4

Comma (0x2c)

When used as a separator

,

When used as an ordinary character and Regular expression is selected in the drop-down list on the right

,

When used as an ordinary character and Regular expression is not selected in the drop-down list on the right

\,

The representation of tabs and line breaks used in the Action Parameter Detailed Definitions window is different from the representation used in the automated-actions definition file (actdef.conf). For details, see Automated action definition file (actdef.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Total number of seconds editing

The area shown above is displayed for the following attributes:

Start timeframe

End timeframe

A numeric value of no more than 4,096 bytes can be specified.

Multiple numeric values cannot be specified.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user can select only Regular expression as the condition for the specified total number of seconds.

Severity-level editing

The area shown above is displayed for the following attribute:

Event level

To specify the severity by selecting a condition, the user selects the Specify directly radio button and then selects the check boxes for the desired severity levels from Emergency, Warning, Critical, Error, Warning, Notice, Information, and Debug.

To specify the condition for the severity level as a regular expression, select the Specify regular expression radio button, and enter the condition. The character string specified as the condition must be no more than 4,096 bytes.

Alphabetic characters are case sensitive.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

Extended-attribute editing

The area shown above is displayed for the following attribute:

Extended attribute

Specify a condition for the program-specific extended attribute.

Depending on the selected radio button, the item that can be specified differs.

When Attribute name is selected

Specify a condition for the program-specific extended attribute by using an attribute name.

The name specified in the Attribute name text box must be no more than 32 bytes of upper-case alphabetic characters, numeric characters, and underscores (_). The attribute name must begin with an upper-case alphabetic character.

When Item name is selected:

Specify a condition for the program-specific extended attribute by using an item name.

Specify a condition by selecting an item name from the Item name drop-down list. The displayed item names are program-specific extended attributes specified for the standard file and the extended file of the definition file for extended event attributes.

The condition the user specifies in the Condition text box must be a character string of no more than 4,096 bytes.

A maximum of 100 character strings, separated by a comma (,), can be specified. Note, however, that if Regular expression is selected from the drop-down list, multiple character strings cannot be specified.

Alphabetic characters are case sensitive.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

From the drop-down list on the right, the user selects a condition for the specified character string from First characters, Match, Does not match, Is contained, Is not contained, and Regular expression.

Compatibility editing

The area shown above is displayed for the following attributes:

Detailed event information

Basic event information

A character string of no more than 4,096 bytes can be specified.

If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). Each character is a one-byte character.

Alphabetic characters are case sensitive.

From the drop-down list on the right, the user can select only Regular expression as the condition for the specified character string.

Execution user name

Specifies the JP1 user name under which the action is to be executed. The JP1 user name specified must be no more than 31 bytes and must not include a space character.

In addition, a variable can be used to specify attribute information of the received JP1 event. For example, to execute an action under the name of the user that issued an event, the user specifies $EVUSR. For details about variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Target host

Specifies the name of the host on which the action is to be executed. The specified host name must not be more than 255 bytes, must not include a space character, and must be the name of a managed host defined in the system configuration definition.

A host group name can also be specified. If specified, it must be defined in the host group definition file.

For Target host, a business group name or monitoring group name that has no more than 2,048 bytes in path format can be specified. However, if the integrated monitoring database and the IM Configuration Management database are disabled at the time of login to JP1/IM, the name specified in path format is treated as a host name or host group name.

In addition, a variable can be used to specify attribute information of the received JP1 event. For example, $EVHOST can be specified to execute the action on the host where the event occurred. For details about variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Action

Specifies the command to be executed as an action. The command line specified in this area can include variables that indicate attribute information of the received JP1 event.

For details about variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Note that the specified command line must not end with a backslash (\).

For details about commands that can be specified, see Chapter 6. Command Execution by Automated Action (JP1/Base linkage) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The maximum length of a command that can be executed as an action is 4,096 bytes. If the length of the command, including variables (such as $EVMSG) that can be used to define the action, exceeds 4,096 bytes, the command is not executed, and the status of the action becomes Fail. In the Message area of the Action Log Details window, the following message is displayed:

KAVB4421-W

If an action contains an unrecognizable character code (anything outside the ASCII character set), the action is not executed because of the shell or other specifications on the target host, or if executed, the results might be incorrect. In this case, the action does not fail, and its status becomes Ended. Invalid codes can also result when variables are replaced by their values at runtime. For the values that replace variables, check the applicable manuals for the products that issue JP1 events ahead of time.

Environment variable file

Specifies the full path name of the environment variable file saved on the host on which the command is executed. The maximum length of the specified full path name is 255 bytes.

The full path name can include variables that indicate attribute information of the received JP1 event. For details about the variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window

Variables can be used to specify the information contained in a JP1 event in the Action Definition area of the Action Parameter Detailed Definitions window for items such as Execution user name, Target host, Action, and Environment variable file. The variables are converted to information within the JP1 event when the action is executed.

The user specifies variables for these items in a format similar to $EVID. The following table describes the variables that can be used.

Table 3‒23: Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window

Type of information

Variable name

Description

Information contained in the JP1 event basic attribute

EVBASE

Overall basic event information

EVID

Event ID (basic-code:extended-code)

EVIDBASE

Event ID (basic code)

EVDATE

Event occurrence date (yyyy/mm/dd)

EVTIME

Event occurrence time (hh:mm:ss)

EVPID

Process ID for the event-issuing source

EVUSRID

User ID for the event-issuing source

EVGRPID

Group ID for the event-issuing source

EVUSR

Name of the event-issuing source user

EVGRP

Name of the event-issuing source group

EVHOST

Name of the event-issuing source host

EVIPADDR

IP address of the event-issuing source

EVSEQNO

Serial number in the event database

EVARVDATE

Event arrival date (yyyy/mm/dd)

EVARVTIME

Event arrival time (hh:mm:ss)

EVSRCNO

Serial number in the event database of the event-issuing source

EVMSG

Overall message text

EVDETAIL

Overall detailed event information

Information contained in the JP1 event extended attribute

EVSEV

Severity of extended event information (Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug)

EVUSNAM

User name

EVOBTYP

Object type

EVOBNAM

Object name

EVROBTYP

Registration name type

EVROBNAM

Registration name

EV"PRODUCT_NAME"

Product name

EV"OBJECT_ID"

Object ID

EV"OCCURRENCE"

Occurrence

EV"START_TIME"

Start time

EV"END_TIME"

End time

EV"RESULT_CODE"

Return code

EV"JP1_SOURCEHOST"

Issuing host name

EV"extended-attribute-name"

Optional extended attribute

Other information

EV"@JP1IM_CORRELATE"

Correlation event flag:

0: The event is not a correlation event.

1: The event is a correlation event.

2: The event is a correlation failure event.

EV"@JP1IM_ORIGINAL_SEVERITY"

Severity of extended event information (before the change)

(Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug)

EV"@JP1IM_CHANGE_SEVERITY"

Severity change flag:

0: The severity has not been changed.

1: The severity has been changed.

EV"@JP1IM_DISPLAY_MESSAGE"

Changed display message

EV"@JP1IM_CHANGE_MESSAGE"

Flag indicating whether the display message has been changed

The message has not been changed: 0

The message has been changed: 1

ACTHOST

Name of the manager for the action execution request source

EVENV1 to EVENV9

In the specified execution condition of an action, data pulled from within () in a regular expression

(This can only be used when an extended regular expression is used on a manager)

If a value cannot be found for a variable, the corresponding item remains blank. Note, however, that an optional extended attribute (EV"extended-attribute-name") and pulled data (EVENV1 to EVENV9) will be handled as variable names. Depending on the type of JP1 event, there might be items without variables and actions that cannot be executed because the information in each attribute contains codes not recognized as characters (anything outside the ASCII character set). In this case, the action either cannot be executed, or if executed, the execution result would be invalid. For products that issue JP1 events before the setup, see the applicable manuals.

Precautions regarding the specification of variables

When alphanumeric characters and an underscore (_) are specified immediately after a variable, conversion will not be performed properly. To ensure proper conversion, the user must enclose the variable in curly brackets ({}), as shown in the following examples. The following examples assume that the event ID ($EVID) is set to 100:0, and the extended attribute EX ($EV"EX") is set to ABC.

Example specifications

Action definition -> Converted information

$EVID abc -> 100:0 abc

$EVIDabc -> $EVIDabc (in Windows) or N/A (in UNIX)

${EVID}abc -> 100:0abc

$EVID_abc -> $EVID_abc (in Windows) or N/A (in UNIX)

${EVID}_abc -> 100:0_abc

$EV"EX" abc -> ABC abc

$EV"EX"abc -> ABCabc

If the source character information contains the following control characters, the control characters are converted to space characters (0x20) and then processed.

These control characters are 0x01 to 0x1F and 0x7F (but not the tab character (0x09)).

For example, if the message obtained by specifying $EVMSG contains a line break (0x0A), the line break (0x0A) is converted to a space character (0x20) and then processed.

As another example, when an action (echo $EVMSG) is set, and a string containing a line break, such as line-10x0Aline-2 is received as an event message, the command executed as the action is echo line-1Δline-2 (Δ represents a space character).

In UNIX, the final expansion depends on evaluation by the shell. If the expanded data contains * or another character that has a special meaning in the shell, the contents are converted. To prevent this replacement, the user must enclose the entire variable in double quotation marks ("), as, for example, "$EVMSG".

If the JP1 event information specified in a variable includes characters that have special meanings in a command, such as a double quotation marks (") and single quotation marks ('), the command might not be interpreted correctly. If such characters are included, it is recommended that the configuration file for converting information is used to convert the characters. For details about the configuration file for converting information, see Configuration file for converting information (event_info_replace.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(2) Execution Monitoring page

The following figure shows an example of the Execution Monitoring page.

Figure 3‒62: Action Parameter Detailed Definitions window (Execution Monitoring page)

Suppress

Specifies whether to suppress execution of the automated action.

Apply: Execution of the automated action is suppressed.

When Apply is selected, the length of time (in seconds) that the automated action is to be suppressed must be specified in the Suppression time text box. The range of specifiable values is from 1 to 3,600. The default is 300.

Do not apply: Execution of the automated action is not suppressed.

When Do not apply is selected, the Suppression time text box is disabled.

The default is Do not apply.

The Suppress area is disabled in the following cases:

An ampersand (&) is specified in the Parameter group area.

The Action name text box is blank.

Delay monitoring

Specifies whether to monitor delays in executing the automated action.

Apply: Delays in executing the action are monitored.

When Apply is selected, the length of time (in seconds) for monitoring delays must be specified in the Monitoring time text box. If the action is not completed within the specified period of time, the action is regarded as a delayed action. The range of specifiable values is from 1 to 86,400. The default is 600.

Do not apply: Delays in executing the action are not monitored.

The default is Do not apply.

When delays in executing the automated action are monitored, if the execution of an action is delayed, a JP1 event is issued or a notification command is executed to report the delay. The method of reporting the abnormal status must be specified in the automatic action notification definition file (actnotice.conf) ahead of time.

The Action Log window, the List of Action Results window, or the Action Log Details window can be used to check the action delay status. Also, the Event Console window can be used to check whether the execution of an action has been delayed.

A monitoring interval appropriate for the automated action being monitored for execution delays needs to be set.

3.33.2 Action Parameter Detailed Definitions (for compatibility) window

The Action Parameter Detailed Definitions (for compatibility) window is used to set up the automated actions for 08-01 and earlier versions of the automated action definition file. This window is displayed when the user chooses Add or Edit in the Action Parameter Definitions window. JP1/IM - View. No business group name can be used in this window. A business group name specified in this window is treated as a host name. The following figure shows an example of the Action Parameter Detailed Definitions (for compatibility) window.

Figure 3‒63: Action Parameter Detailed Definitions (for compatibility) window

The following describes the items displayed in the Action Parameter Detailed Definitions window.

Parameter group

Specifies the parameter group. A one-digit number from 0 to 9 or an ampersand (&), which indicates the AND operator.

Event ID

Specifies a specific event ID or all event IDs for use as a condition for executing the automated action.

To specify a specific event ID, the user selects the Specify ID radio button, and then enters the event ID in the text box. The event ID consists of a basic part and an extended part. Each part is a hexadecimal number of not more than 8 bytes. The two parts are separated by a colon (:). The extended part can be omitted.

To specify all event IDs, the user selects the All IDs radio button.

Message

Specifies a regular expression that represents the message text (or a part of the message text) that is to be used as a condition for executing the automated action. The regular expression must not include any control characters used in message text. If a slash (/) is used as an ordinary character in the regular expression, it must be preceded by a backslash (\/).

Alphabetic characters are case sensitive.

For details about regular expressions, see Appendix G. Regular Expressions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Basic event information

Specifies a regular expression that represents the basic JP1 event information to be used as a condition for executing the automated action. If a slash (/) is used as an ordinary character in the regular expression, it must be preceded by a backslash (\/). For details about regular expressions, see Appendix G. Regular Expressions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Alphabetic characters are case sensitive.

Basic event information is passed as the information for basic JP1 event attributes in order according to the format below. This format must be used to specify the conditions for executing actions.

event-IDΔevent-issuing-user-nameΔevent-issuing-user-IDΔ

event-issuing-group-nameΔevent-issuing-group-IDΔ

event-issuing-event-server-nameΔevent-issuing-process-IDΔ

event-registration-dateΔevent-registration-timeΔevent-issuing-host-IP-address

For details about the information included in the basic attributes for these JP1 events, see 3. JP1 Events in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Detailed event information

Specifies as the execution conditions for executing an automated action, a regular expression that represents information about the detailed attributes of the JP1 event basic attributes. If a slash (/) is used as an ordinary character in the regular expression, it must be preceded by a backslash (\/). For details about regular expressions, see Appendix G. Regular Expressions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Alphabetic characters are case sensitive.

The information for the detailed attributes for the JP1 event basic attributes contains additional JP1 event information. The information content and the format differ according to the JP1 event. Any detailed attribute information for JP1 events that is in binary format is treated as an absence of information (NULL).

The detailed attributes of the JP1 basic event attributes are used primarily when a product that issues events compatible with the JP1/SES format records detailed information in JP1-series products of version 5 or earlier. Many products of version 6 and later use JP1 event extended attributes to record detailed information.

Extended event information

Specifies whether to use extended JP1 event information as a condition for executing an automated action. Extended JP1 event information is used as a condition for executing an automated action when the user selects the Use extended information check box, and then clicks the Configure button.

The Action Parameter Detailed Definitions (Extended Event Information) window appears.

Execution user name

Specifies the JP1 user name under which the action is to be executed. The JP1 user name specified must not be more than 31 bytes and must not include a space character.

In addition, a variable can be used to specify attribute information of the received JP1 event. For example, $EVUSR can be specified to execute the action under the name of the user who issued the event. For details about the variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Target host

Specifies the name of the host on which the action is to be executed. The host name specified must not be more than 255 bytes, must not include a space character, and must be the name of a managed host defined in the system configuration definition.

A host group name can also be specified. If specified, it must be defined in the host group definition file.

In addition, a variable can be used to specify attribute information of the received JP1 event. For example, $EVHOST can be specified to execute the action on the host from which the event was issued. For details about variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Action

Specifies the command to be executed as an action. The command line specified in this area can include variables that indicate attribute information of the received JP1 event.

For details about variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Note that the specified command line must not end with a backslash (\).

For details about the commands that can be specified, see Chapter 6. Command Execution by Automated Action (JP1/Base linkage) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The maximum length of commands that can be executed as actions is 4,096 bytes. If the length of the command, including converted information such as variables that can be used in the action definition (for example, $EVMSG), exceeds 4,096 bytes, the command is not executed, and the status of the action becomes Fail. In the Message column of the Action Parameter Detailed Definitions window, the following message is displayed:

KAVB4421-W

If an action contains an unrecognizable character code (anything outside the ASCII character set), the action might not be executed because of the shell or other specifications on the target host, or if executed, the results might be invalid. In this case, the action does not fail and its status becomes Ended. Invalid codes can also result when variables are replaced with their values at runtime. For the values that replace variables, check the applicable manuals for the products that issue JP1 events ahead of time.

Note:

The length of commands that can be executed as actions differs depending on the system running JP1/IM or JP1/Base.

If JP1/IM or JP1/Base of version 6 or 7 is installed on the hosts via which an automatic action is executed, the command must be 1,024 bytes or less. These hosts include the host from which the command is entered as well as the host on which the command is executed. For details, see 13.4.1 Notes regarding the considerations for automated actions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Environment variable file

Specifies the full path name of the environment variable file saved on the host on which the command is executed. The maximum length of the specified full path name is 255 bytes.

The full path name can include variables that indicate attribute information of the received JP1 event. For details about variables that can be specified, see Variables that can be used in the Action Definition area of the Action Parameter Detailed Definitions window.

Suppress

Specifies whether to suppress execution of the automated action.

Apply: Execution of the automated action is suppressed.

If Apply is selected, the length of time (in seconds) that the automated action is to be suppressed must be specified in the Suppression time text box. The range of specifiable values is from 1 to 3,600. The default is 300.

Do not apply: Execution of the automated action is not suppressed.

When Do not apply is selected, the Suppression time text box is disabled.

The default is Do not apply.

The Suppress area is disabled in the following cases:

An ampersand (&) is specified in the Parameter group area.

The Action text box is blank.

Delay monitoring

Specifies whether to monitor delays in executing the automated action.

Apply: Delays in executing the action are monitored.

When Apply is selected, a number of seconds must be specified in the Monitoring time text box. If the action is not completed within the specified period of time, that action is assumed to be delayed. The range of specifiable values is from 1 to 86,400. The default is 600.

Do not apply: Delays in executing the action are not monitored.

The default is Do not apply.

If delays are monitored, a JP1 event is issued or a notification command is executed to report the delay. The method of reporting the delay must be specified ahead of time in the automatic action notification definition file (actnotice.conf).

The Action Log window, the List of Action Results window, or the Action Log Details window can be used to check the action delay status. Also, the Event Console window can be used to check whether the execution of an action has been delayed.

Note:

A monitoring interval appropriate for the automated action being monitored for execution delays should be set.

Comment

The user can specify a comment for the automated action in this text box.

3.34 Action Parameter Detailed Definitions (Extended Event Information) (for compatibility) window

The Action Parameter Detailed Definitions (Extended Event Information) window is used to specify extended event information as conditions for executing an automated action. This window is displayed when the user chooses Configure in the Action Parameter Detailed Definitions window. JP1/IM - View. No business group name can be used in this window. A business group name specified in this window is treated as a host name. The following figure shows an example of the Action Parameter Detailed Definitions (Extended Event Information) window.

Figure 3‒64: Action Parameter Detailed Definitions (Extended Event Information) window

The following describes the items displayed in the Action Parameter Detailed Definitions (Extended Event Information) window.

Event level

Specifies the JP1 event severity levels from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

Extended attributes

Specifies extended attributes in addition to JP1 event severity levels. All conditions specified in the Event level and Extended attributes areas are assumed to be combined with AND operators. For details about the extended attributes that can be specified, see 3.1.2 Extended attributes in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Alphabetic characters are case sensitive.

The two smaller text boxes are used to add a condition.

The larger box underneath lists the conditions that have already been set.

Add

The user adds a new condition by entering the name of an attribute in the left box and a regular expression that represents the value of the attribute in the right box, and then clicking Add. If a slash (/) is used as an ordinary character in the regular expression, it must be preceded by a backslash (\/). For details about regular expressions, see Appendix G. Regular Expressions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The attribute name specified in the left box can have a maximum of 32 bytes consisting of upper-case alphabetic characters, numeric characters, and underscores (_). The name must begin with an upper-case alphabetic character. If lower-case alphabetic characters are entered, they are automatically converted to the corresponding upper-case alphabetic characters.

When 100 conditions have been registered, the Add button is disabled.

Edit

The user edits a specified condition by selecting a condition from the large lower box and then clicking the Edit button.

Delete

The user deletes a specified condition by selecting a condition from the large lower box and then clicking the Delete button.

3.35 Edit Extended Attributes (for compatibility) window

The Edit Extended Attributes window is used to edit an extended event attribute displayed in the Action Parameter Detailed Definitions (Extended Event Information) (for compatibility) window as a condition for executing an automated action. The Edit Extended Attributes window is displayed when the user selects a condition in the list box in the Extended attributes area of the Action Parameter Detailed Definitions (Extended Event Information) (for compatibility) window, and then clicks the Edit button. The window is also displayed if the user double-clicks a condition in the list box. No business group name can be used in this window. A business group name specified in this window is treated as a host name. The following figure shows an example of the Edit Extended Attributes (for compatibility) window.

Figure 3‒65: Edit Extended Attributes (for compatibility) window

The following describes the items displayed in the Edit Extended Attributes (for compatibility) window.

Text box on the left

Displays the attribute name of the condition selected in the Action Parameter Detailed Definitions (Extended Event Information) (for compatibility) window. The user can change the attribute name as needed.

Text box on the right

Displays the attribute value of the condition selected in the Action Parameter Detailed Definitions (Extended Event Information) (for compatibility) window. The user can change the attribute value as needed. The attribute value must be specified as a regular expression. If a slash (/) is used as an ordinary character in the regular expression, it must be preceded by a backslash (\/).

Alphabetic characters are case sensitive.

3.36 Action Log window

The Action Log window lists the execution results of automated actions. This window is opened from the Event Console window in which the user selects an event with which automated actions are associated, and chooses View from the menu bar and then Action Log.

The following figure shows an example of the Action Log window.

Figure 3‒66: Action Log window

The following describes the items displayed in the Action Log window.

Update

Clicking this button refreshes the list in the Log area.

When an action has been selected and re-executed, clicking the Update button clears the selection.

Event ID

The ID of the selected JP1 event is displayed.

Log

This area lists the execution results of automated actions associated with the selected JP1 event.

When two or more actions are selected in the list, the only operation the user can perform is Cancel Action. If the user selects and double-clicks only one action, the Action Log Details window appears.

Suppress Trigger Details

This button can be used when Deterrent is displayed as the status or when -RD or -RUD is displayed as the status suffix in the Status column of the action selected in the Log area. If this button is clicked in these cases, details of the action that triggered the start of suppression are displayed.

The following describes the status suffixes -RD, -RUD, and -D displayed in the Status column:

-RD

This suffix is displayed when a value other than OFF is specified in the -r option of the jcoimdef command and the command is re-executed for the action suppressed during Automatic Action Service startup. This suffix is also displayed when the action log is output to the action re-execution file (example: Ended-RD)

-RUD

This suffix is displayed when the suppressed action is re-executed by clicking the Re-execute button in the Action Log window or List of Action Results window (example: Ended-RUD).

-D

This suffix is displayed when the status of a suppressed action is Fail. -D is displayed after Fail (example: Fail-D).

When the user selects an action in the Log area and clicks the Suppress Trigger Details button, the Action Log Details window opens. This window can be used to check the detailed execution result of the action.

The detailed execution result of an action can be displayed only if Deterrent is displayed as the status or if -RD or -RUD is displayed as the status suffix.

The Suppress Trigger Details button is disabled in the following cases:

When the user selects an action whose status is not Deterrent or whose status suffix is neither -RD nor -RUD

When the user selects multiple actions

Details

Clicking this button displays the detailed execution result of the action selected in the Log area. The Action Log Details window opens, displaying the detailed execution result.

This button is disabled if multiple actions have been selected.

Re-execute

Clicking this button requests the re-execution of the action selected in the Log area. The user can use this button to re-execute an action whose status is Cancel, Kill, Error, Deterrent, or Ended.

To use this button, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission.

To request the re-execution of an action, the user selects an action in the Log area and then clicks the Re-execute button. When the Re-execute button is clicked, a dialog box asking whether the user wants to re-execute the action appears. Clicking the OK button in the dialog box completes the re-execution request for the selected automated action. Hitachi recommends that the user click the Update button after submission of the request to check the status of the action.

The Re-execute button is disabled in the following cases:

When the user selects an action whose status is not Cancel, Kill, Error, Deterrent, or Ended

When the user selects multiple actions

Cancel Action

Clicking this button cancels execution of an action whose status is Wait, Queue, or Running. Note that cancellation fails if the version of JP1/Base on the host on which the action is to be executed is 07-00 or earlier.

To use this button, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission.

To request cancellation, the user selects an action in the Log area and then clicks Cancel Action. When Cancel Action is clicked, a dialog box asking whether the user wants to cancel execution of the action appears.

Clicking the OK button in the dialog box completes the request to cancel execution of the selected automated action is accepted. Note, however, that canceling the execution of an action whose status is not Wait, Queue, or Running cannot be requested.

Hitachi recommends that the user click the Update button after submission of the request to check the status of the action.

The Cancel Action button is disabled if the status of the selected action is not Wait, Queue, or Running.

3.37 Action Log Details window

The Action Log Details window displays the detailed execution result of an automated action.

This window is displayed when the user selects an action in the Log area of the Action Log window and then clicks Details or when the user double-clicks an action selected in the Log area of the Action Log window.

The following figure shows an example of the Action Log Details window.

Figure 3‒67: Action Log Details window

Log

This area displays the execution result of an automated action. The following table describes the items displayed in this area.

Table 3‒24: Items displayed in the Log area of the Action Log Details window

Item

Description

Action serial number

Number identifying the action

Event ID

ID of the received JP1 event

Serial number

Serial number of the received JP1 event in the event database.

This item is displayed only if the Action Log Details window was opened from the List of Action Results window.

Registered time

Time the received JP1 event was registered.

This item is displayed only if the Action Log Details window was opened from the List of Action Results window.

Event arrival time

Time the received JP1 event arrived at the local server.

This item is displayed only if the Action Log Details window was opened from the List of Action Results window.

Process ID

Process ID of the executed action.

If action information has been written to the action re-execution file because a failover occurred, OUTPUT is displayed.

Status

One of the following character strings indicating an action execution status:

Running, Ended, Unknown (the execution result of the command is unknown), Fail (an error occurred before the command was executed), Error (an error occurred after the command was executed), Queue (the command is waiting for the previous command to terminate), Send, Wait, Deterrent, Cancel, or Kill.

If an action has been re-executed, or the result has been output to the action re-execution file, one of the following suffixes is also displayed:

-R

This suffix is displayed if a value other than OFF was specified for the -r option of the jcoimdef command and the command was re-executed during Automatic Action Service startup. This suffix is also displayed if the action log was output to the action re-execution file (example: Ended-R).

-RU

This suffix is displayed if the command was re-executed by clicking Re-execute in the Action Log window or List of Action Results window (example: Ended-RU).

-RD

This suffix is displayed if a value other than OFF was specified for the -r option of the jcoimdef command and the command was re-executed for an action suppressed during Automatic Action Service startup. This suffix is also displayed if the action log was output to the action re-execution file (example: Ended-RD).

-RUD

This suffix is displayed if the command of a suppressed action was re-executed by clicking Re-execute in the Action Log window or List of Action Results window (example: Ended-RUD).

-D

This suffix is displayed if the status of a suppressed action was Fail. -D is displayed after Fail (example: Fail-D).

Delay

Indication of whether the action has been delayed. If the action has been delayed, Delay is displayed.

Inserted time

The time that the action was sent to the host on which the action was to be executed

Starting time

The time that the notification reporting the start of execution was received from the host on which the action was being executed

End time

The time that the notification reporting the end of execution was received from the host on which the action was executed

Return code

Return code for the executed action

Action

Command that was executed as the action

Host

Host on which the action was executed

Message

This area displays the message that was output when the action was executed.

Re-execute

Clicking this button requests re-execution of the action for which the details are displayed.

The user can use this button to re-execute an action whose status is Cancel, Kill, Error, Deterrent, or Ended. To use this button, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission.

When the Re-execute button is clicked, a dialog box asking whether the user wants to re-execute the action appears. Clicking the OK button in the dialog box completes the request to re-execute the selected automated action.

Hitachi recommends that the user check the status of the action after submission of the request by closing this window to redisplay the Action Log window or List of Action Results window, and then clicking the Update button.

Note that the Re-execute button in the Action Log Details window is disabled if the status of the action selected in the Action Log window or List of Action Results window was not Cancel, Kill, Error, Deterrent, or Ended.

Cancel Action

Clicking this button cancels execution of the action for which the details are displayed.

The user can use this button to cancel execution of an action whose status is Wait, Queue, or Running. Note that cancellation fails if the version of JP1/Base on the host on which the action is to be executed is 07-00 or earlier.

To use this button, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission.

When Cancel Action is clicked, a dialog box asking whether the user wants to cancel execution of the action appears. Clicking the OK button in the dialog box completes the request to cancel execution of the automated action.

Hitachi recommends that the user check the status of the action after submission of the request by closing this window to redisplay the Action Log window or List of Action Results window, and then clicking the Update button.

The Cancel Action button is disabled if the status of the action is not Wait, Queue, or Running.

3.38 List of Action Results window

The List of Action Results window lists the execution results of the automated actions set in the JP1/IM - Manager (JP1/IM - Central Console) to which the user is currently logged in. This window is displayed when the user chooses View from the menu bar of the Event Console window and then List of Action Results.

The following figure shows an example of the List of Action Results window.

Figure 3‒68: List of Action Results window

The following describes the items displayed in the List of Action Results window.

Target Event Search

Clicking this button retrieves the event that triggered execution of the action selected in the list of execution results.

If the user selects an action in the list and clicks this button, the event that triggered execution of the action is displayed on the Search Events page in the Event Console window.

This button is disabled in the following cases:

When multiple actions are selected

When no action is selected

Update

Clicking this button refreshes the execution results of automated actions. If the items that are displayed have been changed by using the or button, the information in the new position is displayed.

Update Settings

Clicking this button displays the Conditions for Updating List of Action Results window, where the conditions for displaying the execution results of automated actions can be set.

List of execution results

This area lists the execution results of the automated actions set in the JP1/IM - Manager (JP1/IM - Central Console) to which the user is currently logged in. The execution result of each action is displayed on one line.

The maximum number of action results displayed here is set in the Conditions for Updating List of Action Results window.

When multiple items are selected in the list, the only operation the user can perform is Cancel Action. If the user double-clicks a single item, the Action Log Details window appears.

Clicking this button displays the execution results of previous actions. The number of items that can be displayed is set in the Conditions for Updating List of Action Results window. After the items that are displayed have been changed by using the button, if the user clicks the Update button (including automatic update), only the information for the currently displayed items is refreshed.

Clicking this button refreshes the execution results that are displayed in the list. When the button is clicked, the display position reverts to what it was before the or button was used.

Note that this button is disabled if the items that are displayed have not been changed by using the or button.

Clicking this button displays the execution results of subsequent actions. The number of items that can be displayed is set in the Conditions for Updating List of Action Results window. After the displayed items have been changed by using the button, if the user clicks the Update button (including automatic update), only the information for the currently displayed items is refreshed.

Suppress Trigger Details

This button can be used when Deterrent is displayed as the status or when -RD or -RUD is displayed as the status suffix in the Status column of the action selected in the Log list box. If this button is clicked in these cases, details of the action that triggered the start of suppression are displayed.

The following describes the status suffixes -RD, -RUD, and -D displayed in the Status column:

-RD

This suffix is displayed when a value other than OFF is specified for the -r option of the jcoimdef command and the command is re-executed for the action suppressed during Automatic Action Service startup. This suffix is also displayed when the action log is output to the action re-execution file (example: Ended-RD)

-RUD

This suffix is displayed when the command of a suppressed action is re-executed by clicking Re-execute in the Action Log window or List of Action Results window (example: Ended-RUD).

-D

This suffix is displayed when the status of the command for a suppressed action is Fail. -D is displayed after Fail (example: Fail-D).

When the user selects the action in the Log list box and clicks Suppress Trigger Details, the Action Log Details window opens. This window can be used to check the detailed execution result of the action.

The detailed execution result of an action can be displayed only if Deterrent is displayed as the status or if -RD or -RUD is displayed as the status suffix.

The Suppress Trigger Details button is disabled in the following cases:

When the user selects an action whose status is not Deterrent or whose status suffix is neither -RD nor -RUD

When the user selects multiple actions

Details

Clicking this button displays the detailed execution result of the action selected in the Log list box. The Action Log Details window opens, displaying the detailed execution result.

Re-execute

Clicking this button requests re-execution of an action displayed in the Log list box. The user can use this button to re-execute an action whose status is Cancel, Kill, Error, Deterrent, or Ended.

To use this button, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission.

To request re-execution of an action, the user selects an action in the Log list box and then clicks the Re-execute button. When the Re-execute button is clicked, a dialog box asking whether the user wants to re-execute the action appears. Clicking the OK button in the dialog box completes the request to re-execute the selected automated action.

Hitachi recommends that the user click the Update button after submission of the request to check the status of the action.

The Re-execute button is disabled in the following cases:

When the user selects an action whose status is not Cancel, Kill, Error, Deterrent, or Ended

When the user selects multiple actions

Cancel Action

Clicking this button cancels execution of an action selected in the list of execution results.

The user can use this button to cancel execution of an action whose status is Wait, Queue, or Running. Note that cancellation fails if the version of JP1/Base on the host on which the action is to be executed is 07-00 or earlier.

To use this button, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission.

To request cancellation, the user selects an action in the Log list box and then clicks the Cancel Action button. When the Cancel Action button is clicked, a dialog box asking whether the user wants to cancel execution of the action appears. Clicking the OK button in the dialog box completes the request to cancel execution of the selected automated action. Note that canceling the execution of an action whose status is Wait, Queue, or Running cannot be requested.

Hitachi recommends that the user click the Update button after submission of the request to check the status of the action.

The Cancel Action button is disabled if the status of the selected action is not Wait, Queue, or Running.

After an action has been selected and re-executed, a refresh of the List of Action Results window cancels the selection.

If the size of the action information file containing the information about executed actions exceeds the maximum, the oldest information is overwritten with new information. When old information is overwritten, action execution result information that is displayed in the List of Action Results window might disappear. If the disappearance of information occurs so frequently that operation is hindered, consider increasing the maximum size of the action information file. For details about estimating and setting the maximum size of the action information file, see Automated action environment definition file (action.conf.update) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

3.39 Conditions for Updating List of Action Results window

The Conditions for Updating List of Action Results window is used to change the conditions for displaying the execution results of automated actions in the List of Action Results window.

The Conditions for Updating List of Action Results window is displayed when the user clicks the Update Settings button in the List of Action Results window.

The following figure shows an example of the Conditions for Updating List of Action Results window.

Figure 3‒69: Conditions for Updating List of Action Results window

The following describes the items displayed in the Conditions for Updating List of Action Results window.

Update method

Specifies whether to refresh the List of Action Results window automatically or manually.

If the Update automatically radio button is selected, the window is refreshed automatically. The user specifies the refresh interval in minutes in the Interval text box. The user can specify a value from 1 to 1,440. The default is 1.

If the Update manually radio button is selected, the window is refreshed manually. When manual refresh is selected, the Interval text box is disabled.

The default of the update method is Update automatically.

Updated contents

Specifies which action execution results are to be acquired. One of the following four types can be selected:

Most recent action results

Selecting this radio button acquires the results of the most recently executed actions. The number of action execution results to be acquired is specified in the Num. to display area.

Specified action serial number

Selecting this radio button and specifying the action serial number acquires the execution results of the action with the specified action serial number. After entering the serial number, the user selects Before or After from the drop-down list to specify the range of actions to be displayed. A value from 1 to 2,147,483,647 can be specified as an action serial number.

Selecting Before from the drop-down list acquires the execution results of the actions preceding (and including) the specified action. If Before is selected, JP1/IM - View acquires the preceding execution results starting with the most recent results.

Selecting After from the drop-down list acquires the execution results of the actions following (and including) the specified action. When After is selected, JP1/IM - View acquires the subsequent execution results starting with the oldest results.

The number of action execution results to be acquired is specified in the Num. to display area.

Specify the event-registration time

Selecting this radio button and specifying the time that the JP1 events were registered in the event databases on the event-issuing hosts acquires the execution results of the actions that are registered within the specified timeframe.

The user enters the base time, and then selects either Before or After from the drop-down list.

Selecting Before from the drop-down list acquires the execution results of the actions registered before (and at) the specified time. If Before is selected, JP1/IM - View acquires the previous execution results starting with the most recent results.

Selecting After from the drop-down list acquires the execution results of the actions registered after (and at) the specified time. If After is selected, JP1/IM - View acquires the subsequent execution results starting with the oldest results.

The number of action execution results to be acquired is specified in the Num. to display area.

Specify a time in YYYY/MM/DD hh:mm:ss format. The time you specify must be within the time range that corresponds to 1970/01/01 00:00:00 GMT to 2038/01/19 03:14:07 GMT in the default time zone of the machine.

For example, on a machine whose time zone is set to GMT+9 (Japan), you can specify a value in the range from 1970/01/01 09:00:00 to 2038/01/19 12:14:07.

Specified event arrival time

Selecting this radio button and specifying the time that the JP1 events arrived at the local server acquires the execution results of the actions for which JP1 events arrived at the local server within the specified timeframe.

Selecting Before from the drop-down list acquires the execution results of the actions for which JP1 events arrived before (and at) the specified time. If Before is selected, JP1/IM - View acquires the previous execution results starting with the most recent results.

Selecting After from the drop-down list acquires the execution results of the actions for which JP1 events arrived after (and at) the specified time. If After is selected, JP1/IM - View acquires the subsequent execution results starting with the oldest results.

The number of action execution results to be acquired is specified in the Num. to display area.

Specify the time in YYYY/MM/DD hh:mm:ss format. The time you specify must be within the time range that corresponds to 1970/01/01 00:00:00 GMT to 2038/01/19 03:14:07 GMT in the default time zone of the machine.

For example, on a machine whose time zone is set to GMT+9 (Japan), you can specify a value in the range from 1970/01/01 09:00:00 to 2038/01/19 12:14:07.

Num. to display

Specifies the maximum number of actions that can be displayed in the List of Action Results window. The range of specifiable values is from 1 to 200. The default is 200.

Host

To specify the name of a host on which an action was executed, select the Host check box, and then specify a host name that is no more than 255 bytes. To specify a business group name or monitoring group name, the maximum length is 2,048 bytes.

Multiple hosts, business group names, and monitoring group names can be specified. The maximum of the total number of names that can be specified is 100. To use a comma (,) or backslash (\) as an ordinary character, prefix a backslash (\) as an escape character. That is, to use a comma (,), enter \,. To use a backslash (\), enter \\. Line breaks and tabs cannot be used. Character strings specified in path format are treated as business group names or monitoring group names. However, if the integrated monitoring database and the IM Configuration Management database are disabled at the time of login to JP1/IM, the names specified in path format are treated as host names.

Alphanumeric characters, underscores (_), hyphens (-), periods (.), and commas (,) can be entered in the text box, although the commas (,) can only be used as separators.

Also note that hyphens (-) and periods (.) cannot be used as the last character, and that host group names cannot be specified.

Status

Specifies the execution statuses of the actions to be displayed. To specify execution statuses, the user selects the Status check box, and then selects the check boxes of the statuses that are to be displayed. Multiple statuses can be specified.

The available check boxes are Wait, Send, Queue, Running, Cancel, Kill, Fail, Error, Deterrent, Other, and Ended. The actions displayed by selecting these check boxes include actions with the status suffixes -R, -RU, -RD, -RUD, and -D. For example, when the Running check box is selected, actions in the Running, Running-R, Running-RU, Running-RD, and Running-RUD statuses are displayed.

For details about the statuses that can be selected in this area, see the table under the description of the Log area in 3.37 Action Log Details window.

If Ended is selected, the condition for selecting return codes can also be selected from 0, Not 0, and All.

Canceled status

Specifies whether actions for which cancellation is in progress and actions for which cancellation failed are to be displayed. These actions are displayed in the List of Action Results window when the Canceled status check box, the Included radio button, and either one or both of the Canceling and Miss check boxes are selected.

If Canceling is selected, the actions for which cancellation is in progress are displayed. If Miss is selected, the actions for which cancellation failed are displayed.

When the Not included radio button is selected, the actions for which cancellation is in progress and the actions for which cancellation failed are not displayed.

The default is Not included.

3.40 Execute Command window

The Execute Command window is used to execute commands on a managed host (agent host or manager host) or on the client host (viewer host).

To open the Execute Command window, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission. This window is displayed when one of the following operations is performed:

In the Event Console window, from the Options menu, choose Execute Command.

In the Event Console window, on the tool bar, click .

In the Event Console window, select a JP1 event, and then, from the View menu, choose Execute Command (Event Inheritance).

In the Event Console window, right-click a JP1 event and select Execute Command (Event Inheritance) from the pop-up menu.

In the Event Details window or the Edit Event Details window, click the Execute Command button.

In the Related Events (Summary) window or the Related Events (Correlation) window, right-click a JP1 event and select Execute Command (Event Inheritance) from the pop-up menu.

The following figure shows an example of the Execute Command window.

Figure 3‒70: Execute Command window

Command buttons can be displayed in this window. The following figure shows an example of the Execute Command window in which command buttons are displayed.

Figure 3‒71: Execute Command window (with command buttons displayed)

The following describes the items displayed in the Execute Command window.

Command buttons

Command buttons are buttons for executing commands that are set in the command button definition file. When a command button is clicked, the command associated with the button is executed. Users can specify the names of command buttons. The maximum length of each command button name is eight characters.

When the user hovers the mouse pointer over a command button, the information registered for the Target host, Command, and Environment variable file boxes is displayed. While this information is displayed, the user cannot use the Target host and Command boxes, the Clear History button, the Environment variable file box, and the Execute button. The user who will click a command button must check the displayed information before clicking the button. Note, however, that if the target host name is not registered as a command button, the user can access the Target host box.

When the user right-clicks a command button, a pop-up menu is displayed. The commands that can be executed from the menu include Custom Execution. When Custom Execution is chosen, the information set for the command button is reflected to the Target host, Command, and Environment variable file boxes.

Command buttons can be set to display a confirmation message before command execution or to start execution immediately without displaying the message. On the command buttons that are set to immediate execution, the string Execute is displayed after the button names.

The procedure for setting command buttons is described in the JP1/Integrated Management 3 - Manager Configuration Guide, but the relevant section differs according to the platform. If the platform is Windows, see 1.16 Setting up a command execution environment (for Windows). If the platform is UNIX, see 2.15 Setting up a command execution environment (for UNIX).

Command type

The type of the command to be executed is selected from the following radio buttons. This field is not displayed when the version of the connected JP1/IM - Manager is earlier than 10-00.

Command of managed host

Select this radio button to execute a command on a managed host (agent host or manager host).

Client application

Select this radio button to execute a client host (viewer host).

Event information to inherit

This area displays the event that the command will inherit (event to be inherited). This field is not displayed when the version of the connected JP1/IM - Manager is earlier than 10-00.

The event to be inherited can be changed by performing one of the following operations:

In the Event Console window, select a JP1 event, and then, from the View menu, choose Execute Command (Event Inheritance).

In the Event Console window, select and right-click a JP1 event, and then choose Execute Command (Event Inheritance).

In the Event Details window or the Edit Event Details window, click the Execute Command button.

In the Related Events (Summary) window or the Related Events (Correlation) window, select and right-click a JP1 event, and then choose Execute Command (Event Inheritance).

Inherit event information

Select this check box if the command needs to inherit the event information during execution.

If this check box is not selected, the command will not inherit event information.

Target host

Specifies the name of a host on which a command is to be executed. The host name specified in the box cannot exceed 255 bytes and must be a host name that is set as a managed host in the system configuration definition. This text box is disabled when the Client application radio button is selected. If the function for restricting reference permissions and operation permissions is enabled for business groups (ON is set for the -bizmonmode option of the jcoimdef command), specify the name of a host that belongs to a business group that the logged-in JP1 user can view. For details about the jcoimdef command, see jcoimdef in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

A host group name that is defined in the host group definition file can be specified.

A business group name or monitoring group name that has no more than 2,048 bytes can also be specified. If a character string in path format is specified, the character string is treated as a business group name or monitoring group name. However, if the integrated monitoring database and the IM Configuration Management database are disabled, the specified character string is treated as a host name or host group name even if the string is in path format.

A host name specified in the past can be selected from the drop-down list. A maximum of five hosts per viewer specified in the past can be stored for one user.

Note that commands executed via command buttons are not recorded in the command history.

The attribute information for a JP1 event displayed in Event information to inherit can also be specified by using a variable. For example, if you want to execute a command on the event-issuing host, specify $EVHOST. For details about the variables that can be specified, see 4.19.5 Inheriting event information when a command is executed in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Note:

A large number of agents are requested at once to execute a command, a heavy load might be applied on the manager host. To reduce the load, we recommend that you divide the agents into host groups each of, and then execute the command for each group.

Command

Specifies the command line to be executed.

The command line specified in the box cannot exceed 4,096 bytes. Note, however, that the maximum length of the command that can be executed from JP1/IM - View depends on the system that runs JP1/IM and JP1/Base.

The attribute information for a JP1 event displayed in Event information to inherit can also be passed to the command as a parameter of the command by using a variable. For details about the variables that can be specified, see 4.19.5 Inheriting event information when a command is executed in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

If the Command of managed host radio button is selected in the Command type area:

A command line specified in the past can be selected from the drop-down list.

This drop-down list displays the last five command lines that were specified when the Command of managed host radio button was selected.

A maximum of five command lines per viewer specified in the past can be stored for one user. Note, however, that commands executed via command buttons are not recorded in the command history.

The following describes the types of commands that can be specified for Command.

On a Windows host, the following types of commands can be executed:

Executable files (.com and .exe)

Batch files (.bat)

Script files of JP1/Script (.spt) (An association must be set for .spt files so that they can be executed.)

Data files (such as .vbs) that have file types (extensions) associated with applications that can be executed by an automated action

On a UNIX host, the following types of commands can be executed:

UNIX commands

Shell scripts

Note that the following commands cannot be executed:

Commands requiring user interaction

Commands displaying windows

Commands with an escape sequence or control code specified

Commands that do not stop, such as daemons

Windows message functionality, DDE commands, and other commands requiring interaction with the Desktop (in Windows only)

Commands that shut down the OS, such as shutdown and halt

If the Client application radio button is selected in the Command type area:

A command line specified in the past can be selected from the drop-down list.

This drop-down list displays the last five command lines that were specified when the Client application radio button was selected.

A maximum of five command lines per viewer specified in the past can be stored for one user. Note, however, that commands executed via command buttons are not recorded in the command history.

Clear History

Clicking this button clears all command lines specified in the past from the drop-down list. This button can be used when there is no need to save the history of commands executed in the past.

If the Command of managed host radio button has been selected, the history of command lines that were executed when the Command of managed host radio button was selected is cleared.

If the Client application radio button has been selected, the history of command lines that were executed when the Client application radio button was selected is cleared.

Environment variable file

Specifies the name of the environment variable file saved on the host on which the command is executed. Specify a full path name of 255 or fewer bytes. This text box is disabled when the Client application radio button is selected.

Environment variables are set as specified in the file before the command is executed.

The attribute information for a JP1 event displayed in Event information to inherit can also be passed to the command as a parameter of the command by using a variable. For details about the variables that can be specified, see 4.19.5 Inheriting event information when a command is executed in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Execute

How the system behaves when this button is clicked differs depending on whether the Inherit event information check box in the Event information to inherit area is selected:

If the Inherit event information check box is selected:

Clicking this button opens the Preview Command Execution Content window.

If the Inherit event information check box is not selected:

Clicking this button executes the specified command.

Log

This area displays the results of commands that were executed by clicking the Execute button or a command button. The time the command was executed, the name of the host on which the command was executed, and the message output to the standard output or standard error output are displayed. When a list header (Time, Host, or Message) is clicked, the list is sorted by time, host name, or message.

The results of commands executed from the Execute Command window are displayed in the list box until the window is closed.

The maximum number of items that can be displayed in the Log area is set by Lines of execution results to display in the Preferences window. If the maximum number of items that can be displayed in this area is exceeded, the oldest item, regardless of the sort order, is deleted.

Clear

Clicking this button clears the command execution results listed in the Log area.

3.41 Preview Command Execution Content window

The Preview Command Execution Content window is used to preview the result of executing the command specified in the Execute Command window. In the Preview Command Execution Content window, variables in the command are replaced with the corresponding event information. The user can use this window to check whether the variables in the command will be replaced correctly and check for any problems with command execution before executing the command.

Figure 3‒72: Preview Command Execution Content window (when "Command of managed host" is selected in the Execute Command window)

Figure 3‒73: Preview Command Execution Content window (when "Client application" is selected in the Execute Command window)

The Preview Command Execution Content window is displayed when the Execute button or a command button is clicked while the settings in the Execute Command window satisfy the following conditions:

Inheritance of event information is enabled.

The event to be inherited is selected.

If Command of managed host is selected, the Target host and Command values are specified. If Client application is selected, the Command value is specified.

The following describes the items displayed in the Preview Command Execution Content window.

,

Either of these icons followed by a message indicates the status of the command execution result. The icon is displayed if all specified variables are replaced with event information successfully. The icon is displayed if variable replacement fails or truncation of character strings occurs after replacement.

Command type

This area displays the type of the displayed command. Either Command of managed host or Client application is displayed.

Target host

This area displays the target host name. If variables are used, the corresponding event information is displayed instead of the variables.

This area appears only if Command of managed host is displayed in the Command type area.

Note that the length of the target host name after replacing variables with the corresponding event information might exceed the maximum length of the Target host value that can be specified in the Execute Command window. If the maximum length is exceeded, the target host name displayed in the Preview Command Execution Content window is truncated to the maximum length.

If a truncated target host name is displayed in the Preview Command Execution Content window, the Initialize with Pre-truncated Values button is displayed.

The maximum length of a character string that can be handled in this area is 20,480 bytes in terms of the character encoding used on the manager host. The specifiable values and the maximum value are the same as for Target host in the Execute Command window. For details, see the description of the Target host area in 3.40 Execute Command window.

Also note that in the Preview Command Execution Content window, the user cannot specify any variables that inherit event information.

If either of the following conditions is satisfied when the Preview Command Execution Content window opens, the icon is displayed:

The target host name includes variables that could not be replaced with event information.

The target host name is truncated to the maximum length of the Target host value that can be specified in the Execute Command window.

Initialize with Pre-truncated Values

This button appears if a truncated target host name is displayed in the Target host area when the Preview Command Execution Content window opens.

If this button is clicked, the target host name before truncation is displayed in the text box in the Target host area. Note, however, that the capacity of the text box is 20,480 bytes. If the length of the target host name before truncation exceeds 20,480 bytes, the target host name is truncated to 20,480 bytes.

If this truncation occurs, the KAVB1036-W message is displayed.

Initialize with Default Values

After the character string displayed in Target host has been changed, clicking this button resets the character string to the initial value that was displayed when the Preview Command Execution Content window was opened.

Command

The text box in this area displays the command that will be executed. In the displayed command, variables are replaced with the corresponding event information.

Note that the length of the command string after replacing variables with event information might exceed the maximum length of the Command value that can be specified in the Execute Command window (4,096 bytes#). If the maximum length is exceeded, the command string is truncated to the maximum length.

If a truncated command string is displayed in the Preview Command Execution Content window, the Initialize with Pre-truncated Values button is displayed.

The maximum length of a character string that can be handled in this area is 20,480 bytes#. The specifiable values and the maximum value are the same as for Command in the Execute Command window. For details, see the description of the Command text box in 3.40 Execute Command window.

Also note that in the Preview Command Execution Content window, the user cannot specify any variables that inherit event information.

If either of the following conditions is satisfied when the Preview Command Execution Content window opens, the icon is displayed:

The command string includes variables that could not be replaced with event information.

The command string is truncated to the maximum length of the Command value that can be specified in the Execute Command window.

#:

If Command of managed host is displayed in Command type, the maximum length is based on the character encoding used on the manager host. If Client application is displayed in Command type, the maximum length is based on the character encoding used on the viewer host.

Initialize with Pre-truncated Values

This button appears if a truncated command string is displayed in the Command area when the Preview Command Execution Content window opens.

If this button is clicked, the command string before truncation is displayed in the text box in the Command area. Note, however, that the capacity of the text box is 20,480 bytes. If the length of the command string before truncation exceeds 20,480 bytes, the command string is truncated to 20,480 bytes.

If this truncation occurs, the KAVB1036-W message is displayed.

Initialize with Default Values

After the character string displayed in Command has been changed, clicking this button resets the character string to the initial value that was displayed when the Preview Command Execution Content window was opened.

Environment variable file

The text box in this area displays the environment variable file name with variables replaced with the corresponding event information.

This area appears only if Command of managed host is displayed in Command type.

Note that the length of the environment variable file name after replacing variables with event information might exceed the maximum length of the Environment variable file value that can be specified in the Execute Command window (255 bytes). If the maximum length is exceeded, the environment variable file name is truncated to the maximum length.

If a truncated environment variable file name is displayed in the Preview Command Execution Content window, the Initialize with Pre-truncated Values button is displayed.

The maximum length of a character string that can be handled in this area is 20,480 bytes#. The specifiable values and the maximum value are the same as for Environment variable file in the Execute Command window. For details, see the description of the Environment variable file text box in 3.40 Execute Command window.

Also note that in the Preview Command Execution Content window, the user cannot specify any variables that inherit event information.

If either of the following conditions is satisfied when the Preview Command Execution Content window opens, the icon is displayed:

The environment variable file name includes variables that could not be replaced with event information.

The environment variable file name is truncated to the maximum length of the Environment variable file value that can be specified in the Execute Command window.

Initialize with Pre-truncated Values

This button appears if a truncated environment variable file name is displayed in the Environment variable file area when the Preview Command Execution Content window opens.

If this button is clicked, the environment variable file name before truncation is displayed in the text box in the Environment variable file area. Note, however, that the capacity of the text box is 20,480 bytes. If the length of the environment variable file name before truncation exceeds 20,480 bytes, the file name is truncated to 20,480 bytes.

If this truncation occurs, the KAVB1036-W message is displayed.

Initialize with Default Values

After the environment variable file name displayed in Command has been changed, clicking this button resets the file name to the initial value that was displayed when the Preview Command Execution Content window was opened.

Execute

Click this button to execute the specified command.

3.42 Event-Information Mapping Definitions window

The Event-Information Mapping Definitions window is used to map items displayed in the event list with program-specific extended attributes so that the extended attributes can be displayed in the corresponding columns of the event list.

To open the Event-Information Mapping Definitions window, the user must have JP1_Console_Admin permission.

If the function for restricting reference permissions and operation permissions is enabled for business groups, this operation might not be performed depending on the combination of the JP1 resource group and permission level. For details, see 4.1.4(2) Assigning a JP1 resource group and permission level to a JP1 user in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

This window is displayed when the user chooses Options from the menu bar of the Event Console window and then Event-Information Mapping Definitions.

The following figure shows an example of the Event-Information Mapping Definitions window.

Figure 3‒74: Event-Information Mapping Definitions window

The following describes the items displayed in the Event-Information Mapping Definitions window.

Mapping

Specifies whether to enable mapping between the display items and program-specific extended attributes. Selecting Map enables the mapping.

List of definitions

This area lists the event-information mapping definitions that have already been set. A mapping definition is displayed on each line. A maximum of 16 definitions can be set.

If an event-information mapping definition is double-clicked in the list, the Event-Information Mapping Detailed Definitions window appears.

Add

Clicking this button allows the user to add a new event-information mapping definition. When this button is clicked, the Event-Information Mapping Detailed Definitions window appears.

Edit

To edit an event-information mapping definition that appears in the List of definitions area, select the definition in the list and click the Edit button. When this button is clicked, the Event-Information Mapping Detailed Definitions window appears.

Delete

To delete an event-information mapping definition that appears in the List of definitions area, select the definition in the list and click the Delete button.

3.43 Event-Information Mapping Detailed Definitions window

The Event-Information Mapping Detailed Definitions window is used to create an event-information mapping definition that maps a display item and a program-specific extended attribute.

This window is opened from the Event-Information Mapping Definitions window when the Add or Edit button is clicked or when an even-information mapping definition is double-clicked in List of definitions.

The following figure shows an example of the Event-Information Mapping Detailed Definitions window.

Figure 3‒75: Event-Information Mapping Detailed Definitions window

The following describes the items displayed in the Event-Information Mapping Detailed Definitions window.

Display item

This text box is used to select which item displayed in the event list that the specified program-specific extended attribute is to be mapped to.

You can select one of the following items, which can be selected in the Preferences window:

Source process ID, Arrived time, Source user ID, Source group ID, Source user name, Source group name, Source host, Source serial number, Event level, User name, Product name, Object type, Object name, Root object type, Root object name, Occurrence, Start time, or End time

Example: Source host

Program-specific extended attribute

Specifies the program-specific extended attribute to be mapped to the selected display item. For details about the program-specific extended attributes that can be specified, see 3.1 Attributes of JP1 events in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

To map a program-specific extended attribute to Arrived time, Start time, or End time, the user must specify an attribute whose value is a numeric value indicating the number of seconds from 1/1/1970 00:00:00 UTC in the range from 0 to 4,102,444,799. If the value of the specified attribute is not a numeric value or is outside the range, the previously entered attribute is displayed.

Attribute name

This area becomes available if you select the Attribute name radio button.

The attribute name specified in this area can have a maximum of 32 bytes, and can consist of upper-case alphabetic characters, numeric characters, and underscores (_). If a lower-case alphabetic character is entered, it is automatically converted to the corresponding upper-case alphabetic character. The attribute name must begin with an upper-case alphabetic character and does not need to include E that indicates an extended attribute.

Only one program-specific extended attribute can be mapped to one display item.

Example: LOGHOST

Item name

Specifies the condition of a program-specific extended attribute by using an item name.

This area becomes available if you select the Item name radio button.

Specify the condition by selecting an item name from the Item name drop-down list. The displayed item names are program-specific extended attributes specified for the standard file and the extended file of the definition file for extended event attributes.

Event ID

Specifies the IDs of the JP1 events for which the specified displayed item and attribute name are to be mapped. Each event ID is specified by using 1 to 8 hexadecimal numbers. You can specify a value in the range from 0 to 7FFFFFFF. A maximum of 100 event IDs can be specified. Multiple event IDs require a comma (,) as a separator.

Example 1: 3FFF

Example 2: 12345B,7FFFFFFF

3.44 Windows displayed during management of response-waiting events

This section describes the windows listed below. It focuses on the items that change when the response-waiting event management function is enabled and the setting that allows users to respond to and work with response-waiting events is enabled. Note that the response-waiting event management function can be set up when linkage with BJEX or JP1/AS is used.

Event Console window

Event Details window

Enter Response window

Related Events windows

Preferences window

Event Search Conditions window

Filter condition definition windows

Settings for Event Receiver Filter window

Severe Event Definitions window

Settings for View Filter window

The window components and specifications that are not described here, including how to open the windows, are the same as when the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events are disabled. For information such as those, see 1. Window Transitions and Login Window.

3.44.1 Window transitions

The figure below shows JP1/IM - View window transitions when linkage with BJEX or JP1/AS is enabled. The Login window and the View List of Filters window in the figure are not described in this section.

Figure 3‒76: JP1/IM - View window transitions

3.44.2 Event Console window

The Event Console window provides the pages listed below. These pages display the various response-waiting events. Note that the Response-Waiting Events page is displayed only when the response-waiting event management function and the Response-waiting event option in the Preferences window are enabled.

Monitor Events page

Severe Events page

Search Events page

Response-Waiting Events page

Note that if the function for restricting reference permissions and operation permissions is enabled, the above pages display only the JP1 events that occurred in the business group that the user is in charge of. For details about this function, see 4.1.4 Restrictions on viewing and operating business groups in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

For response-waiting events, the JP1 event type column displays icons.

The following table describes the menu items that are added to the Event Console window when the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events are enabled.

Table 3‒25: Menu items added to the Event Console window

Menu

Command

Description

View

Enter Response

Displays the Enter Response window for the selected response-waiting event.

Users that have JP1_Console_Operator or higher permission can execute this command.

Note that this command can be executed only when all of the following conditions exist:

The Response-Waiting Events page or the Search Events page is open.

If the Search Events page is open, the user must have logged in to the search-target Manager host.

Only one event is selected.

The selected JP1 event is a response-waiting event.

Remove Accumulated Events

Releases the selected response-waiting events from the hold-and-accumulate state.

Users that have JP1_Console_Operator or higher permission can execute this command.

Note that this menu can be executed only in the following case:

The Response-Waiting Events page is open.

Options

Function-Status Notification Return

Monitor Accumulation Status

Restarts monitoring the accumulation status of response-waiting events.

Users that have JP1_Console_Admin permission can execute this command.

Note that this menu item is disabled in the following case:

The number of accumulated events does not exceed 2,000.

(1) Response-Waiting Events page

The Response-Waiting Events page displays a list of response-waiting events that users have not responded to yet.

Figure 3‒77: Response-Waiting Events page of the Event Console window

The following describes the items displayed in the Event Console window.

Accumulation status

This area displays the accumulation status of response-waiting events. This area displays nothing while the number of accumulated response-waiting events does not exceed 2,000. When 2,000 is exceeded, this area displays a message to that effect (KAVB0551-E). The message continues to be displayed until the status monitoring is restarted.

Event list

This list box displays the following response-waiting events:

Response-waiting events that have been accumulated in JP1/IM - Manager (users have not responded)

Response-waiting events that have passed through the event acquisition filter

Response-waiting events that have passed through the user filter for the logged-in JP1 user

When you change the status of response-waiting events or release response-waiting events from the hold-and-accumulate state, you can perform that operation for a maximum of 2,000 response-waiting events at the same time.

Indicator

The color of the event indicator in the Response-Waiting Events tab shows whether there are response-waiting events. Green means that there are response-waiting events, and gray means that there are not.

3.44.3 Event Details window

The Event Details window displays detailed attribute information about a JP1 event.

If the function for restricting reference permissions and operation permissions is enabled, this window displays only information about JP1 events that occurred in the business group that the user is in charge of. For details about this function, see 4.1.4 Restrictions on viewing and operating business groups in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The following figure shows the Event Details window.

Figure 3‒78: Event Details window

The following describes the items that are displayed when the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events are enabled.

Enter Response

Click this button to open the Enter Response window for the selected response-waiting event. This button is enabled when all of the following conditions exist:

The displayed JP1 event is a response-waiting event.

The Event Details window was opened from the Response-Waiting Events page, Search Events page, or a Related Events window (list of events that can be responded in the previous window).

The logged-in JP1 user has JP1_Console_Operator or higher permission.

Important

If you start the Event Details window by using Ctrl + Enter key soon after you close the Event Details window, the Event Console window of the WWW page version may freeze, or may not be rendered.If you close the Event Details window, wait for a few seconds before starting the Event Details window. If the Event Console window of the WWW page version freezes, close "JP1 Central Console" from the Applications tab or the Processes tab of Task Manager to restart it.

3.44.4 Enter Response window

The Enter Response window is used to enter a response to a response-waiting event. To open this window, you need JP1_Console_Operator or higher permission.

You can open the Enter Response window in the following ways:

In the Event Console window, select a response-waiting event, and from the menu bar, select View and then Enter Response.

In the Event Console window or a Related Events window, right-click a response-waiting event and select Enter Response from the pop-up menu.

In the Event Details window, click the Enter Response button.

The following figure shows the Enter Response window.

Figure 3‒79: Enter Response window

The following describes the items displayed in the Enter Response window.

Response attributes

This area displays information necessary to respond to a response-waiting event.

Event database serial number

Shows the sequence number assigned to the response-waiting event in the event database.

Status

Shows the status of the process that issued the response-waiting event.

READY TO RESPOND: You can respond to the event because the process that issued the event exists.

NO LONGER MANAGED BY BJEX or NO LONGER MANAGED BY JP1/AS: You cannot respond to the event because the process that issued the event does not exist.

RESPONDED SUCCESSFULLY: Response to the process was successful. (This is displayed only in the Enter Response window in which the response was made.)

ALREADY RESPONDED: Response to the process has already finished. (This is displayed only when the Enter Response window was displayed or refreshed for a response-waiting event which has already been responded to.)

Message

Displays the message in the response-waiting event.

Message after the change/Message before the change

You can use the radio buttons to switch the message to be displayed between the message that was changed by the display message change function and the message before the change. If you select the Message after the change radio button, the changed display message is displayed. If you select the Message before the change radio button, the message before the change is displayed.

If the changed display message does not exist (that is, the event was received when the display message change function was disabled or paused), the radio buttons are unavailable with the Message before the change radio button selected.

When you display the Enter Response window, the Message after the change radio button is selected.

If the IM database has not been updated by using the jimdbupdate command after an upgrade installation was performed from version 10-50 or earlier, the radio buttons are unavailable with the Message before the change radio button selected.

Response

Enter a response.

You can enter a string that has 512 or fewer bytes.

You can use ASCII codes in the range from 0x20 to 0x7E.

You can use only the UTF-8 encoding.

Respond

Click this button to execute the response that you entered. When a dialog box asking you whether to respond appears, click the Yes button. The entered response will be executed. For details about the response mechanism, see 11.2.4 Responding to response-waiting events in the JP1/Integrated Management 3 - Manager Administration Guide.

3.44.5 Related Events windows

There are the following two Related Events windows:

Related Events (Summary) window

This window displays repeated events for consolidation events when suppression of monitoring of repeated events or consolidated display of repeated events is enabled.

Related Events (Correlation) window

This window uses the correlation event generation function to display a list of correlation source events for correlation events.

If the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events are enabled, the menu items listed in the table below are added.

Note that if the function for restricting reference permissions and operation permissions is enabled, the Related Events windows displays only the JP1 events that occurred in the business group that the user is in charge of. For details about this function, see 4.1.4 Restrictions on viewing and operating business groups in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Table 3‒26: Pop-up menu items added to Related Events windows

Menu

Command

Description

View

Enter Response

Displays the Enter Response window for the selected response-waiting event.

Users that have JP1_Console_Operator or higher permission can execute this command.

Note that this command can be executed only when all of the following conditions exist:

The Related Events window was opened from the Response-Waiting Events page of the Event Console window. Alternatively, the Related Events window was opened from the Search Events page of the Event Console window, and the Manager host that the user has logged in to was being searched from that page.

Only one event is selected.

The selected JP1 event is a response-waiting event.

Note that the displayed Enter Response window is always dimmed, and users can only view the information displayed in the window.

Remove Accumulated Events

This item is always disabled.

3.44.6 Preferences window

The Preferences window is used to specify user preferences, such as whether to automatically refresh the event list in the Event Console window and the items to be displayed in the event list.

The following figure shows the Preferences window.

Figure 3‒80: Preferences window

The following describes the items displayed in the Preferences window when the response-waiting event management function is enabled.

Response-waiting event

This area contains the check box that determines whether to allow users to respond to and work with response-waiting events. To allow response or manipulation for response-waiting events, select the check box.

If you select the check box that is cleared, the change of the setting is applied to JP1/IM - View when you click the OK button.

If you clear the check box that is selected, the change of the setting is applied to JP1/IM - View when you log in to JP1/IM - Manager again after clicking the OK button.

3.44.7 Event Search Conditions window

The Event Search Conditions window is used to set JP1 event search conditions. The following figure shows this window.

Figure 3‒81: Event Search Conditions window

The following describes the items that are displayed when the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events are enabled.

Response-waiting event

The options in this area can be used to determine whether to include response-waiting events in search targets or exclude response-waiting events from search targets.

Important

If you start the Event Search Conditions window by using Ctrl + F key soon after you close the Event Search Conditions window, JP1/IM - View may freeze, or may not be rendered. If you close the Event Search Conditions window, wait for a few seconds before starting the Event Search Conditions window. If the Event Console window of the WWW page version freezes, close "JP1 Central Console" from the Applications tab or the Processes tab of Task Manager to restart it.

3.44.8 Filter condition definition windows

The items for filtering response-waiting events are displayed in the filter condition definition window for a filter when specific conditions are satisfied. The following table describes the conditions for each filter.

Table 3‒27: Conditions for filtering response-waiting events

Filter

Condition definition window

Condition

Event receiver filter

Settings for Event Receiver Filter window

The response-waiting event management function is enabled.

Severe event filter

Severe Event Definitions window

The response-waiting event management function is enabled.

View filter

Settings for View Filter window

The response-waiting event management function is enabled.

The setting that allows users to respond to and work with response-waiting events is enabled.

The following figure shows the items displayed in the filter condition definition windows when the necessary conditions are satisfied.

Figure 3‒82: Items displayed in the filter condition definition windows

Response-waiting event

The options in this area can be used to show or hide response-waiting events.

4 Monitoring Tree Window

This chapter describes the items displayed and defined in the Monitoring Tree window.

4.1 Overview of the Monitoring Tree window

The Monitoring Tree window appears when the user logs in to JP1/IM - Manager (Central Scope) from the Login window with Central Scope selected or when the user clicks on the toolbar of the Login window.

Note that some windows, buttons, and other items might not be enabled or displayed, depending on the version of JP1/IM - Manager (Central Console). For details, see Appendix H. Connectivity with Previous Versions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The Monitoring Tree window provides a tree view for visually and centrally monitoring the system status. Nodes in the tree can be grouped on a monitored server basis or on a server basis. If a failure occurs, the system administrator can drill down through the tree to identify the cause of the failure or check the applications affected by the failure. The Monitoring Tree window can also be used to launch related programs.

If virtualization configuration information is imported, the Monitoring Tree window can be used to monitor a virtualized system.

The following figure shows an example of the Monitoring Tree window.

Figure 4‒1: Monitoring Tree window

The following describes the items displayed in the Monitoring Tree window.

Title bar

The following two kinds of information are displayed in the title bar of the Monitoring Tree window:

About JP1/IM - View

The data version of the monitoring tree in the Monitoring Tree window is displayed in the title bar.

Note that the version displayed in the title bar is the data version of the server's monitoring tree, and is not a product version.

Login information

Login information is displayed in the following format:

Login information: user-name@host-name (or IP-address)

Alarm indicator

Flashes if a failure occurs in the monitored application system.

The following table describes the conditions that cause the alarm indicator to flash under the default settings.

Table 4‒1: Conditions that cause the alarm indicator to flash

Setting and status of the top node

Alarm indicator state

Whether monitoring enabled

Application status

Enabled (Monitoring)

Warning, Normal, Debug, or Initial

Not lit

Enabled (Monitoring)

Emergency, Alert, Critical, or Error

Flashing

Disabled (Not monitoring)

Initial#

Not lit

#: The status of node set to Not monitoring is always Initial.

You can change the conditions that cause the alarm indicator to flash. For details, see System profile of Central Scope (jcs_sysprofile_xxx.def) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Toolbar

Provides buttons for executing functions that are frequently used in the Monitoring Tree window.

(Update Tree to Latest Status button)

Reads the tree configuration information from the connected JP1/IM - Manager (Central Scope), and refreshes the tree with the information. If this button is clicked when tree nodes are open, only the top and second-level nodes are displayed. The third-level and lower nodes are not displayed.

(Visual Monitoring button)

Displays the Open Visual Monitoring Window window.

(Start Integrated Function Menu button)

Displays the Tool Launcher window.

(Central Console)

Displays the Event Console window.

(Help button)

Displays the manual.

The user can customize the toolbar in the Monitoring Tree window by editing three definition files. For details, see the following references:

Start program definition file (!JP1_CS_APP0.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference

Toolbar definition file (!JP1_CS_FTOOL0.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference

Icon operation definition file (!JP1_CS_FTREE0.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference

Tree display area

Displays the elements that make up the application system that is monitored in a tree structure. The following table describes the items displayed in the tree display area.

Table 4‒2: Items displayed in the tree display area

Item

Description

Plus sign (+) icon

A plus sign (+) icon is displayed beside a group node (monitoring group) that has child nodes when the child nodes are not displayed.

When the plus sign (+) icon is clicked, the group node is expanded to show the child nodes, and the icon changes to a minus sign (-) icon.

Minus sign (-) icon

A minus sign (-) icon is displayed beside a group node (monitoring group) that has child nodes when the child nodes are displayed.

When the minus sign (-) icon is clicked, the group node is collapsed to hide the child nodes, and the icon changes to a plus sign (+) icon.

Monitoring group

A tree node that has or can have child nodes. When a monitoring group has child nodes, a plus sign (+) or minus sign (-) icon is displayed beside the monitoring group.

When a monitoring group is selected in the tree display area, the child nodes are displayed in the details display area. If the monitoring group has no child nodes, nothing is displayed in the details display area.

When a collapsed monitoring group is double-clicked, the monitoring group is expanded to show the child nodes.

When an expanded monitoring group is double-clicked, the monitoring group is collapsed to hide the child nodes.

Monitoring object

A bottom-level tree element that has no child nodes. A plus sign (+) or minus sign (-) icon is not displayed beside this element.

When a monitoring object is selected in the tree display area, the detailed information of the monitoring object is displayed in the details display area.

When a monitoring object is double-clicked, the Properties window opens, and displays the attributes of the monitoring object.

Virtual root node

When the logged-in user's monitoring range in the tree is set and enabled, the nodes that the user can monitor are displayed in a tree structure under a top-level node called a virtual root node, which is indicated by (or ).

When the virtual root node is selected in the tree display area, the child nodes of the virtual root node are displayed in the details display area. If the virtual root node has no child nodes, nothing is displayed in the details display area.

Details display area

Displays the child nodes of a monitoring group or virtual root node selected in the tree display area, or displays the details of a monitoring object selected in the tree display area. The displayed details include node name, node type, application status, whether monitoring is enabled, and time status last updated. The details display area is displayed in map mode when is clicked and in list mode when is clicked.

When a monitoring group is double-clicked in the details display area, the child nodes are displayed. At the same time, the corresponding monitoring group in the details display area is expanded.

When a monitoring object is double-clicked in the details display area, the Properties window opens, and displays the attributes of the monitoring object.

The nodes displayed in list mode can be sorted by status (Emergency, Alert, Critical, Error, Warning, Normal, Debug, and Initial, in this order). The nodes are sorted by status when the user chooses View from the menu bar, Sort Status, and then Sorted.

The following table describes the items displayed in the details display area.

Table 4‒3: Items displayed in the details display area

Item

Description

Icons

The icons of monitoring nodes are displayed.

If icons overlap in map mode, the icon of a node with a higher node ID is displayed in front of the icon of a node with a lower node ID. If a check mark is displayed for Visual Icon display on the View menu, icons are displayed in the order specified in the Monitoring Tree (Editing) window.

Visual Icon

If a check mark is displayed for Visual Icon display on the View menu, the Visual Icon is displayed for the monitoring node.

This information is displayed only in map mode.

If Visual Icon overlap in this area, they are displayed in the order specified in the Monitoring Tree (Editing) window.

Monitoring Node Name

The name of each monitoring node is displayed.

Monitoring Node Type

The type of each monitoring node is displayed. A monitoring group, which is a group of nodes, is indicated as Monitoring Group. Monitoring objects are indicated as AJS Monitoring Object, SSO Monitoring, or User Monitoring Object. This information is not displayed in map mode.

Status

The status of the application monitored by each monitoring node is displayed. Emergency, Alert, Critical, Error, Warning, Normal, Debug, or Initial can be displayed.

This information is not displayed in map mode.

Monitoring

Whether monitoring by the monitoring node is enabled is displayed. If monitoring is enabled, Monitoring is displayed. If monitoring is disabled, Not monitoring is displayed.

This information is not displayed in map mode.

Last Status Update

The date on which the node status was last updated is displayed.

This information is not displayed in map mode.

(Move to Upper Monitoring Group button)

Clicking this button selects the parent node of a node selected in the tree display area. The focus moves to the parent node in the tree display area, and the details of the parent node are displayed in the details display area.

(Icon View button)

Clicking this button switches the details display area to map mode, in which the information of the monitoring group or monitoring object selected in the tree display area is displayed in map format. Icons are placed at the locations set in the Monitoring Tree (Editing) window. The icons can also be moved in the details display area in map mode, but the locations of the icons are reset when the Monitoring Tree window is closed.

(Detailed View button)

Clicking this button switches the details display area to list mode, in which the information of the monitoring node selected in the tree display area is displayed in list format.

(Select Block button)

Clicking this button allows the user to select the icons of multiple monitoring groups or monitoring objects displayed in map mode at the same time. When this button is clicked, the user can draw a rectangle by dragging to enclose the icons. All the icons in the rectangle are selected. This button is disabled in list mode.

(Set in Equal Intervals button)

Clicking this button temporarily aligns the icons of monitoring groups or monitoring objects displayed in map mode at equal intervals. The icons are reset to their former locations when the Monitoring Tree window is closed. This button is disabled in list mode.

Search Status-Change Events

Clicking this button displays the events that caused the node status to change in the Event Console window. Events are selected based on the conditions set in the event receiver filter. The event receiver filter settings can be checked in the Settings for Event Receiver Filter window. This button is disabled when a virtual root node is selected.

Pop-up menu

In the tree display area and details display area, the user can select and right-click a node to display a pop-up menu. If the selected node is a virtual root node, the pop-up menu appears, but the menu does not contain any items that can be chosen.

The following item on the pop-up menu appears only if specific conditions are met.

Display Order

This item can be chosen if a check mark is displayed for Visual Icon display on the View menu. Even if multiple monitoring nodes have been selected, the user can choose this item.

The user can temporarily change the Display Order of a monitoring node by choosing the following commands. If the user closes the window, and then opens it again, the Display Order is reset to the one specified in the Monitoring Tree (Editing) window.

Move to the foremost

The selected monitoring node is displayed in the front.

Move 1 level upward

The selected monitoring node moves forward one position in the Display Order.

Move 1 level backward

The selected monitoring node moves back one position in the Display Order.

Move to the backmost

The selected monitoring node moves to the backmost position in the Display Order.

For details about other items appearing on the pop-up menu, see the explanations below of the corresponding menu items available from the menu bar.

The following table describes the menu items available from the menu bar of the Monitoring Tree window.

Table 4‒4: Menu items available from the menu bar of the Monitoring Tree window

Menu

Command

Description

File

Save Monitoring-Tree Status

Saves the status information (such as Normal and Error) and common conditions of the displayed nodes in a CSV file on the local computer as a tree configuration file. When the logged-in user's monitoring range in the tree is set and enabled, the user cannot choose this menu item.

Central Console

Opens the Event Console window.

When the Event Console window opens, a user who has logged in to JP1/IM - Manager (Central Scope) is logged in to the window. No Login window appears.

If the Event Console window is displayed within a process, the Event Console window is displayed in front.

Close

When the Event Console window has been displayed by choosing Central Console from the File menu or by clicking , and the user executes the Close command, following occurs:

The Monitoring Tree window is hidden.

If the Tool Launcher window is displayed, it continues to be displayed.

When the Monitoring Tree window has not been displayed by choosing Central Console from the File menu or by clicking , and the user executes the Close command, the following occurs:

The KAVB0122-I message is displayed in a dialog box. The user can log out by clicking Yes.

If the Tool Launcher window is displayed, it closes.

Exit, Logout

Lets the user log out from JP1/IM - Manager (Central Scope), and closes the window that is currently displayed. When the Event Console window is displayed, it closes after the Monitoring Tree window closes.

Operation

Change Status

Lets the user change the status of a node selected in the Monitoring Tree window. A check mark indicates the current status, which the user can change by choosing another status.

Change Monitoring Status

Lets the user select the monitoring status of a monitoring node selected in the Monitoring Tree window from the following statuses:

Monitoring

Monitoring by the monitoring node is enabled.

Not monitoring

Monitoring by the monitoring node is disabled.

A check mark indicates the current status, which the user can change by choosing the other status.

If the monitoring status of a parent node is changed, the monitoring status of the child nodes is also changed.

View

Icon View

Switches the details display area to map mode, in which the information for the monitoring group or monitoring object selected in the tree display area is displayed in map format.

Icons are placed at the locations set in the Monitoring Tree (Editing) window. The icons can also be moved in the details display area in map mode, but they are reset to their former locations when the Monitoring Tree window is closed.

Detailed View

Switches the details display area to list mode, in which the information of the monitoring node selected in the tree display area is displayed in list format.

Visual Icon display

Specifies by means of a check mark whether the Visual Icon can be used.

If a check mark is displayed, the Visual Icon specified for the monitoring group or the monitoring object can be displayed in the detailed display area in map mode and in a Visual Monitoring window.

Set in Equal Intervals

Temporarily aligns the icons of monitoring groups or monitoring objects displayed in map mode at equal intervals. The icons are reset to their former locations when the Monitoring Tree window is closed.

Visual Monitoring

Displays the Open Visual Monitoring Window window.

Search

Opens the Search window when a monitoring group has been selected in the Monitoring Tree window. If the Search window is already open, it is brought to the front.

When a monitoring object or virtual root node has been selected in the Monitoring Tree window, this command cannot be chosen.

Guide

Opens the Guide window for the monitoring node selected in the Monitoring Tree window only if guide information for the node exists.

Search Status-Change Events

Displays the events that caused the node status to change in the Event Console window. Events are selected based on the conditions set in the event receiver filter. If the window is already open, it is brought to the front. The event receiver filter settings can be checked in the Settings for Event Receiver Filter window.

Update Tree to Latest Status

Reads the tree configuration information from the connected JP1/IM - Manager (Central Scope), and refreshes the tree with the information. When the configuration of the nodes displayed in the Monitoring Tree window has changed, the top-level node is selected in initial status.

Properties

Opens the Properties window (with the General page displayed) for the monitoring node selected in the Monitoring Tree window.

Sort Status

Sorts the listed nodes by status. If Sorted is selected, the nodes are sorted in order by Emergency, Alert, Critical, Error, Warning, Normal, Debug, and Initial. The nodes in the same status are sorted in order of last status-update time. If Not sorted is selected, the nodes are listed in order of last status-update time.

This command can be used to sort the nodes listed in the details display area of the Monitoring Tree window and the nodes listed in the Search window.

Options

Select Block

Allows the user to select the icons of multiple monitoring groups or monitoring objects displayed in map mode at the same time. When this command is chosen, the user can draw a rectangle by dragging to enclose the icons. All the icons in the rectangle are selected.

Basic Information

Opens the Properties window (with the Basic Information page displayed) for the node selected in the Monitoring Tree window.

Status-Change Condition

Opens the Properties window (with the Status-Change Condition page displayed) for the node selected in the Monitoring Tree window.

Common Condition Settings

Opens the Common Condition Settings window, which can be used to add, delete, edit, or check the common conditions managed by JP1/IM - Manager (Central Scope).

This command is available only to users who have JP1_Console_Admin permission.

Event-Issue Conditions

Opens the Properties window (with the Event-Issue Conditions page displayed) for the node selected in the Monitoring Tree window.

Edit Tree

Opens the Monitoring Tree (Editing) window, which can be used to edit the tree without connecting to JP1/IM - Manager (Central Scope).

Logged-in User List

Opens the Login User List window, which lists the users who are currently logged in to JP1/IM - Manager (Central Scope).

Start Integrated Function Menu

Opens the Tool Launcher window.

Help

Help Contents

Displays the Help contents.

About JP1/IM - View

Displays the JP1/IM - View version information.

4.2 Open Visual Monitoring Window window

The Open Visual Monitoring Window window displays a list of the visual monitoring windows that are registered as visual monitoring data. The user can use the list to select a visual monitoring window to open. Any of the following operations displays the Open Visual Monitoring Window window:

In the Monitoring Tree window, the user chooses View from the menu bar and then Visual Monitoring.

In the Monitoring Tree window, the user clicks on the toolbar.

In the Visual Monitoring (Editing) window, the user clicks .

The following figure shows an example of the Open Visual Monitoring Window window. If this window is displayed from Visual Monitoring (Editing) window, the Display column does not appear.

Figure 4‒2: Open Visual Monitoring Window window

When the user selects the names of visual monitoring windows in the list and clicks OK, the selected visual monitoring windows open.

The Open Visual Monitoring Window window can also be displayed when visual monitoring windows have already been opened from the Monitoring Tree window. When the Open Visual Monitoring Window window opens in this case, check marks indicate the monitoring windows that are already open.

When the logged-in user's monitoring range in the tree is set and enabled, the Open Visual Monitoring Window window lists only the visual monitoring windows containing at least one node that the user can monitor.

4.3 Edit Visual Monitoring Window List window

The Edit Visual Monitoring Window List window displays a list of the visual monitoring windows registered as visual monitoring data. The user can select a visual monitoring window in the list and delete that window or change its display order. These operations can be performed only by users who have JP1_Console_Admin permission and belong to the JP1 resource group JP1_Console.

The Edit Visual Monitoring Window List window is opened from the Monitoring Tree (Editing) window when the user chooses Edit and then Edit Visual Monitoring Window List.

The following figure shows an example of the Edit Visual Monitoring Window List window.

Figure 4‒3: Edit Visual Monitoring Window List window

The following describes the items displayed in the Edit Visual Monitoring Window List window.

Up

Clicking this button moves the selected item up one line.

Down

Clicking this button moves the selected item down one line.

Delete

Clicking this button deletes the selected item.

OK

The changes made in the Edit Visual Monitoring Window List window are not applied until the OK button is clicked. When the button is clicked, the changes are saved on the server and also reflected in the Open Visual Monitoring Window window.

4.4 Visual Monitoring (Editing) window

The Visual Monitoring (Editing) window is used to create a visual monitoring window, so that the user can monitor applications visually. The user creates a visual monitoring window by dragging icons from the Monitoring Tree (Editing) window. Only users who belong to the JP1 resource group JP1_Console and have JP1_Console_Admin permission can load visual monitoring data from, and save data to, JP1/IM - Manager (Central Scope).

The Visual Monitoring (Editing) window is displayed when the user chooses Edit from the menu bar of the Monitoring Tree (Editing) window and then Create New Visual Monitoring Window.

The user can set any background image in the Visual Monitoring (Editing) window by using the Background Image Settings window. To use a user-created background image, the user needs to distribute it to all viewer hosts on which JP1/IM - View is used.

The following figure shows an example of the Visual Monitoring (Editing) window.

Figure 4‒4: Visual Monitoring (Editing) window

The following describes the items displayed in the Visual Monitoring (Editing) window.

(Select Block button)

Clicking this button allows the user to select the icons of multiple monitoring groups or monitoring objects at the same time. When this button is clicked, the user can draw a rectangle by dragging to enclose the icons. All the icons in the rectangle are selected.

(Icon Deletion button)

Clicking this button deletes the monitoring node icon selected in the monitoring point display area. The icon is deleted only from the monitoring point display area. The corresponding item in the tree display area is not deleted.

This button is enabled when a monitoring node icon has been selected.

(Background Image Settings button)

Clicking this button loads the background image that is to be set in the monitoring point display area.

A JPEG, GIF, or PNG file located in view-path\image\map\ can be loaded.

(Open Visual Monitoring Data button)

Clicking this button loads the visual monitoring data for a specific visual monitoring window from a local file.

(Save Visual Monitoring Data button)

Clicking this button saves to a local file the visual monitoring data for the visual monitoring window that is being edited.

(Acquire Visual Monitoring Data from Server button)

Clicking this button loads the visual monitoring data for a specific visual monitoring window acquired from JP1/IM - Manager (Central Scope). This button is available only to the users who belong to the JP1 resource group JP1_Console and have JP1_Console_Admin permission.

When a qualified user clicks this button, the Login window opens. After login#, the Open Visual Monitoring Window window opens.

(Update the Visual Monitoring Data of Server button)

Clicking this button saves the visual monitoring data edited in the Visual Monitoring (Editing) window to JP1/IM - Manager (Central Scope). This button is available only to the users who belong to the JP1 resource group JP1_Console and have JP1_Console_Admin permission. After clicking this button, the user must log in from the Login window#.

Monitoring point display area

A maximum of 128 monitoring node icons can be dragged into this area from the Monitoring Tree (Editing) window. The user can position an icon or the background image in this area by dragging it.

Window Name:

Displays the name of the visual monitoring window that is currently open. The user can use this text box to rename the visual monitoring window. The window name must be from 1 to 63 bytes.

Comment:

Displays a comment about the visual monitoring window that is currently open. The user can use this text box to enter a comment. The comment must not be more than 80 bytes.

#: When Save Login Information is selected from the File menu of the Monitoring Tree (Editing) window, the logged-in user's name, password, and host name are saved, and the Login window does not appear until the user logs out.

Pop-up menu

A pop-up menu is displayed when the user right-clicks in the monitoring point display area. The following describes the items on the pop-up menu.

Change Monitoring Status

Lets the user change the monitoring status of the selected monitoring node from Monitoring to Not monitoring or vise versa.

Display Order

This item can be chosen if a check mark is displayed for Visual Icon display on the View menu. Even if multiple monitoring nodes have been selected, the user can choose this item.

The following commands can be chosen to change the Display Order of a monitoring node.

Move to the foremost

The selected monitoring node is displayed in front.

Move 1 level upward

The selected monitoring node moves forward one position in the Display Order.

Move 1 level backward

The selected monitoring node moves back one position in the Display Order.

Move to the backmost

The selected monitoring node moves to the backmost position in the Display Order.

Icon Deletion

The user can choose this menu item if the icon of a monitoring node has been selected. Choosing this item deletes the selected monitoring node icon in the same way as clicking .

Search

The user can choose this item if the icon of a monitoring group has been selected. Choosing this menu opens the Search window. If the Search window is already open, it is brought to the front. This item cannot be chosen if the icon of a monitoring object has been selected.

Properties

The user can choose this menu item if the icon of a monitoring node has been selected. Choosing this item opens the Properties window (with the General page displayed) for the selected monitoring node.

Background Image Settings

Choosing this item loads the background image to be set in the monitoring point display area. This item has the same effect as the button. This item appears on the pop-up menu when no icon has been selected.

4.5 Visual Monitoring window

Visual Monitoring windows are used to monitor the applications (monitoring nodes) represented by icons pasted into the windows from the Visual Monitoring (Editing) window. The Visual Monitoring window can also be used to change the status of nodes, display guide information, and retrieve nodes whenever necessary.

The user can display the applicable Visual Monitoring windows by selecting their names in the Open Visual Monitoring Window window and then clicking the OK button.

When the logged-in user's monitoring range is set and enabled, only the icons of those nodes that the user can access are displayed. If the user is monitoring nodes in a visual monitoring window and that window is edited so that all the nodes that the user can access are deleted, a message dialog box appears and the Visual Monitoring window closes.

Important

By maximizing the Visual Monitoring window, the entire background image is displayed without scrolling the window. If the size of the Visual Monitoring window is larger than the screen resolution, scroll bars might appear to adjust the window to fit the screen resolution. In addition, the Close button and the Help button might be hidden.

Figure 4‒5: Visual Monitoring window

The following describes the items displayed in each Visual Monitoring window.

Alarm indicator

Flashes if a failure occurs in the monitored application system. The following table describes the conditions that cause the alarm indicator to flash under the default settings.

Table 4‒5: Conditions that cause the alarm indicator to flash

Setting and status of a node in the Visual Monitoring window

Alarm indicator

Whether monitoring enabled

Status

Enabled (Monitoring)

Warning, Normal, Debug, or Initial

Not lit

Enabled (Monitoring)

Emergency, Alert, Critical, or Error

Flashing

Disabled (Not monitoring)

Initial#

Not lit

#: The status of node set to Not monitoring is always Initial.

You can change the conditions that cause the alarm indicator to flash. For details, see System profile of Central Scope (jcs_sysprofile_xxx.def) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Monitoring point display area

Displays the icons of monitoring nodes.

If a failure occurs on a monitoring node represented by an icon, the background color of the icon changes. When the user double-clicks the icon, the associated monitoring node is selected in the Monitoring Tree window.

If icons overlap in this area, the icon of a node with a higher node ID is displayed in front of the icon of a node with a lower node ID. If a check mark is displayed for Visual Icon display on the View menu, the icons are displayed in the order specified in the Visual Monitoring (Editing) window.

(Select Block button)

Clicking this button allows the user to select the icons of multiple monitoring groups or monitoring objects displayed in the monitoring point display area at the same time. When this button is clicked, the user can draw a rectangle by dragging to enclose the icons. All the icons in the rectangle are selected.

Pop-up menu

In the monitoring point display area, the user can select and right-click an icon to display a pop-up menu. The following describes the items on the pop-up menu.

Change Status

Lets the user change the status of the selected monitoring node. A check mark indicates the current status, which the user can change by choosing another status.

Change Monitoring Status

Lets the user change the monitoring status of the selected monitoring node from Monitoring to Not monitoring and vice versa.

Display Order

This item can be chosen if a check mark is displayed for Visual Icon display on the View menu. Even if multiple monitoring nodes have been selected, the user can choose this item.

The use can temporarily change the Display Order of a monitoring node by choosing the following commands. If the user closes the window and then displays it again, the Display Order is reset to the order specified in the Visual Monitoring (Editing) window.

Move to the foremost

The selected monitoring node is displayed in front.

Move 1 level upward

The selected monitoring node moves forward one position in the Display Order.

Move 1 level backward

The selected monitoring node moves backward one position in the Display Order.

Move to the backmost

The selected monitoring node moves to the backmost position in the Display Order.

Search

The user can choose this item if the selected node is a monitoring group. Choosing this item opens the Search window. If the window is already open, it is brought to the front. The user cannot choose this item when the selected node is a monitoring object.

Guide

Opens the Guide window for the selected monitoring node only if guide information for the node exists.

Search Status-Change Events

Displays the events that caused the node status to change in the Event Console window. Events are selected based on the conditions set in the event receiver filter. If the window is already open, it is brought to the front. The event receiver filter settings can be checked in the Settings for Event Receiver Filter window.

Properties

Opens the Properties window (with the General page displayed) for the selected monitoring node.

4.6 Background Image Settings window

The Background Image Settings window is used to set the background image of a Visual Monitoring window or the background image of the details display area in map mode (Icon View) in the Monitoring Tree window. The following explains how to open the Background Image Settings window.

To set the background image of a Visual Monitoring window:

In the Visual Monitoring (Editing) window, the user clicks .

To set the background image of the details display area in map mode (Icon View) in the Monitoring Tree window:

The user opens the Properties window, and on the General page, clicks the Change button on the right of the Background image setting area.

Note that the user can perform this operation only for a monitoring group in the Monitoring Tree (Editing) window.

The following figure shows an example of the Background Image Settings window.

Figure 4‒6: Background Image Settings window

The following describes the storage location, formats, and maximum size of the images that can be selected as background images.

Location of the images:

view-path\image\map\

The maximum length of the file name is 260 bytes, which includes the path to the file storage location and the file name with its extension.

Image formats:

JPEG

GIF

PNG

Maximum image size:

2,048 x 2,048 pixels

The Background Image Settings window has two areas: File list and Preview. If an image file is selected in the File list area, the image and size are displayed in the Preview area. If No background image is selected in the File list area, icons are displayed on a solid white background in the Visual Monitoring window or in the details display area of the Monitoring Tree window in map mode.

The following images cannot be used for background images:

An image whose height or width is greater than 2,048 pixels

An image whose file format is not JPEG, GIF, or PNG

4.7 Search window

The Search window is used to retrieve the monitoring nodes that satisfy the specified search conditions. Either of the following operations displays this window:

In the Monitoring Tree window, the user chooses View from the menu bar and then Search.

In the Monitoring Tree (Editing) window, the user chooses Edit on the menu bar and then Search.

The following nine search conditions can be set. The conditions that are set are combined with the AND operator.

Monitoring node name

Monitoring node ID

Monitoring node type

Status

JP1 resource group

Monitoring status

Basic Information

Status-Change Condition

Event-Issue Conditions

The following figure shows an example of the Search window.

Figure 4‒7: Search window

The following describes the items displayed in the Search window.

Search start location

Displays the monitoring node on which the search is to be started.

Monitoring node name

Specifies a regular expression that is used to perform a search based on the monitoring node name. The user can specify a maximum of 1,280 bytes for the regular expression.

For details about regular expressions, see Appendix G. Regular Expressions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Monitoring node ID

Specifies as hexadecimal values the IDs of the monitoring nodes to be retrieved. The user can specify a maximum of 1,023 bytes for the monitoring node IDs. A maximum of 113 monitoring node IDs, separated by a comma (,), can be specified.

Monitoring node type

Specifies the type of the monitoring nodes to be retrieved. Either the Monitoring object or the Monitoring group radio button can be selected. If the Monitoring object radio button is selected, a drop-down list can be used to select a general monitoring object (user monitoring object) or system-monitoring object (such as AJS2 Monitoring Object or SSO Monitoring object). If blank space is selected, all types of monitoring objects are specified.

Status

Specifies the statuses of the monitoring nodes to be retrieved. The user can select Emergency, Alert, Critical, Error, Warning, Normal, Debug, and Initial.

JP1 resource group

Specifies the name of the JP1 resource group for which the search is to be performed. The user can specify a maximum of 1,280 bytes for the character string.

A regular expression can also be specified. For details about regular expressions, see Appendix G. Regular Expressions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

This item is displayed when the logged-in user's monitoring range in the tree display area is set and enabled.

Monitoring status

Lets the user select Monitoring or Not monitoring as the monitoring status of the selected monitoring node.

Basic Information

Specifies the basic information of the monitoring nodes to be retrieved. A maximum of five items can be entered. When multiple items are specified, they are combined with the AND operator.

An item of basic information consists of two elements, a monitoring node attribute name and a monitoring node attribute value. Each element can have a maximum of 1,023 bytes. However, the total number of bytes that can be used to specify monitoring node attribute values is 1,280. Regular expressions can also be used to specify basic information.

To edit an item displayed in the list box, the user selects the item and then clicks Edit. The Edit Basic Information window opens, where the user can edit basic information. To delete an item of basic information from the list box, the user selects the item and then clicks the Delete button.

Figure 4‒8: Edit Basic Information window

Status-Change Condition

Specifies the status-change conditions for the monitoring nodes to be retrieved. The Condition Name text box is used to enter a regular expression of 1,023 or fewer bytes. If this text box is blank, all monitoring nodes are retrieved.

Event-Issue Conditions

Specifies the event-issue conditions for the monitoring nodes to be retrieved. The user can select Emergency, Alert, Critical, Error, Warning, Normal, and Debug.

Search results list

When the Search button is clicked, the monitoring nodes that satisfy the specified search conditions are displayed in the list. The list can be sorted by status by choosing View from the menu bar of the Monitoring Tree window, Sort Status, and then Sorted. When Sorted is selected, the list is sorted by status (Emergency, Alert, Critical, Error, Warning, Normal, and Debug, and Initial, in this order).

Pop-up menu

A pop-up menu is available in the Search window opened from the Monitoring Tree window or Monitoring Tree (Editing) window. The pop-up menu is displayed when the user selects and right-clicks a monitoring node in the search results list. The following describes the items on the pop-up menu.

Change Status

This item appears on the pop-up menu when the Search window is opened from the Monitoring Tree window, and is used to change the status of the application associated with the selected monitoring node. One of the following statuses is marked with a check mark to indicate the current status, which the user can change by choosing another status:

Emergency

Alert

Critical

Error

Warning

Normal

Debug

Initial

Change Monitoring Status

Changes the monitoring status of the selected monitoring node. Either of the following statuses is marked with a check mark to indicate the current status, which the user can change by choosing the other status:

Monitoring

Not monitoring

4.8 Guide window

The Guide window displays the guide information appropriate for the status of a monitoring node. JP1/IM - View reads the guide information file for the selected monitoring node from JP1/IM - Manager, and displays the contents of the file in the Guide window. The Guide window is displayed when the user chooses View from the menu bar of the Monitoring Tree window and then Guide.

The following figure shows an example of the Guide window.

Figure 4‒9: Guide window

The information to be displayed in the Guide window must be provided in the appropriate guide information files. For details, see Guide information file (jcs_guide.txt) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

4.9 Properties window

The Properties window is used to display or change the attributes of a monitoring node selected in the Monitoring Tree window. Note that the Properties window cannot be used to change any status.

The Properties window has four pages: General, Basic Information, Status-Change Condition, and Event-Issue Conditions. Each page is displayed by clicking the corresponding tab.

This section explains the items displayed in the Properties window. The window can also be used to change these items, although the procedures for doing so are not described.

To use the Monitoring Tree window to change attributes, the user must have JP1_Console_Admin permission or JP1_Console_Operator permission. No user permissions are required when the Monitoring Tree (Editing) window is used to change attributes.

4.9.1 General page

The General page of the Properties window can be used to display or change the name and icon of a monitoring node, the monitoring status of the node, and the JP1 resource group of the node.

The following figure shows an example of the General page in the Properties window.

Figure 4‒10: Properties window (General page)

The following describes the items displayed on the General page of the Properties window.

Icon and name of a monitoring node

Displays the icon and name of the selected monitoring node. When the node is a monitoring group, the icon that is displayed when the node is collapsed is also displayed.

Monitoring node ID:

Displays the node ID of the selected monitoring node.

Location:

Displays the location of the selected monitoring node in the tree. Each hierarchical level from the top of the tree is indicated by a slash (/). When the selected node is a monitoring group, a slash (/) is suffixed to the location.

Monitoring node type:

Displays the type of the selected monitoring node.

Icon (normal):

Displays the file name of the icon of the selected monitoring node. The user can change the icon by clicking Change to display the Select Icon window, where the user can select an icon.

Icon (expanded):

This item, which is applicable to only a monitoring group, displays the file name of the icon that is displayed when the node is expanded in the tree. The user can change the icon by clicking Change to display the Select Icon window, where the user can select an icon.

Visual Icon

Displays the file name of the Visual Icon for the selected monitoring node. Clicking the Change button opens the Visual Icon Selection window, where the user can change the Visual Icon.

If a Visual Icon is not set for a monitoring node, no file name is displayed.

Background image setting:

Displays the file name of the background image of the details display area in map mode (Icon View) in the Monitoring Tree window. The user can change the background image by clicking Change to display the Background Image Settings window, where the user can set a background image. Note that the user can change the background image only for a monitoring group in the Monitoring Tree (Editing) window.

Status-update date/time:

Displays the date and time that the selected monitoring node was updated.

Status:

Displays the status of the selected monitoring node. For example, Normal or Error is displayed. The monitoring status of the selected monitoring node is also displayed. The user can select either Monitoring or Not monitoring to change the monitoring status.

JP1 resource group:

Displays the name of the JP1 resource group set for the selected monitoring group when the logged-in user's monitoring range is set and enabled. If the Properties window is opened from the Monitoring Tree window, this item is disabled and the JP1 resource group cannot be changed. The JP1 resource group can be changed only by opening the Properties window from the Monitoring Tree (Editing) window. A JP1 resource group must be set for the top-level monitoring node. The default JP1 resource group for the top-level monitoring node is JP1_Console.

The following are notes on changing the JP1 resource group:

The name of the top-level JP1 resource group can have from 1 to 64 bytes, and the names of other JP1 resource groups can have from 0 to 64 bytes.

Only printable ASCII characters can be used in JP1 resource group names. However, the following characters cannot be specified: tab character, space character, control characters, and the symbols " / [ ] ; : = , + ? < >

Clicking OK or Apply applies the changes made on the General page:

4.9.2 Basic Information page

The Basic Information page is used to display or set basic information for the selected monitoring node.

The following figure shows an example of the Basic Information page of the Properties window.

Figure 4‒11: Properties window (Basic Information page)

The following describes the items displayed in the Basic Information page of the Properties window.

Monitoring Node Attribute Name and Monitoring Node Attribute Value

When the Add button is clicked, the values entered in these text boxes are registered as one entry in the list box (basic information display field). The following are notes on registering basic information entries:

A maximum of five basic information entries can be registered.

Each monitoring node attribute name must be unique. The attribute name of a monitoring node that has already been registered cannot be used.

The length of each monitoring node attribute name must be from 1 to 32 bytes.

The length of each monitoring node attribute value must be from 1 to 1,023 bytes.

The total length of monitoring node attribute values must not exceed 1,280 bytes.

Basic information display field

This area displays basic information about the selected monitoring node.

The user can edit or delete an entry listed in the basic information display field. The user edits an entry by selecting it in the basic information display field and then clicking the Edit button to display the Edit Basic Information window, where the values of the entry can be edited. The user deletes an entry by selecting it in the basic information display field and then clicking the Delete button.

Figure 4‒12: Edit Basic Information window

4.9.3 Status-Change Condition page

The Status-Change Condition page is used to display or set the event conditions for changing the status of the selected monitoring node.

The following figure shows an example of the Status-Change Condition page of the Properties window.

Figure 4‒13: Properties window (Status-Change Condition page)

The following describes the items displayed on the Status-Change Condition page of the Properties window.

Status-change condition display field

This area lists the conditions for changing the application status of the monitoring node. Each condition in the field consists of a condition name and a status.

The user can edit a condition listed in the status-change condition display field by selecting it, and then clicking Edit to display the Status-Change Condition Settings window. This window displays the settings of the selected condition.

For example, if the user selects an event monitoring condition that has been set for a monitoring object, the Status-Change Condition Settings window displays the conditions for the selected monitoring events.

To add a condition, the user clicks Add. The Status-Change Condition Settings window opens, and the user can set a new condition for changing the status of the monitoring node. The new condition is added at the bottom of the status-change condition display field.

A maximum of eight status-change conditions can be set for one monitoring object or monitoring group.

To delete a condition, the user selects a condition in the status-change condition display field, and then clicks Delete.

4.9.4 Event-Issue Conditions page

A JP1 event can be issued when the status of the selected monitoring node changes. The Event-Issue Conditions page can be used to set the conditions for issuing JP1 events.

When a condition set on this page exists, JP1/IM - Manager sends a status-change event. If an automated action is to be set, the event must be specified in JP1/IM - View.

The following figure shows an example of the Event-Issue Conditions page of the Properties window.

Figure 4‒14: Properties window (Event-Issue Conditions page)

The following describes the items displayed on the Event-Issue Conditions page of the Properties window.

Event-issue conditions display field

This area specifies the monitoring node statuses that trigger the issuing of a JP1 event. The user selects the statuses from Emergency, Alert, Critical, Error, Warning, Normal, and Debug by selecting the corresponding check boxes. When the status of the monitoring node changes to any of the selected statuses, a JP1 event is issued.

4.10 Select Icon window

The Select Icon window is used to select icons for the monitoring nodes displayed in the Monitoring Tree window and Visual Monitoring windows. The Select Icon window is displayed when the user clicks the Change button on the General page of the Properties window.

The following figure shows an example of the Select Icon window.

Figure 4‒15: Select Icon window

When the user selects an icon displayed in the Select Icon window and clicks the OK button, the icon of the specified monitoring node changes to the selected icon. User-created icons can also be used by storing them in the specific folder JP1/IM - View shown below. The Select Icon window displays the icons available in the folder. If JP1/IM - View is installed on multiple hosts, the user-created icons must be distributed to each viewer. The following describes the location, formats, and size of the icons displayed in the Select Icon window:

Location of the icon folder:

view-path\image\icon\

The maximum length of the file name is 260 bytes, which include the path to the file storage location and the file name with its extension.

Formats of icon files that can be selected:

JPEG

GIF#

PNG

#: Animation GIF files cannot be used.

Size of icon images that can be selected:

16 x 16 pixels

When status-change conditions are set for a monitoring group, a monitoring group symbol is added to the icon of the monitoring group (example: , , , , and ).

4.11 Visual Icon Selection window

The Visual Icon Selection window is used to select the Visual Icons for monitoring nodes used in the Monitoring Tree window (when Icon View is selected for the Details display area) and the Visual Monitoring windows. The Visual Icon Selection window is displayed when the user clicks the Change button for Visual Icons on the General page of the Properties window.

The following figure shows an example of the Visual Icon Selection window.

Figure 4‒16: Visual Icon Selection window

When the user selects a Visual Icon displayed in the Visual Icon Selection window and clicks the OK button, the Visual Icon of the specified monitoring node changes to the selected Visual Icon. To list Visual Icons in the Visual Icon Selection window, the user must create the JP1/IM - View folder indicated below and store the files ahead of time. If JP1/IM - View is installed on multiple hosts, the Visual Icons must be distributed to each viewer.

The following describes the location, formats, and size of the images to be used as Visual Icons displayed in the Visual Icon Selection window:

Location of the Visual Icon folder:

view-path\image\visual\

The maximum length of the file name is 260 bytes, which includes the path to the file storage location and the file name with its extension.

Formats of icon files:

JPEG

GIF#

PNG

#: Animation GIF files cannot be used.

Size of icon images:

Minimum size: 24 x 24 pixels

Maximum size: 2,048 x 2,048 pixels

When a file name is selected in the file list, the image and the size are displayed in the Preview window. If a Visual Icon has not been set for the monitoring node, choose No Visual Icon in the file list.

4.12 Status-Change Condition Settings window

The Status-Change Condition Settings window is used to set status-change conditions for the monitoring node selected in the Monitoring Tree window or the Monitoring Tree (Editing) window. The Status-Change Condition Settings window is displayed when the user clicks Add or Edit on the Status-Change Condition page of the Properties window.

4.12.1 Status-Change Condition Settings window for a monitoring object

The following figure shows an example of the Status-Change Condition Settings window opened when a monitoring object is selected.

Figure 4‒17: Status-Change Condition Settings window for a monitoring object

For details about the status-change condition settings available in this window, see Chapter 8. Lists of System-Monitoring Objects (for Central Scope) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Note that the setting in Common condition and the setting in Individual conditions are combined by using the AND operator. The individual conditions in Individual conditions are also combined by using the AND operator.

The following describes the items displayed in the Status-Change Condition Settings window for a monitoring object.

Condition name

The user enters the name of an event condition for changing the status of the monitoring object. The maximum length is 63 bytes.

Status

The user selects the status of the monitoring object from Emergency, Alert, Critical, Error, Warning, Normal, Debug, or Initial in the drop-down list.

Condition (under Common condition)

From the drop-down list, the user selects one of the common conditions set in the Common Condition Settings window. When the Set Common Condition button is clicked, the Common Condition Settings window opens, where the user can add or edit a common condition.

Condition (under Individual conditions)

This area is used to register individual conditions. The user specifies the name and value of an individual attribute, and a condition.

The name of an individual attribute must begin with B. if the attribute is a JP1 event basic attribute, and must begin with E. if the attribute is a JP1 event extended attribute.

The following are notes on registering individual conditions:

A maximum of five individual conditions can be registered.

The length of each individual attribute name must be from 1 to 32 bytes.

Each individual attribute name must begin with an upper-case alphabetic character and can consist of upper-case alphabetic characters, numeric characters, and underscores (_). If a lower-case alphabetic character is entered, it is automatically converted to the corresponding upper-case alphabetic character.

The length of one individual attribute value must be from 1 to 1,023 bytes.

The total length of individual attribute values must not exceed 1,280 bytes.

Duplicate individual attribute names can be specified, but the Match comparison condition can be specified for only one of them.

When the same individual attribute name and value are specified in multiple conditions, either the Match or the Does not match comparison condition, but not both, can be specified in the conditions.

After specifying character strings in the text boxes, the user uses the drop-down list on the right to select Match, Does not match, First characters, Is contained, Is not contained, Regular expression, or Host name comparison as the comparison condition. If a condition other than Host name comparison is selected, the specified character string is case sensitive. If Host name comparison is selected, the host information saved in JP1/IM - Manager is used for the comparison. For details about the difference between Match and Host name comparison, see 5.11.2 Host information in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When the Add button is clicked, the specified values are added as one entry to the list box (individual condition display field).

The user can edit or delete an entry listed in the individual condition display field. The user edits an entry by selecting it in the field and then clicking the Edit button to display the Edit Individual Condition window, where the selected entry can be edited. The user deletes an entry by selecting it in the individual condition display field and then clicking the Delete button.

Figure 4‒18: Edit Individual Condition window

Common information and program-specific information of a JP1 event extended attribute can be specified for an individual attribute. For details, see Chapter 3. JP1 Events in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

4.12.2 Status-Change Condition Settings window for a monitoring group

The following figure shows an example of the Status-Change Condition Settings window opened when a monitoring group is selected.

Figure 4‒19: Status-Change Condition Settings window for a monitoring group

The following describes the items displayed in the Status-Change Condition Settings window for a monitoring group.

Condition name

The user enters the name of an event condition for changing the application status of the monitoring group. The maximum length is 63 bytes. Note that duplicate condition names cannot be specified for one monitoring group.

Status

The user selects the status in which the monitoring group is to be placed when the specified condition is met. Emergency, Alert, Critical, Error, Warning, Normal, or Debug can be selected from the drop-down list.

Child node status

The user selects the application status of a child node that causes the status of the monitoring group to change. Emergency, Alert, Critical, Error, Warning, Normal, or Debug can be selected from the drop-down list.

Comparison condition

Specifies either the percentage or the number of child nodes placed in the selected status as the threshold that triggers changing of the monitoring group status.

Percentage (n % or higher)

You can specify a value in the range from 1 to 100 (%). If you enter 100, the status of the monitoring group changes when all the child nodes are in the selected status.

Number (n items or more)

You can specify a value in the range from 1 to 50,000. If you enter 50,001 or a larger value, an error occurs when you click the OK button.

4.13 Common Condition Settings window

The Common Condition Settings window is used to add, delete, edit, or check the status-change conditions (common conditions) of a monitoring object.

This window is displayed when the user chooses Options from the menu bar of the Monitoring Tree window and then Common Condition Settings or when the user clicks the Set Common Condition button in the Status-Change Condition Settings window.

The following figure shows an example of the Common Condition Settings window.

Figure 4‒20: Common Condition Settings window

The following describes the items displayed in the Common Condition Settings window.

Common Condition Settings

This area lists the common conditions for changing the application status of the monitoring object.

If the Common Condition Settings window is opened from the Monitoring Tree window during monitoring of system operation, the Common Condition Settings window displays the common conditions saved in JP1/IM - Manager.

For example, the common conditions saved in JP1/IM - Manager are displayed when the user chooses Options from the menu bar of the Monitoring Tree window and then Common Condition Settings.

If the Common Condition Settings window is opened from the Monitoring Tree (Editing) window, the displayed common conditions change, depending on the condition, as described below:

When a new monitoring tree is being created, the default common conditions saved in JP1/IM - View are displayed.

When a CSV file saved on the local computer is loaded, the common conditions saved in the file are displayed.

After Acquire Tree from Server, Auto-generate Tree, or Acquire Latest Definition has been executed, the common conditions saved in JP1/IM - Manager are displayed.

Example 1: The user opens Monitoring Tree (Editing) window, and immediately chooses Options from the menu bar and then Common Condition Settings. In this case, the common conditions saved in JP1/IM - View are displayed. (Condition 1 above)

Example 2: The user chooses File from the menu bar of the Monitoring Tree (Editing) window, and then Open Tree to open a local CSV file. The user then opens the Common Condition Settings window. In this case, the common conditions saved in the file are displayed. (Condition 2 above)

Example 3: The user chooses Acquire Latest Definition from the Options menu in the menu bar of the Monitoring Tree (Editing) window to acquire the latest definition from JP1/IM - Manager. The user then opens the Common Condition Settings window. In this case, the common conditions saved in JP1/IM - Manager are displayed. (Condition 3 above)

Add

Clicking this button displays the Common Condition Detailed Settings window, where a common condition can be added.

This button cannot be used when 191 editable common conditions have already been registered.

Browse or Edit

If the selected common condition is a system definition, Browse is displayed. If the selected common condition is a user definition, Edit is displayed.

Clicking the Edit button displays the Common Condition Detailed Settings window, where the detailed settings of the selected common condition can be edited. If Browse is displayed, the selected common condition cannot be edited.

Delete

Clicking this button deletes the selected common condition.

4.14 Common Condition Detailed Settings window

The Common Condition Detailed Settings window is used to specify the detailed settings of a common condition. This window is displayed when the user clicks Add, Edit, or Browse in the Common Condition Settings window.

The following figure shows the Common Condition Detailed Settings window.

Figure 4‒21: Common Condition Detailed Settings window

The following describes the items displayed in the Common Condition Detailed Settings window.

Common condition name

Displays the name of the selected common condition for changing the application status of the monitoring object. The name can be changed.

A character string having from 1 to 63 bytes can be specified.

Registration host

Specifies the name of a host that issues JP1 events.

Multiple character strings require a comma (,) as a separator. A maximum of 100 character strings can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

From the drop-down list on the right, the user selects a condition for the specified character strings from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression. If Regular expression is selected, only one condition can be set.

Severity

Specifies the severity levels of the JP1 events to be specified from Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

Object type

Specifies the object type of a JP1 event. The character string can be typed in the text box or selected from the drop-down list.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

Object name

Specifies the object name of a JP1 event.

Multiple character strings require a comma as a separator. A maximum of 100 character strings can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

From the drop-down list on the right, the user selects a condition for the specified characters string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

If Regular expression is selected, only one condition can be set.

Registration name type

Specifies the registration name type (root object type) of a JP1 event. The value can be typed in the text box or selected from the drop-down list.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

Registration name

Specifies the registration name (root object name) of a JP1 event.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

Event type

Specifies the event type (occurrence type) of a JP1 event.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

User name

Specifies the user name of a JP1 event. A character string having from 0 to 1,023 bytes can be specified.

Multiple character strings require a comma as a separator. A maximum of 100 character strings can be specified. If a character string that includes a comma (,) or backslash (\) is specified, a backslash (\) must be added before the comma (\,) or backslash (\\). A linefeed or tab character cannot be specified.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

If Regular expression is selected, only one condition can be set.

Message

Specifies the message text of a JP1 event.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

Product name

Specifies the name of a program that issues JP1 events.

From the drop-down list on the right, the user selects a condition for the specified character string from Match, Does not match, First characters, Is contained, Is not contained, and Regular expression.

Event ID

Specifies the ID of a JP1 event as a hexadecimal number. You can specify a value in the range from 0 to 7FFFFFFF.

Multiple IDs require a comma (,) as a separator.

A maximum of 113 event IDs can be specified.

Extended attribute

This area is used to register extended attributes (names and values in pairs) for the common condition items other than Severity. The following are notes on registering extended attributes:

A maximum of five extended attributes can be registered.

Each extended attribute name must be unique. An extended attribute name that has already been registered cannot be used.

The length of each extended attribute name must be from 1 to 32 bytes.

Each extended attribute name must begin with an upper-case alphabetic character and can consist of upper-case alphabetic characters, numeric characters, and underscores (_). If a lower-case alphabetic character is entered, it is automatically converted to the corresponding upper-case alphabetic character.

The length of one extended attribute value must be from 1 to 1,023 bytes.

The total length of extended attribute values must not exceed 1,280 bytes.

Each extended attribute value must be specified as a regular expression. For details about regular expressions, see Appendix G. Regular Expressions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When the Add button is clicked, the specified values are added as one entry to the list box (extended attribute display field).

The user can edit or delete an entry listed in the extended attribute display field. The user edits an entry by selecting it in the field and then clicking the Edit button to display the Edit Extended Attributes window, where the selected entry can be edited. The user deletes an entry by selecting it in the extended attribute display field and then clicking the Delete button.

The following figure shows an example of the Edit Extended Attributes window.

Figure 4‒22: Edit Extended Attributes window

4.15 Monitoring Tree (Editing) window

The Monitoring Tree (Editing) window is used to set the monitoring nodes that are to be monitored in the Monitoring Tree window. When the settings specified in the Monitoring Tree (Editing) window have been saved in the monitoring object database, the settings are applied to all the JP1/IM - View programs connected to JP1/IM - Manager. The Monitoring Tree (Editing) window is displayed when the user chooses Options from the menu bar of the Monitoring Tree window and then Edit Tree.

The following figure shows an example of the Monitoring Tree (Editing) window.

Figure 4‒23: Monitoring Tree (Editing) window

The following describes the items displayed in the Monitoring Tree (Editing) window.

Tree display area

Displays the elements that make up the application system that is monitored in a tree structure. For details about the items displayed in the tree display area, see the explanation in 4.1 Overview of the Monitoring Tree window. Note that no virtual root node is displayed in the Monitoring Tree (Editing) window.

Details display area

Displays the child nodes of a monitoring group selected in the tree display area or displays the details (node name and type) of a monitoring object selected in the tree display area. For details about the items displayed in the tree display area, see the explanation in 4.1 Overview of the Monitoring Tree window. The details display area is displayed in map mode when is clicked and in the detailed view mode when is clicked.

(Move to Upper Monitoring Group button)

Clicking this button selects the parent node of a node selected in the tree display area. The focus moves to the parent node in the tree display area, and the details of the parent node are displayed in the details display area.

(Icon View button)

Clicking this button switches the details display area to map mode, in which the information of the monitoring group or monitoring object selected in the tree display area is displayed in map format. Every time the user moves an icon, the new location of the icon is immediately saved. The locations of the icons placed in the Monitoring Tree (Editing) window are reflected in the Monitoring Tree window displayed in map mode.

(Detailed View button)

Clicking this button switches the details display area to list mode, in which the information of the monitoring group or monitoring object selected in the tree display area is displayed in list format.

(Select Block button)

Clicking this button selects the icons of multiple monitoring groups or monitoring objects displayed in map mode at the same time. When this button is clicked, the user can draw a rectangle by dragging to enclose the icons. All the icons in the rectangle are selected. This button is disabled in list mode.

(Set in Equal Intervals button)

Clicking this button resets the locations of the icons of monitoring groups or monitoring objects and aligns the icons at equal intervals. The locations of the icons placed in the Monitoring Tree (Editing) window are reflected in the Monitoring Tree window displayed in map mode. This button is disabled in list mode.

Pop-up menu

The pop-up menu is displayed when the user right-clicks in the tree display area or details display area.

The following items appear on the pop-up menu only if specific conditions are met.

Background Image Settings

This item can be chosen if no icons have been selected in the Details display area in map mode and if the user right-clicks an area where there is no icon.

The background image in map mode is loaded.

Display Order

This item can be chosen if a check mark is displayed for Visual Icon display on the View menu. Even if multiple monitoring nodes have been selected, the user can choose this item.

The user can change the Display Order of the monitoring nodes by choosing the following commands:

Move to the foremost

The selected monitoring node is displayed in front.

Move 1 level upward

The selected monitoring node moves forward one position in the Display Order.

Move 1 level backward

The selected monitoring node moves back one position in the Display Order.

Move to the backmost

The selected monitoring node moves to the backmost position in the Display Order.

For details about other items appearing on the pop-up menu, see the explanations below of the corresponding menu items available from the menu bar.

The following table describes the items available from the menu bar of the Monitoring Tree (Editing) window.

Table 4‒6: Menu items available from the menu bar of the Monitoring Tree (Editing) window

Menu

Command

Description

File

New

Creates a new tree. The user can add nodes to the new tree by choosing Edit and then Create New Monitoring Node. A sequence number starting at 00000001 is assigned as a monitoring node ID to each node.

Open Tree

Loads a tree configuration file stored on the local computer. The version of the loaded tree configuration file is displayed in the title bar.

Save Tree

Saves the tree configuration information in a CSV tree configuration file on the local computer.

Acquire Tree from Server

Acquires tree configuration information from JP1/IM - Manager.

When the user chooses this command, the Login window opens. When the user logs in#, the monitoring tree of JP1/IM - Manager is acquired. The version of the monitoring object database in the JP1/IM - Manager from which the monitoring tree is acquired is displayed in the title bar.

This command is available only to users who belong to the JP1 resource group JP1_Console and have JP1_Console_Admin permission.

Update Server Tree

Saves the tree configuration information edited by using the Monitoring Tree (Editing) window in the monitoring object database of JP1/IM - Manager.

When the user chooses this command, the Login window opens. When the user logs in#, the tree configuration information of the tree currently displayed in the Monitoring Tree (Editing) window is applied to the monitoring tree of JP1/IM - Manager.

This command is available only to users who belong to the JP1 resource group JP1_Console and have JP1_Console_Admin permission.

Save Login Information

If a check mark is displayed beside this command, the user's login information used for the first login has been saved. As a result, when the user connects to the server again, the Login window does not appear.

Exit

Closes the Monitoring Tree (Editing) window.

Edit

Change Monitoring Status

Lets the user select the monitoring status of a monitoring node selected in the Monitoring Tree (Editing) window.

A check mark indicates the current status, which the user can change by choosing the other status.

Cut

Cuts the selected monitoring node. When a root monitoring node is selected, the user cannot choose this command.

Copy

Copies the selected monitoring node. When a root monitoring node is selected, the user cannot choose this command.

Paste

Pastes the cut or copied monitoring node into the selected monitoring group as a child node of the monitoring group.

Create New Monitoring Node

Opens the Create New Monitoring Node window so that a child node can be added to the selected monitoring group.

When new monitoring nodes are created in map mode, they are placed in the details display area automatically, starting at the top left of the area, until their locations become fixed.

Delete

Deletes the selected monitoring node.

If monitoring nodes whose locations have not been fixed yet are deleted in map mode, the rest of the monitoring node icons whose locations have not become fixed yet are re-aligned, starting at the top left of the details display area.

Delete All

Deletes all monitoring nodes displayed in the Monitoring Tree (Editing) window. This command is typically used while the user is editing a tree loaded from a CSV tree configuration file so that the user can re-edit the tree from scratch. Choosing this command clears the tree, but does not clear the contents of the CSV tree configuration file.

Undo

Cancels the last editing operation related to the parent-child relationship performed for a monitoring node in the Monitoring Tree (Editing) window.

Redo

Cancels the undo operation that was performed immediately before Redo was chosen.

Search

Opens the Search window so that the user can search the tree in the Monitoring Tree (Editing) window for monitoring nodes. When a monitoring group is selected in the tree, JP1/IM - View searches only the selected monitoring group, including the child nodes.

If the Search window is already open, it is brought to the front.

Create New Visual Monitoring Window

Opens the Visual Monitoring (Editing) window.

Edit Visual Monitoring Window List

Opens the Edit Visual Monitoring Window List window.

Before this window opens, the Login window opens, from which the user must log in.#

This command is available only to users who belong to the resource group JP1_Console and have JP1_Console_Admin permission.

Properties

Opens the Properties window (with the General page displayed) for the monitoring node selected in the Monitoring Tree (Editing) window.

Options

Icon View

Switches the details display area to map mode, in which the information of the monitoring group or monitoring object selected in the tree display area of the Monitoring Tree (Editing) window is displayed in map format.

Every time the user moves an icon, the new location is immediately saved. The locations of the icons set in this window are reflected in the Monitoring Tree window displayed in map mode.

Detailed View

Switches the details display area to list mode, in which the information of the monitoring node selected in the tree display area of the Monitoring Tree (Editing) window is displayed in list format.

Visual Icon display

Specifies by means of a check mark whether the Visual Icon can be used.

If a check mark is displayed, the Visual Icon specified for the monitoring group or the monitoring object is displayed in the detailed display area in map mode and in a Visual Monitoring window.

Set in Equal Intervals

Aligns the icons of monitoring groups or monitoring objects displayed in map mode at equal intervals. The locations of the icons set in the Monitoring Tree (Editing) window are reflected in the Monitoring Tree window displayed in map mode. This command cannot be chosen in list mode (Detailed View).

Select Block

Allows the user to select the icons of multiple monitoring groups or monitoring objects displayed in map mode at the same time. When this command is chosen, the user can draw a rectangle by dragging to enclose the icons. All the icons in the rectangle are selected.

Auto-generate Tree

Opens the Auto-generation - Select Configuration window for automatically generating a monitoring tree.

Before this window opens, the Login window opens, from which the user must log in.# To use this command to generate a monitoring tree automatically, the user must log in as the jp1admin user.

Note:

If the jp1admin user has been deleted for whatever administrative reason, log in as a JP1 user that has sufficient permissions for accessing the definition information of the linked products.

Monitoring Range Settings

Enables or disables the setting of the JP1 resource group's monitoring range in the monitoring tree. When a check mark is displayed beside this menu item, the setting is enabled.

Basic Information

Opens the Properties window (with the Basic Information page displayed) for the node selected in the Monitoring Tree (Editing) window.

Status-Change Condition

Opens the Properties window (with the Status-Change Condition page displayed) for the node selected in the Monitoring Tree (Editing) window.

Common Condition Settings

Opens the Common Condition Settings window, which can be used to add, delete, edit, or check the common conditions managed by JP1/IM - Manager (Central Scope).

This command is available only to users who belong to the JP1 resource group JP1_Console and have JP1_Console_Admin permission.

Event-Issue Conditions

Opens the Properties window (with the Event-Issue Conditions page displayed) for the node selected in the Monitoring Tree (Editing) window.

Acquire Latest Definition

Acquires the latest information of the following definitions from JP1/IM - Manager:

All common conditions

When this command is chosen, the Login window opens. When the user logs in#, the latest information is acquired.

This command is available only to users who belong to the JP1 resource group JP1_Console and have JP1_Console_Admin permission.

Help

Help

Displays the Help contents.

About JP1/IM - View

Displays the JP1/IM - View version information.

#: When Save Login Information is selected, the logged-in user's name, password, and host name are saved, and the Login window does not appear until the user logs out.

Information displayed in the title bar of the Monitoring Tree (Editing) window

The following two kinds of information are displayed in the title bar of the Monitoring Tree (Editing) window:

About JP1/IM - View

The data version of the monitoring tree that is being edited in the Monitoring Tree (Editing) window is displayed in the title bar. The default data version is 09-00.

When JP1/IM - View connects to the server, the version displayed in the title bar changes to the version of JP1/IM - Manager (Central Scope) installed on the server.

When a CSV file saved on the local computer is loaded, the version displayed in the title bar changes to the data version of the CSV file.

Note that the version displayed in the title bar is the data version of the server's monitoring tree or CSV file, and is not a product version.

Login information

When the user's login information is saved in JP1/IM - View, the login information is displayed in the title bar. By default, the function for saving login information is disabled, and no login information is displayed in the title bar. The function is enabled when a check mark appears beside Save Login Information on the File menu, and the user performs one of the operations listed in the following table.

Table 4‒7: Operations requiring the user to log in

Window

Operation

Result

Monitoring Tree (Editing)

From the File menu, choosing Acquire Tree from Server

Existing monitoring tree settings are acquired from JP1/IM - Manager.

From the File menu, choosing Update Server Tree

The edited monitoring tree settings are saved in JP1/IM - Manager.

From the Options menu, choosing Auto-generate Tree

A monitoring tree is automatically generated.

From the Options menu, choosing Acquire Latest Definition

The latest information of the common condition definitions is acquired from JP1/IM - Manager.

From the Edit menu, choosing Edit Visual Monitoring Window List

The Edit Visual Monitoring Window List window opens.

Visual Monitoring (Editing)

Clicking the Acquire Visual Monitoring Data from Server button

Visual monitoring data is loaded from JP1/IM - Manager.

Clicking the Update the Visual Monitoring Data of Server button

The edited visual monitoring data is saved in JP1/IM - Manager.

After the Save Login Information function has been enabled, it remains enabled until the user disables it in the Monitoring Tree (Editing) window.

When the function is enabled, the following information is displayed in the title bar:

user-name@host-name (or user-name@IP-address)

Figure 4‒24: Display in the title bar when login information has been saved and has not been saved

If a login error occurs when login information has been saved, the login information is lost, an error dialog box appears, and the operation is interrupted.

If this situation occurs, the Login window appears when the user performs an operation that requires a login, and the login information entered in the window at that time is saved.

4.16 Create New Monitoring Node window

The Create New Monitoring Node window is used to add a child node to the monitoring group selected in the Monitoring Tree (Editing) window. The Create New Monitoring Node window is displayed when the user chooses Edit from the menu bar of the Monitoring Tree (Editing) window and then Create New Monitoring Node.

The following figure shows an example of the Create New Monitoring Node window.

Figure 4‒25: Create New Monitoring Node window

The following describes the items displayed in the Create New Monitoring Node window.

Monitoring node name

Specifies the name of the new monitoring node to be created. The name can be from 1 to 255 bytes, but must not include tab characters.

Monitoring node type

This area is used to select the type of the new monitoring node to be created. Either the Monitoring object or the Monitoring group radio button can be selected. When the Monitoring object radio button is selected, the drop-down list can be used to select a system-monitoring object (such as AJS Monitoring Object or SSO Monitoring object) or a general monitoring object (user monitoring object). When a system-monitoring object is selected and the OK button is clicked, the Basic Information Settings window appears.

4.17 Basic Information Settings window

The Basic Information Settings window is used to set basic information for the system-monitoring object selected in the Create New Monitoring Node window. The Basic Information Settings window is opened from the Create New Monitoring Node window when the user selects a system-monitoring object from the drop-down list in the Monitoring node type area and then clicks the OK button.

The following figure shows an example of the Basic Information Settings window.

Figure 4‒26: Basic Information Settings window

The items displayed in the Basic Information Settings window differ depending on the system-monitoring object selected in the Create New Monitoring Node window. The items displayed in the above figure are only examples.

For details about the information to be set, see Chapter 8. Lists of System-Monitoring Objects (for Central Scope) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The maximum length of each item that can be specified in the Basic Information Settings window is 1,023 bytes. A maximum of five items can be specified. However, the total length of all items specified in the window must not exceed 1,280 bytes.

4.18 Auto-generation - Select Configuration window

The Auto-generation - Select Configuration window is used to select the configuration of the tree that will be generated automatically. This window is displayed when the user chooses Options from the menu bar of the Monitoring Tree (Editing) window and then Auto-generate Tree.

The following figure shows an example of the Auto-generation - Select Configuration window.

Figure 4‒27: Auto-generation - Select Configuration window

The following describes the items displayed in the Auto-generation - Select Configuration window.

Generation Tree

This list box displays tree templates. The user uses one of these templates to generate a monitoring tree automatically in the Monitoring Tree (Editing) window.

Generate

When this button is clicked, JP1/IM - View collects definition information from the system as defined in the template selected in the list box, and then displays the definition information in the Monitoring Tree (Editing) window. The existing monitoring tree displayed in the Monitoring Tree (Editing) window is replaced by the new one.

Show Differences

When this button is clicked, JP1/IM - View collects definition information from the system as defined in the template selected in the list box, and adds the differential information to the current monitoring tree of JP1/IM - Manager. JP1/IM - View then replaces the monitoring tree in the Monitoring Tree (Editing) window with the monitoring tree that includes the differential information.

Add

When this button is clicked, JP1/IM - View collects definition information from the system as defined in the template selected in the list box, and generates a new monitoring tree from the collected information. JP1/IM - View then displays the new monitoring tree in addition to the existing one. The new monitoring tree is displayed under a monitoring group named NEW_TREE.

4.19 Login User List window

The Login User List window displays a list of the users logged in to JP1/IM - Manager (Central Scope). This window is displayed when the user chooses Options from the menu bar of the Monitoring Tree window and then Logged-in User List.

The Login User List window displays the following four items of user information:

User Name

Host Name

IP Address

Login Date/Time

The following shows an example of the Login User List window.

Figure 4‒28: Login User List window

5 IM Configuration Management Window

This chapter explains the items displayed and defined in IM Configuration Management - View.

5.1 IM Configuration Management window

The IM Configuration Management window is used to view or edit the hierarchical system components (IM configuration), the list of source hosts, and the organization of business groups that are managed by IM Configuration Management. When the user logs in to IM Configuration Management - View (IM Configuration Management), the IM Configuration Management window appears.

The IM Configuration Management window has the Host List, IM Configuration, and Business Group pages, one of which can be opened by choosing the corresponding tab. For details about the Host List page, see 5.1.1 Host List page. For details about the IM Configuration page, see 5.1.2 IM Configuration page. For details about the Business Group page, see 5.1.3 Business Group page.

Note that if different versions of IM Configuration Management - View and IM Configuration Management are connected, items might not be displayed as described in the manual or disabled items might be displayed. Even though the versions of these components are the same, these problems might also occur if the version of JP1/Base is different. For details about the differences in window display, see Appendix H. Connectivity with Previous Versions in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

The following figure shows an example of the IM Configuration Management window.

Figure 5‒1: IM Configuration Management window

Toolbar

Provides buttons for executing functions that are frequently used in the IM Configuration Management window

(Refresh)

Refreshes the information displayed in the tree display area.

(Central Console)

Opens the Central Consol window.

(Central Scope)

Opens the Central Scope window.

(Help button)

Displays Help.

Host List tab

Clicking the Host List tab opens the Host List page. On the Host List page, the hosts registered in the hierarchical structure of the system are listed in the tree display area. If the user selects a host or a virtual host from the tree display area, detailed information about the selected host is displayed in the node information display area.

IM Configuration tab

Clicking the IM Configuration tab opens the IM Configuration page. On the IM Configuration page, the hierarchical structure of the system is displayed in the tree display area. If the user selects a manager or an agent in the tree display area, detailed information about the selected manager or agent is displayed in the node information display area.

Business Group tab

Clicking the Business Group tab opens the Business Group page. The tree display area on the Business Group page displays business groups and the configuration of monitoring groups in each business group.

Display items

The user can show or hide a display item in the node information display area by right-clicking the item and selecting or deselecting the item on the menu. Selecting a display item on the menu displays it (a check mark appears). Deselecting a display item on the menu hides it (the check mark disappears). A display item whose check mark is gray cannot be deselected.

The following table describes the menu items available from the menu bar of the IM Configuration Management window.

Table 5‒1: Menu items available from the menu bar of the IM Configuration Management window

Menu

Command

Description

File

Exit, Logout

Lets the user log out from the connected JP1/IM - Manager (IM Configuration Management), and closes open windows.

Edit

Register Host

Displays the Register Host window.

Delete Host

Deletes the selected host. Multiple hosts can be deleted at one time.

Edit Host Properties

Displays the Edit Host Properties window. The registration information for the host selected in the IM Configuration Management window can be edited.

System Common Settings

Displays the System Common Settings window.

Edit Agent Configuration

Displays the Edit Agent Configuration window. This window can be used to edit agent configuration definitions.

Edit Remote Monitoring Configuration

Displays the Edit Remote Monitoring Configuration window. This window can be used to edit remote monitoring configuration definitions.

Business Group

New

If a root node has been selected:

Choosing this command displays the Create Business Group window. This window can be used to create business groups.

If a business group node or monitoring group node has been selected:

Choosing this command displays the Create Monitoring Group window. This window can be used to create monitoring groups.

Edit Basic Information

If a business group node has been selected:

Choosing this command displays the Edit Business Group Basic Information window. This window can be used to edit the basic information of the business group node.

If a monitoring group node has been selected:

Choosing this command displays the Edit Monitoring Group window. This window can be used to edit the basic information of the monitoring group node.

Delete

If a business group node has been selected:

Choosing this command deletes the selected business group.

If a monitoring group node has been selected:

Choosing this command deletes all items under the selected monitoring group node.

Copy

Copies the tree structure from the selected monitoring group in its entirety.

Cut

Cuts the tree structure from the selected monitoring group in its entirety.

Paste

Pastes the monitoring group that was copied or cut.

If a business group node has been selected:

The monitoring group will be pasted as a monitoring group immediately under the selected business group node.

If a monitoring group node has been selected:

The monitoring group will be pasted immediately under the selected business group node.

Add or Delete Affiliated Hosts

Displays the Add or Delete Affiliated Hosts window. This window can be used to add a host to the selected business group or monitoring group or remove a host from the selected business group or monitoring group.

Copy Path to Clipboard

Copies the path to the selected node (business group or monitoring group) to the Clipboard.

Operation

Collect Host Information

Collects information about the selected host. If the user selects multiple hosts, the Execution Results window appears.

Collect IM Configuration

Acquires the configuration definition information in effect in the system.

Synchronize IM Configuration

Synchronizes the IM configuration information between the upper-level manager and the lower-level manager.

Verify IM Configuration

Compares the configuration definition information of the manager and of the agent to check for whether they match. A message indicating that processing is in progress appears in the Execution Results window.

Batch Collect Profiles

Collects the profiles in a batch operation. A message indicating that processing is in progress appears in the Execution Results window.

Batch Reflect Profiles

Applies the profiles in a batch. A message indicating that processing is in progress appears in the Execution Results window.

Virtualization Configuration

Collect Virtualization Configuration

Collects virtualization configuration information from the virtualization system management host selected in the IM Configuration Management window.

Batch Collect Virtualization Configurations

Collects virtualization configuration information from all virtualization system management hosts managed by IM Configuration Management.

Apply to Central Scope Monitoring Tree

Applies the virtualization configuration information to the monitoring tree in the central scope.

Business Group

Apply Business Group

Applies the edited business group to the system.

When the edited business group is applied, the names of business groups and monitoring groups specified in the following definitions on the central console are also updated:

Severe event definitions

Event search conditions

Event acquisition filter (common exclusion-conditions in extended mode)

Event receiver filter

View filter

Correlation event generation definition

Automated action definition

Conditions for updating the list of action results

Command button definition

Severity changing definition

Display message change definitions

Event-source host mapping definition

Apply to Central Scope Monitoring Tree

Applies the edited business group to the monitoring tree in the central scope.

Launch Base View

Displays IM Configuration Management - View of the base manager.

Display

Display Profiles

Displays the Display/Edit Profiles window.

Login User List

Displays the Login User List window.

Central Console

Displays the Central Console viewer.

Central Scope

Displays the Central Scope viewer.

Display Configuration Status Unknown Icon

Specifies whether to display configuration status unknown icons. The default is to display the icons.

Refresh

Refreshes the information displayed in the IM Configuration Management window.

Help

Help

Displays Help.

Help Contents

Displays the Help contents.

About JP1/IM - View

Displays the version information of IM Configuration Management - View.

5.1.1 Host List page

The Host List page in the IM Configuration Management window lists the hosts registered in IM Configuration Management. The Host List page has two parts: a tree display area in which the hosts are listed in a tree structure, and a node information display area in which detailed information about the nodes displayed in the tree is displayed.

Figure 5‒2: Host List page

Tree display area

Lists the hosts registered in the system hierarchy in a tree structure. The following table describes the items displayed in the tree display area.

Table 5‒2: Items displayed in the tree display area (Host List page)

Display item

Description

Indicates a group.

When a group is selected, the lower-host information for the group is displayed in the node information display area. If there are no lower hosts, nothing is displayed in the node information display area.

Indicates a host. When a host is selected, detailed information about the host is displayed in the node information display area.

Indicates a virtual host. When a virtual host is selected, detailed information about the virtual host is displayed in the node information display area.

The virtual-host tree is always expanded.

Node information display area

The node information display area on the Host List page displays information about the node item selected in the tree display area. The user can change the information that is displayed by clicking one of the following four buttons below.

(Lower Host Information button)

Lists the hosts positioned lower than the selected host.

(Basic Information button)

Displays the basic information about a host.

(Product Information button)

Displays information about the product installed on the host.

(Service Information button)

Displays information about the services running on the host.

Whether information can be displayed depends on the type of the host selected in the tree display area. The following table describes the relationship between host type and information that can be displayed.

Table 5‒3: Types of hosts and information displayable for each (Host List page)

Type of host

Lower host information

Basic information

Product information

Service information

Group

Y

N

N

N

Host

Y#1

Y#2

Y#2

Y

Virtual host

N

Y#2

Y#2

Y

Legend:

Y: Can be displayed.

N: Cannot be displayed.

#1: Displayed if there are lower virtual hosts.

#2: Displayed if host information has already been collected.

(1) Lower Host Information

This area displays the full path name of the node selected in the tree display area, and the hosts positioned lower than the host selected in the tree. For example, if the user selects the upper-level host of a virtual host in the tree (VMM host), the virtual host is displayed. If Host List at the top of the tree is selected, all hosts are displayed.

The following figure shows an example of the window displayed when the Lower Host Information button is clicked.

Figure 5‒3: Host List page displayed when the Lower Host Information button is clicked

Lower Host Information

The items to be displayed in the Lower Host Information area, such as Host, IP address, and Host type can be selected from the menu displayed when the user right-clicks an item name.

The list in this area can be sorted based on an item (column) by clicking the header of the column. Sort the list if it is difficult to find the desired host.

When the header of a column is clicked once, the Δ icon is displayed beside the title. When the header of a column is clicked once again, the icon changes to . These icons alternate every time the header is clicked. The icon displayed for a column disappears when the header of another column is clicked, in which case, the list is re-sorted based on the other column.

The Δ icon means that the list is sorted based on the column in ascending order.

The icon means that the list is sorted based on the column in descending order.

The following table describes the items that can be displayed in the Lower Host Information area.

Table 5‒4: Items displayable in the Lower Host Information area

Item

Displayed information

Host#1, #2

The name of a managed host.

Example: HostA

IP address#1

The managed host's IP address resolved on the manager host.

Example: 10.208.40.40

Example: 2001:db8::28

Host name list

A list of managed hosts to be managed and their alias names.

Example: HostB, HostC

Actual host name

The name actually specified for the managed host.

Example: HostA

Host type#1

One of the following four host types:

Physical host

Virtual host

Logical host

Unknown

Active host#3

The name of the physical host that is the active logical host.

Example: HostA

Standby host#3

The name of the physical host that is the standby logical host.

Example: HostA

VMM host#4

The name of the host on which VMM is running.

Example: HostA

OS#1

One of the following five OS names which is used on the managed host:

Windows

Linux

AIX

SunOS

HP-UX

Collection date/time

The date and time that the host information was last collected.

Example: 2008/01/14 12:34:14

Configuration type

One of the following four IM configuration types:

Integrated manager

Base manager

Relay manager

Agent

Collection status

One of the following four types of host information collection status:

Not collected

Collected

Collection failed

Configuration application date/time

The date and time at which the system hierarchy was applied on the manager host.

This item is updated to the date and time at which the system hierarchy was applied when the configuration distribution succeeded.

For hosts to which the differential distribution functionality did not distribute configuration definition information, this item is also updated to the date and time at which the system hierarchy was applied when the configuration distribution succeeded.

Example: 2008/01/14 12:34:14

Comment#1

A comment.

Example: HQ server

Virtual Manager Type

The type of the virtualization configuration management product.

For virtualization system management hosts:

vCenter

JP1/SC/CM

SCVMM

HCSM

For VMM hosts:

ESX

Hyper-V

KVM

Virtage#5

Remote communication type

One of the following remote communication types:

WMI/NetBIOS

SSH

Blank

Business Group

Business group information.

Monitoring Group

Monitoring group information.

#1: This item is displayed by default.

#2: This item cannot be hidden.

#3: This item is displayed only if the host type is Logical host.

#4: This item is displayed only if the host type is Virtual host.

#5: Virtage indicates the Hitachi Compute Blade logical partitioning feature.

(2) Basic Information

This area displays the full path name, basic information, and detailed information for the host selected in the tree display area. The following figure shows an example of the window displayed when the Basic Information button is clicked.

Figure 5‒4: Host List page displayed when the Basic Information button is clicked

Basic Information

The items to be displayed in the Basic Information area, such as Name, Status, and Date/time, can be selected from the menu displayed when the user right-clicks an item name.

The following table describes the items that can be displayed in the Basic Information area.

Table 5‒5: Items displayable in the Basic Information area

Item

Displayed information

Name#1, #2

The following:

Host information

IM configuration application

IM configuration verification

Profile collection

Profile application

Virtualization Configuration information#3

Remote monitoring settings#4

Status#1

The status after the collection, application, or verification of information.

For Host information:

Collected, Not collected, or Collection failed is displayed as the status of host information collection.

For IM configuration application:

Applied, Not applied, or Application failed is displayed as the status of system hierarchy application.

For IM configuration verification:

Match, Does not match, Verification failed, or Not yet verified is displayed as the status of system hierarchy verification.

For Profile collection:

Collected, Not collected, Partially collected, or Collection failed is displayed as the status of profile collection.

For Profile application:

Applied, Not applied, or Application failed is displayed as the status of profile application.

As the initial condition (profile application has not been performed yet), nothing is displayed.

For virtualization configuration information#3:

Collected, Not collected, Collection failed, or Does not match is displayed as the collection status for virtualization configuration information.

For remote monitoring settings#4:

Collected, Not collected, Collection failed, or Does not match is displayed as the collection status for the remote monitoring configuration.

Date/time#1

The time#5 on the manager that the collection, application, or verification of information was last performed in the JP1/IM - View locale.

For profile application, however, the time on the agent that profile was applied correctly by the JP1/IM - View locale.

Example: 2008/01/14 12:34:14

#1: This item is displayed by default.

#2: This item cannot be hidden.

#3: This item is displayed if the virtualization management type has been set for the selected host.

#4: This item is displayed if remote monitoring has been set for the selected host.

#5: The time on the manager on which IM Configuration Manager is running is used.

Detailed Information

The following table describes the items displayed in the Detailed Information area.

Table 5‒6: Items displayed in the Detailed Information area

Type

Item

Description

Host information

IP address

The managed host's IP address resolved on the manager host.

OS

The name of the OS running on the managed host.

VMM host#1

The name of the host on which VMM is running.

Comment

A comment.

Host

The name of a managed host.

Host name list

A list of managed hosts and their alias names.

Host type

One of the following four host types:

Physical host

Virtual host

Logical host

Unknown host

Collection date/time

The date and time that host information was last collected.

Information collection result

One of the following three types of the host information collection status for agents or remotely monitored hosts:

Not collected

Collected

Collection failed

If all hosts are agents, the host information for remotely monitored hosts is not displayed. If all hosts are remotely monitored, the host information for agents is not displayed.

Actual host name

The name actually specified for the managed host.

Active host#2

The name of the physical host that is the active logical host.

Standby host#2

The name of the physical host that is the standby logical host.

Configuration type

One of the following four IM configuration types:

Integrated manager

Base manager

Relay manager

Agent

Virtualization Configuration information

Virtual Manager Type#3

The virtual manager type set in the virtualization configuration information.

For the virtualization system management host, one of the following types is displayed:

vCenter

JP1/SC/CM

SCVMM

HCSM

For the VMM host, one of the following types is displayed:

ESX

Hyper-V

KVM

Virtage#4

Version#3

Version information about the virtualization configuration management product.

(If the virtual manager type is HCSM) Version information about the HCSM external interface.

If virtualization configuration information is collected from HCSM, no version number is displayed on hosts whose virtual manager type is Virtage#4.

User name#3, #5

User name

Communication type#3, #6

Communication type

Domain name#3, #7

Domain name

Port number#8

Port number

Remote monitoring settings

Remote communication type

Remote communication type

Authentication method#9

Authentication method for remote communication

User name

User name for remote communication

Domain name#10

Domain name for remote communication

#1: This item is displayed only if the host type is Virtual host.

#2: This item is displayed only if the host type is Logical host.

#3: This item is displayed only if Virtualization Configuration information is selected in Basic Information.

#4: Virtage indicates the Hitachi Compute Blade logical partitioning feature.

#5: This item is displayed only if the virtualization management type is vCenter, SCVMM, HCSM, or KVM.

#6: This item is displayed only if the virtualization management type is vCenter, HCSM, or KVM.

#7: This item is displayed only if the virtualization management type is SCVMM.

#8: This item is displayed only if the virtualization management type is HCSM or KVM.

#9: This item is displayed only if the remote communication type is SSH.

#10: This item is displayed only if the remote communication type is WMI/NetBIOS.

(3) Product Information

This area displays the full path name, product information, and detailed information of the host selected in the tree display area. The following figure shows an example of the window displayed when the Product Information button is clicked.

Figure 5‒5: Host List page displayed when the Product Information button is clicked

Product Information

The items to be displayed in the Product Information area, such as Product name and Version, can be selected from the menu displayed when the user right-clicks the item name.

The following table describes the items that can be displayed in the Product Information area.

Table 5‒7: Items displayable in the Product Information area

Item

Displayed information

Product name#1, #2

The product name.

Example: JP1/Base

Version#1

The product version.

Example: 0900

#1: This item is displayed by default.

#2: This item cannot be hidden.

Detailed Information

The items to be displayed in the Detailed Information area, such as Product name, Product module, Version, and Installation path, can be selected from the menu displayed when the user right-clicks the item name.

The following table describes the items that can be displayed in the Detailed Information area.

Table 5‒8: Items displayable in the Detailed Information area

Item

Displayed information

Product name

The product name.

Example: JP1/Base

Product module#

The product module.

Example: P-242C-6LAL

Version#

The product version.

Example: 0900

Installation path#

The installation directory for the product.

Example: c:\Program files\Hitachi\JP1Base

#: If the version of JP1/Base running on the host is 9 or earlier, only information for Product name is displayed. All other items are blank.

(4) Service Information

This area displays the full path name, service information, and detailed information for the host selected in the tree display area. The following figure shows an example of the window displayed when the Service Information button is clicked.

Figure 5‒6: Host List page displayed when the Service Information button is clicked

Service Information

The items to be displayed in the Service Information area, such as Product name, Service name, and Startup status, can be selected from the menu displayed when the user right-clicks the item name.

The following table describes the items that can be displayed in the Service Information area.

Table 5‒9: Items displayable in the Service Information area

Item

Description

Product name#1

The product name of the service.

Example: JP1/Base

Service name#1, #2

The service name.

Example: Event service

Startup status#1, #2

One of the following four service startup statuses:

Running

Stopped

Partially running

Collection failed

#1: This item is displayed by default.

#2: This item cannot be hidden.

Detailed Information

The Detailed Information area displays commands that the user can use to check the status of the service, and displays the standard error output. For remote monitoring, this area displays information equivalent to the information that the status check command outputs to the standard output and standard error output.

5.1.2 IM Configuration page

The IM Configuration page of the IM Configuration Management window displays the system hierarchy. The IM Configuration page has two parts: a tree display area in which the system hierarchy is displayed in a tree structure, and a node information display area in which detailed information about the nodes in a tree is displayed.

Figure 5‒7: IM Configuration page

Tree display area

Displays the system hierarchy in a tree structure. The following table describes the items displayed in the tree display area.

Table 5‒10: Items displayed in the tree display area (IM Configuration page)

Item

Description

Plus sign (+) icon

A plus sign (+) icon is displayed beside the name of a manager that has lower hosts.

If the plus sign (+) icon is clicked, the manager is expanded to show the lower hosts.

Minus sign (-) icon

A minus sign (-) icon is displayed beside the name of a manager that has lower hosts.

If the minus sign (-) icon is clicked, the expanded manager is collapsed to hide the lower hosts.

Indicates an integrated manager (local hosts and remote hosts). If an integrated manager has lower hosts, a plus sign (+) icon or a minus sign (-) icon is displayed beside the integrated manager.

When an integrated manager (remote host) is selected, lower host information for the integrated manager appears in the node information display area. If there are no hosts under the integrated manager, nothing is displayed in the area.

When an integrated manager (local host) is selected, detailed information about the integrated manager is displayed in the node information display area.

Indicates a relay manager. If a relay manager has lower hosts, a plus sign (+) icon or a minus sign (-) icon is displayed beside the relay manager.

When a relay manager is selected, detailed information about the relay manager is displayed in the node information display area.

Indicates a base manger. If a base manager has lower hosts, a plus sign (+) icon or a minus sign (-) icon is displayed beside the base manager. When configuring a hierarchy with a base manager, define the system hierarchy in the base manager first, and then synchronize the hierarchy between the integrated and base managers.

When a base manager (remote host) is selected, lower host information for the base manager is displayed in the node information display area. If there are no hosts under the base manager, nothing is displayed in the area.

When a base manager (local host) is selected, detailed information about the base manager is displayed in the node information display area.

Indicates an agent.

When an agent is selected, detailed information about the agent is displayed in the node information display area.

If any of the cases below applies, an icon indicating an error ()# is superimposed on the icon for an integrated manager, relay manager, base manager, or agent. is an example of the error icon superimposed on the agent icon.

The system hierarchy has not been applied correctly.

This error icon is not displayed for cases where the distribution processing was not completed, such as the connection with JP1/Base failed or a timeout occurred.

The system hierarchy has not been verified correctly.

The results of system hierarchy verification do not match.

The profile has not been applied correctly.

The profile has not been collected correctly.

When the error icon is superimposed on an agent and the user clicks the agent, detailed information about the agent is displayed in the node information display area.

If the result of system hierarchy verification is not addressed because JP1/Base of the host is version 8 or earlier, an icon indicating that the configuration status is unknown ()# is superimposed on the icon for an integrated manager, relay manager, base manager, or agent. is an example of the configuration-status-unknown icon superimposed on the agent icon.

The user can specify whether to display this icon by choosing Display from the menu bar in the IM Configuration Management window and then choosing Display Configuration Status Unknown Icon. The default setting is to display the icon.

When the error icon is superimposed on an agent and the user clicks the agent, detailed information about the agent is displayed in the node information display area.

Indicates agent monitoring.

Indicates remote monitoring.

#

If the conditions for displaying an error icon () and a configuration-status-unknown icon () are both met, the error icon () has precedence.

Node information display area

The node information display area of the IM Configuration page displays information about the node item selected in the tree display area. The user can change the information that is displayed by clicking one of the following four buttons.

(Lower Host Information button)

Displays the hosts positioned lower than the selected host.

(Basic Information button)

Displays the basic information about a host.

(Product Information button)

Displays information about the product installed on the host.

(Service Information button)

Displays information about the services running on the host.

Whether information can be displayed depends on the type of the host selected in the tree display area. The following table describes the relationship between hosts type and information that can be displayed.

Table 5‒11: Types of hosts and information displayable for each (IM Configuration page)

Type of host

Lower host information

Basic information

Product information

Service information

Integrated manager

(local host)

Y

Y

Y#

Y#

Integrated manager

(remote host)

Y

N

N

N

Relay manager

Y

Y

Y#

Y#

Base manager

(local host)

Y

Y

Y#

Y#

Base manager

(remote host)

Y

N

N

N

Agent

(managed)

N

Y

Y#

Y#

Agent

(not managed)

N

N

N

N

Remote host

(site manager)

N

N

N

N

Remote host

(integrated manager)

N

Y

Y#

Y#

Legend:

Y: Can be displayed.

N: Cannot be displayed.

#: Displayed if host information has already been collected.

(1) Lower Host Information

This area displays the full path name of the host selected in the tree display area and the hosts positioned lower than the selected host. The following figure shows an example the window that is displayed when the Lower Host Information button is clicked. Note that business groups and monitoring groups are not displayed.

Figure 5‒8: IM Configuration page displayed when the Lower Host Information button is clicked

For details about the items displayed in the Lower Host Information area, see 5.1.1(1) Lower Host Information.

(2) Basic Information

This area displays the full path name, basic information, and detailed information of the host selected in the tree display area. The following figure shows an example of the window displayed when the Basic Information button is clicked.

Figure 5‒9: IM Configuration page displayed when the Basic Information button is clicked

For details about the items displayed in the Basic Information and Detailed Information areas, see 5.1.1(2) Basic Information.

(3) Product Information

This area displays the full path name, product information, and detailed information of the host selected in the tree display area. The following figure shows an example of the window displayed when the Product Information button is clicked.

Figure 5‒10: IM Configuration page displayed when the Product Information button is clicked

For details about the items displayed in the Product Information and Detailed Information areas, see 5.1.1(3) Product Information.

(4) Service Information

This area displays the full path name, service information, and detailed information of the host selected in the tree display area. The following figure shows an example of the window displayed when the Service Information button is clicked.

Figure 5‒11: IM Configuration page displayed when Service Information button is clicked

For details about the items displayed in the Service Information and Detailed Information areas, see 5.1.1(4) Service Information.

5.1.3 Business Group page

The Business Group page of the IM Configuration Management window displays business groups and the configuration of monitoring groups in each business group. The Business Group page has a tree display area, which displays the configuration of business groups in a tree structure, and a node information display area, which displays detailed information about the node selected in the tree display area.

Figure 5‒12: Example of the Business Group page

Tree display area:

Displays business group nodes and the monitoring group nodes under the business group nodes in a tree structure. The following describes the items displayed in the tree display area.

Table 5‒12: Items displayed in the tree display area (Business Group page)

Display Item

Node type

Description

Root node

Node displayed as the root of the tree for convenience

Business group node

Node indicating a user-defined business group

Monitoring group node

Node indicating a monitoring group (a group of hosts) in a business group

Node information display area:

The node information display area on the Business Group page displays information about the node selected in the tree display area. If the selected node is a business group or monitoring group, the full path to the node is also displayed. The display mode of the node information display area can be switched by choosing either of the following buttons:

Affiliated Host List

While this button is selected, a list of hosts that the selected business group or monitoring group belongs to is displayed.

If a business group has been selected, a list of all hosts that belong to the business group is displayed. If a monitoring group has been selected, the hosts that directly belong to only the monitoring group are displayed. The hosts that directly belong to the monitoring group and also belong to other monitoring groups are not displayed.

The items displayed in this display mode are the same as the items displayed in the Lower Host Information area on the Host List page. For details about the items displayed the Lower Host Information area, see 5.1.1(1) Lower Host Information.

Basic Information

While this button is selected, basic information about the selected business group or monitoring group is displayed.

The items displayed as basic information depend on the selected node.

Table 5‒13: Items displayed as basic information

Item

Description

When a business group node is selected

When a monitoring group node is selected

Business group name

The name of the business group is displayed.

Y

N

Monitoring group name

The name of the monitoring group is displayed.

N

Y

Assigned JP1 resource group name

The JP1 resource group name assigned to the business group is displayed.

Y

N

Business group information applied status

Editing, Applied, or Application failed is displayed as the status of editing for all business groups and monitoring groups displayed in the IM Configuration Management window.

If the status is Editing, the icon also appears. This icon indicates that changes to the root node have not been applied yet.

Y

N

Business group information applied date

The last date and time at which changes were applied is displayed.

Y

N

Comment

The comment on the business group or monitoring group is displayed.

Y

Y

Legend:

Y: Can be displayed.

N: Cannot be displayed.

Acquire update right

When the user selects the Acquire update right check box, the user can edit the configuration of business groups and monitoring groups. When a user has acquired the update permission and edits the configuration, other users are unable to edit the configuration.

5.2 Register Host window

The Register Host window is used to add hosts to the Host List tab of IM Configuration Management.

The following figure shows an example of the Register Host window.

Figure 5‒13: Register Host window

The following describes the items displayed in the Host Registration window. An item with an asterisk (*) must be specified.

Host

Specifies the name of the host to be registered in the system hierarchy, or the name of the device to register in the business group. From 1 to 255 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), and periods (.). Note that the host name cannot end with a hyphen (-) or a period (.).

The user must keep the following in mind when entering the host name:

Make sure that the host name being specified has been assigned to an agent. If a host name that has not been assigned to an agent is specified, JP1/IM - Manager will not operate normally.

Do not specify an IP address or alias as the name of the host to be registered in the system hierarchy.

The host name must be one that the system can resolve.

IP address

The IP address of the host to be registered in the system hierarchy is automatically entered. The user cannot type an IP address.

Comment

The user can enter a comment about the host to be registered in the system hierarchy. From 0 to 80 bytes can be specified.

Host type

Specifies the type of the host to be registered in the system hierarchy. The user can select Physical host, Logical host, Virtual host, or Unknown. Associated hosts can be entered, depending on the host type.

Note that you do not need to change the host type from Physical host if you do not manage a virtualization system configuration. For details, see 8.3 Virtualization configuration management in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

When Physical host is selected:

Virtual Manager Type

Sets the virtual manager type for the selected host. One of the following types can be set:

vCenter

JP1/SC/CM

SCVMM

HCSM

KVM

Setup

Clicking this button opens the Virtual Manager Settings window, which can be used to set virtualization management information.

After the virtualization manager type for the physical host has been set, if the Host type value is changed to Logical host or Unknown, a dialog box that displays the KNAN20301-Q message appears. If the Yes button is clicked, the virtualization manager type set in JP1/IM - View and the collected virtualization configuration information is deleted.

When Logical host is selected:

Active host

The user enters the name of the active logical host. From 0 to 255 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), and periods (.).

Standby host

The user enters the name of the standby host. Multiple host names require a comma (,) as a separator. A maximum of four host names can be entered. From 0 to 1,024 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), periods (.), and commas (,).

When Virtual host is selected:

VMM host

The user enters the name of the host on which VMM is running. From 1 to 255 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), and periods (.).

Virtual Manager Type

Sets the virtual manager type for the selected host. One of the following types can be set:

vCenter

JP1/SC/CM

SCVMM

HCSM

KVM

Setup

Clicking this button opens the Virtual Manager Settings window, which can be used to set virtualization management information.

After the virtualization manager type for the virtual host has been set, if the Host type value is changed to Logical host or Unknown, a dialog box that displays the KNAN20301-Q message appears. If the Yes button is clicked, the virtualization manager type set in JP1/IM - View and the collected virtualization configuration information is deleted.

When Unknown is selected:

Associated hosts cannot be entered.

Remote communication settings

This drop-down list selects the communication method for remote monitoring. The user can select WMI/NetBIOS or SSH. If remote monitoring will not be performed, the user does not need to specify the setting.

Setup

Clicking this button opens the Remote Monitoring Settings window, which can be used to set the communication method for remote monitoring. For details about the Remote Monitoring Settings window, see 5.7 Remote Monitoring Settings window.

5.3 Virtual Manager Settings window

The Virtual Manager Settings window sets virtualization management information. This window is opened from the Register Host window or the Edit Host Properties window by clicking the Setup button in the Virtual Manager Type area.

The following figure shows an example of the Virtual Manager Settings window.

Figure 5‒14: Example of the Virtual Manager Settings window

The following describes the items displayed in this window.

Virtual Manager Type

Use this item to select the virtual manager type for the host. One of the following types can be selected:

vCenter

JP1/SC/CM

SCVMM

HCSM

KVM

User name

Use this item to specify the user name for the selected host if vCenter, SCVMM, HCSM, or KVM is selected as Virtual Manager Type. You can specify a character string that does not contain any control characters and has one to 255 bytes. The specified character string is case sensitive. The previously specified user name is used as the initial value. If no user name was previously specified, a blank is displayed.

Password

Use this item to specify the password for the selected host if vCenter, SCVMM, or HCSM is selected as Virtual Manager Type. You can specify a character string that does not contain any control characters and has one to 255 bytes. The specified character string is case sensitive. The previously specified password is used as the initial value, but the characters are masked by asterisks (*). If no password was previously specified, a blank is displayed.

Communication type

Use this item to specify the communication type for the selected host if vCenter, HCSM, or KVM is selected as Virtual Manager Type. The specified character string is not case sensitive. The following table shows the communication types that can be specified and the default values for virtual manager types.

Table 5‒14: Communication types that can be specified and the default values for virtual manager types

Virtual manager types

Specifiable communication type

Default

vCenter

HTTP

HTTPS

HTTPS

HCSM

HTTP

HTTP

KVM

SSH

SSH

Port number

Use this item to specify the number of the port that is used to communicate with the selected host if HCSM or KVM is selected as Virtual Manager Type. You can specify a number from 1 to 65,535. The default port number differs depending on the selected virtual manager type. The following table shows the default port numbers for the virtual manager types.

Table 5‒15: Virtual manager types and default port numbers

Virtual manager type

Default port number

HCSM

23015

KVM

22

Private key file name

If KVM is selected as Virtual Manager Type, you can use this text box to specify the absolute path name of the private key file that is used to communicate with the selected host's KVM. You can specify a character string that does not contain any control characters and has one to 256 bytes. The specified character string is case sensitive. Do not enclose the path in double-quotation marks ("), even if it contains spaces. If a file name has already been specified, input complete is displayed. If no file name has been specified, a blank is displayed.

If a file name has already been specified, the Private key file name text box is disabled. In this status, the contents of the box cannot be edited. To change the private key file name, click the Clear button to clear the text box.

Domain name

If SCVMM is selected as Virtual Manager Type, this text box specifies the domain name of the selected host. You can specify a character string that does not contain any spaces or tabs, and has one to 255 bytes. The specified character string is case sensitive. The previously specified domain name is used as the initial value. If no domain name has previously been specified, a blank is displayed.

5.4 Edit Host Properties window

The Edit Host Properties window is used to edit the properties of a host that has been registered in the IM configuration, which is the system hierarchy managed by IM Configuration Management. If the user who is currently logged in does not have permission to update the host attribute, host properties cannot be edited.

The following figure shows an example of the Edit Host Properties window.

Figure 5‒15: Edit Host Properties window

The following describes the items displayed in the Edit Host Properties window. An item with an asterisk (*) must be specified.

Host name

The user enters a new host name. From 1 to 255 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), and periods (.). Note that the host name cannot end with a hyphen (-) or a period (.). The names of hosts registered in business groups cannot be changed.

IP address

The IP address of the host is automatically entered. The user cannot type an IP address.

Comment

The user can enter a new comment. From 0 to 80 bytes can be entered.

Host type

Physical host, Logical host, Virtual host, or Unknown can be selected as a new host type. Associated hosts can be entered, depending on the host type.

The display changes, depending on the selected host type, to allow associated hosts to be entered.

When Physical host is selected:

Virtual Manager Type

Use this drop-down list to set the virtual manager type for the selected host. You can select one of the following types:

vCenter

JP1/SC/CM

SCVMM

HCSM

KVM

Setup

Clicking this button opens the Virtual Manager Settings window, which can be used to set virtualization management information.

When Logical host is selected:

Active host

The user enters the name of the active logical host. From 0 to 255 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), and periods (.).

Standby host

The user enters the name of the standby host. Multiple host names require a comma (,) as a separator. A maximum of four host names can be entered. From 0 to 1,024 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), periods (.), and commas (,).

When Virtual host is selected:

VMM host

The user enters the name of the host on which VMM is running. From 1 to 255 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), and periods (.).

Virtual Manager Type

Use this drop-down list to set the virtual manager type for the selected host. You can select one of the following types:

vCenter

JP1/SC/CM

SCVMM

HCSM

KVM

Setup

Clicking this button opens the Virtual Manager Settings window, which can be used to set virtualization management information.

When Unknown is selected:

Associated hosts cannot be entered.

Remote communication settings

This drop-down list selects the communication method for remote monitoring. The user can select WMI/NetBIOS or SSH. If remote monitoring will not be performed, the user does not need to specify the setting.

Setup

Clicking this button opens the Remote Monitoring Settings window, which can be used to set the communication method for remote monitoring. For details about the Remote Monitoring Settings window, see 5.7 Remote Monitoring Settings window.

5.5 Select Hosts window

The Select Hosts window selects hosts that the system will display as candidates for entry.

This window can be opened by using one of the following operations:

In the Edit Host Properties window, from the Host type drop-down list, select VMM host.

In the Edit Agent Configuration window, from the Edit menu, choose Add Host or Exchange Hosts.

In the Edit Remote Monitoring Configuration window, from the Edit menu, choose Add Host or Exchange Hosts.

Figure 5‒16: Select Hosts window

The following describes the items displayed in the Select Hosts window.

Select host(s):

Lists hosts that can be selected. Hosts that have already been selected or cannot be selected are not listed.

The following table describes the items that are displayed in the Select host(s): area.

Table 5‒16: Items displayed in the Select host(s) area

Item

Displayed information

Host

The name of the host registered in the system hierarchy

Host type

The type of the host registered in the system hierarchy. Physical host, Logical host, Virtual host, or Unknown can be displayed in the Host Type column.

Comment

A comment about the host registered in the system hierarchy

Selected host(s):

Lists the hosts that have already been selected.

The items displayed in the Selected host(s): area are the same as the items displayed in the Select host(s): area.

Add

Moves the host selected in the Select host(s): area to the Selected host(s): area.

Delete

Moves the host selected in the Selected host(s): area back to the Select host(s): area.

5.6 Edit Agent Configuration window

The Edit Agent Configuration window is used to edit the IM configuration, which is the system hierarchy managed by IM Configuration Management. This window has a tree display area, the Lower Host Information area, and the Host List area. The tree display area displays the system hierarchy in a tree structure. If the host selected in the tree display area has subordinate hosts, the Lower Host Information area displays a list of these subordinate hosts. The Host List area displays a list of hosts that can be added to the system hierarchy.

When hosts are deleted from the agent configuration and the change is applied, all JP1/Base profiles are deleted from the manager, and the profile trees for the functions running on agents are re-obtained. At this time, all profiles that have not yet been applied on the manager are deleted.

The following figure shows an example of the Edit Agent Configuration window.

Figure 5‒17: Example of the Edit Agent Configuration window

Toolbar

Displays the buttons for commands that are frequently used in the Edit Agent Configuration window.

(Refresh)

Refreshes the information displayed in the tree display area.

(Help button)

Displays Help.

Tree display area

Displays the system hierarchy in a tree structure. In the system hierarchy, the host selected in the tree display area of the Edit Agent Configuration window can be edited. Dragging a host selected in the tree display area, and dropping it in the Host List area deletes the host from the system hierarchy. From the menu displayed when a host is right-clicked in the tree display area, the following operations can be performed: Cut, Paste, Add Host, Delete Host, Exchange Hosts, Base Manager Settings, or Release Base Manager Settings. The following table lists the items that are displayed in the tree display area.

Table 5‒17: Items displayed in the tree display area (Edit Agent Configuration window)

Item

Description

Plus sign (+) icon

A plus sign (+) icon is displayed beside the name of a manager that has lower hosts.

If the plus sign (+) icon is clicked, the manager is expanded to show the lower hosts.

Minus sign (-) icon

A minus sign (-) icon is displayed beside the name of a manager that has lower hosts.

If the minus sign (-) icon is clicked, the expanded manager is collapsed to hide the lower hosts.

Indicates an integrated manager. If an integrated manager has lower hosts, a plus sign (+) icon or a minus sign (-) icon is displayed beside the integrated manager.

Indicates a relay manager. If a relay manager has lower hosts, a plus sign (+) icon or a minus sign (-) icon is displayed beside the relay manager.

Indicates a base manager. If a base manager has lower hosts, a plus sign (+) icon or a minus sign (-) icon is displayed beside the base manager. When configuring a hierarchy with a base manager, define the system hierarchy in the base manager first, and then synchronize the hierarchy between the integrated and base managers.

Indicates an agent.

Acquire update right check box

When the user selects the Acquire update right check box, the user can edit the system hierarchy. When a user has acquired the update permission and edits the system hierarchy, other users are unable to edit the system hierarchy.

Lower Host Information

The items to be displayed in the Lower Host Information area, such as Host, IP address, and Host type, can be selected from the menu displayed when the user right-clicks an item name.

The hosts positioned lower than the item selected in the tree display area are listed in this area. The following table explains the items displayed in the Lower Host Information area.

Table 5‒18: Items displayed in the Lower Host Information area

Item

Displayed information

Host#1, #2

The name of a host.

IP address#1

The managed host's IP address resolved on the manager host.

Host name list

A list of hosts and their alias names.

Actual host name

The name of the host actually specified.

Host type#1

One of the following four host types:

Physical host

Virtual host

Logical host

Unknown

Active host#3

The name of the physical host that is the active logical host.

Standby host#3

The name of the physical host that is the standby logical host.

VMM host#4

The name of the host on which VMM is running.

Alternatively, the name of the virtualization system management host that manages VMM.

OS#1

The name of the OS running on the managed host.

Collection status

One of the following three statuses, which is the status following the host information collection when the managed was connected to JP1/Base:

Not collected

Collected

Collection failed

Collection date/time

The date and time that the host information was last collected.

Configuration type

The type of configuration.

Configuration application date/time

The date and time at which the system hierarchy was applied on the manager host.

This item is updated to the date and time at which the system hierarchy was applied even when the configuration definition information was not distributed to the host.

Comment#1

A comment.

Virtual Manager Type#5

The virtual manager type set in the virtualization configuration information.

For the virtualization system management host, one of the following types is displayed:

vCenter

JP1/SC/CM

SCVMM

HCSM

For the VMM host, one of the following types is displayed:

ESX

Hyper-V

KVM

Virtage#6

Remote communication settings

The type of remote communication.

#1: This item is displayed by default.

#2: This item cannot be hidden.

#3: This item is displayed only if the host type is Logical host.

#4: This item is displayed only if the host type is Virtual host.

#5: This item is displayed only if Virtualization Configuration information is selected in the Basic Information area.

#6: Virtage indicates the Hitachi Compute Blade logical partitioning feature.

Display items

The user can show or hide a display item in the Lower Host Information area by right-clicking the item and selecting or deselecting the item on the menu. Selection of a display item on the menu displays it (a check mark appears). Deselection of a display item on the menu hides it (the check mark disappears). A display item whose check mark is gray cannot be deselected.

Host List

Only the hosts that can be added to the system hierarchy are listed in the Hosts area. Hosts already edited and set in the system hierarchy, and hosts whose actual host name is the same as the name of a host in the system hierarchy are not listed.

The following table describes the menu items available in the Edit Agent Configuration window.

Table 5‒19: Menu items available in the Edit Agent Configuration window

Menu

Command

Description

File

New

Creates new information about the system hierarchy.

Open Agent Configuration

Loads the configuration information of the JP1/IM system stored in a file.

Save Agent Configuration

Saves the configuration information of the JP1/IM system that is being edited to a file.

Acquire Agent Configuration from Server

Acquires the configuration information of the JP1/IM system from the server.

Close

Closes the Edit Agent Configuration window.

Edit

Cut

Copies the node (host) selected in the tree display area.

Paste

Pastes the copied node (host) into another tree structure.

Add Host

Adds a host to the node selected in the tree display area. The Select Hosts window opens.

Delete Host

Deletes the node (host) selected in the tree display area.

Exchange Hosts

Displays the Host Exchange window to enable the node (host) selected in the tree display area to be replaced.

Base Manager Settings

Sets a host as the base manager.

Release Base Manager Settings

Releases the base manager settings.

Undo

Cancels the immediately preceding operation.

Redo

Cancels the operation performed by executing the Undo command.

Operation

Apply Agent Configuration

Applies the changes to the agent configuration.

Update Host Information

Refreshes the information displayed in the Edit Agent Configuration window.

Help

Help

Displays Help.

Help Contents

Displays the Help contents.

About JP1/IM - View

Displays the version information of IM Configuration Management - View.

5.7 Remote Monitoring Settings window

The Remote Monitoring Settings window is used to set information required to perform remote monitoring. This window is opened from the Register Host window or the Edit Host Properties window by clicking the Setup button in the Remote monitoring settings area. The items that must be set depend on whether WMI/NetBIOS or SSH is selected from the Remote communication type drop-down list.

The following describes the items displayed in the Remote Monitoring Settings window.

Remote communication settings

The drop-down list in this area selects the communication method for remote monitoring. The user can select WMI/NetBIOS or SSH. The default is blank. If a blank is selected in this area, other areas are not displayed. The areas displayed in the window vary depending on the selected communication method. If remote monitoring will not be performed, the user does not need to specify the setting.

If WMI/NetBIOS is selected:

A Windows host can be connected. The following figure shows an example of the Remote Monitoring Settings window displayed when WMI/NetBIOS is selected.

Figure 5‒18: Example of the Remote Monitoring Settings window (when WMI/NetBIOS selected)

Setting method

This drop-down list selects the method for setting remote monitoring. The user can select Individual or Common. The default is Individual.

User name

This text box specifies a user name if Individual is selected in Setting method. No user name can be specified if Common is selected.

The specified value is not case sensitive. Alphanumeric characters and symbols other than control characters can be used. A character string having no more than 255 bytes can be specified. The previously specified value is used as the initial value. If no value has previously been specified, a blank is displayed.

This item is required if characters are entered in text boxes other than User name.

Password

This text box specifies a password if Individual is selected in Setting method. No password can be specified if Common is selected.

The specified value is not case sensitive. Alphanumeric characters and symbols other than control characters can be used. A character string having no more than 255 bytes can be specified. The previously specified password is used as the initial value, but the characters are masked by asterisks (*). If no password has previously been specified, a blank is displayed.

This item is required if characters are entered in text boxes other than User name.

Password confirmation

If Individual is selected in Setting method, after the password has been entered, this text box is used for password confirmation. If Common is selected, password re-entry for confirmation is unnecessary.

The characters that can be used, the maximum length, and the default value are the same as for Password.

Domain name

This text box specifies a domain name if Individual is selected in Setting method. If Common is selected, no domain name can be specified.

The specified value is not case sensitive. Alphanumeric characters and symbols other than control characters can be used. A character string having no more than 255 bytes can be specified. The previously specified domain name is used as the initial value. If no domain name has previously been specified, a blank is displayed.

If SSH is selected:

A UNIX host can be connected. The following figure shows an example of the Remote Monitoring Settings window displayed when SSH is selected.

Figure 5‒19: Example of the Remote Monitoring Settings window (when SSH selected)

Selecting the configuration method for remote monitoring

You can select the configuration method for remote monitoring by using this drop down list. The options are Individual or Common. The default is Individual.

User name

This text box specifies a user name if Individual is selected as the Configuration method. If Common is selected, no user name can be specified.

The specified value is not case sensitive. Alphanumeric characters and symbols other than control characters can be used. A character string with a maximum length of 255 bytes can be specified. By default, this text box displays root. If a character string was specified previously, this text box displays the previously specified character string.

This item is required if characters are entered in other text fields.

Port number

This text box specifies the target port number if Individual is selected as the Configuration method. If Common is selected, no port number can be specified.

You can specify a numeric value in the range from 1 to 65535. By default, this text box displays 22. If a numeric value was specified previously, this text box displays the previously specified numeric value.

This item is required when SSH is selected in Remote communication type.

Private key filename

This text box specifies a private key filename if Individual is selected as the Configuration method. If Common is selected, no private key filename can be specified.

A character string of 0 to 4,096 bytes can be specified. Only alphanumeric characters and non-control characters can be used. Do not enclose the character string in double-quotation marks ("), even if it contains spaces. By default, this text box is empty. If a character string was specified previously, this text box displays the previously specified character string.

This item is required when SSH is selected in Remote communication type.

Clear

This button clears the private key filename if Individual is selected as the Configuration method. If Common is selected, the button is disabled.

Authentication method

The string Public key encrypted method is displayed as the authentication method. This value cannot be changed.

5.8 Edit Remote Monitoring Configuration window

The Edit Remote Monitoring Configuration window is used to edit the remote monitoring configuration managed by IM Configuration Management. This window has a tree display area, the Lower Host Information area, and the Host List area. The tree display area displays the remote monitoring configuration in a tree structure. If the host selected in the tree display area has subordinate hosts, the Lower Host Information area displays a list of these subordinate hosts. The Host List area displays a list of hosts that can be added to the remote monitoring configuration.

Important

When hosts are deleted from the remote monitoring configuration and the change is applied, all profiles for the remote monitoring configuration are deleted.

The following figure shows an example of the Edit Remote Monitoring Configuration window.

Figure 5‒20: Example of the Edit Remote Monitoring Configuration window

Toolbar

Displays the buttons for commands that are frequently used in the Edit Remote Monitoring Configuration window.

(Refresh)

Refreshes the information displayed in the tree display area.

(Help button)

Displays Help.

Tree display area

Displays the remote monitoring configuration in a tree structure. In the remote monitoring configuration, the host selected in the tree display area of the Edit Remote Monitoring Configuration window can be edited. Dragging a host selected in the tree display area, and dropping it in the Host List area deletes the host from the remote monitoring configuration. In the tree display area, a node can be moved by drag-and-drop. When the icon of a node is left-clicked, the node is selected as the operation target. There is an icon that indicates the integrated manager () and an icon that indicates a remote managed host ().

Acquire update right

When the user selects the Acquire update right check box, the user can edit the remote monitoring configuration. When a user has acquired the update permission and edits the remote monitoring configuration, other users are unable to edit the remote monitoring configuration.

Lower Host Information

The items to be displayed in the Lower Host Information area, such as Host, IP address, and Host type can be selected from the menu displayed when the user right-clicks an item name.

The hosts subordinate to the item selected in the tree display area are listed in this area. The items displayed in the Lower Host Information area are the same as the items displayed in the Edit Agent Configuration window. For details about the items displayed in the Lower Host Information area, see Table 5-18 Items displayed in the Lower Host Information area.

Host List

Only hosts that can be added to the remote monitoring configuration are listed in the Host List area. Hosts already edited and set in the remote monitoring configuration, and hosts whose actual host name is the same as the name of a host in the system hierarchy (IM configuration) are not listed.

The following table describes the menu items available in the Edit Remote Monitoring Configuration window.

Table 5‒20: Menu items available in the Edit Remote Monitoring Configuration window

Menu

Command

Description

File

New

Creates new information about the remote monitoring configuration.

Open Remote Monitoring Configuration

Loads the remote monitoring configuration information stored in a file.

Save Remote Monitoring Configuration

Saves the configuration information of the remote monitoring configuration that is being edited to a file.

Acquire Remote Monitoring Configuration from Server

Acquires the configuration information of the remote monitoring configuration from the server.

Close

Closes the Edit Remote Monitoring Configuration window.

Edit

Add Host

Adds a host to the node selected in the tree display area. The Select Hosts window opens.

Delete Host

Deletes the node (host) selected in the tree display area.

Exchange Hosts

Displays the Host Exchange window to enable the node (host) selected in the tree display area to be replaced.

Undo

Cancels the immediately preceding operation.

Redo

Cancels the operation performed by executing the Undo command.

Operation

Apply Remote Monitoring Configuration

Applies the changes to the remote monitoring configuration.

Update Host Information

Refreshes the information displayed in the Edit Remote Monitoring Configuration window.

Help

Help

Displays Help.

Help Contents

Displays the Help contents.

About JP1/IM - View

Displays the version information of IM Configuration Management - View.

5.9 Display/Edit Profiles window

The Display/Edit Profiles window is used to display profile information that is valid in JP1/Base or for remote monitoring. The window is also used to view or edit settings files and definition files saved on the IM Configuration Management server.

The Display/Edit Profiles window has two pages: Valid Configuration Information and Configuration File. Each page can be opened by choosing the corresponding button. For details about the Valid Configuration Information page, see 5.9.1 Valid Configuration Information page. For details about the Configuration File page, see 5.9.2 Configuration File page.

The following figure shows an example of the Display/Edit Profiles window.

Figure 5‒21: Display/Edit Profiles window

Toolbar

(Help button)

Displays Help.

Valid Configuration Information button

Clicking this button opens the Valid Configuration Information page. This page displays the configuration information that is valid in JP1/Base or for remote monitoring.

The settings information for the following functions is displayed:

Event forwarding

Log file trapping

Event log trapping

Local action

User management, including the authentication server, user permissions, user registration, and user mapping

Configuration File button

Clicking this button opens the Configuration File page. The Configuration File page is used to display or edit the configuration file or definition files saved on the IM Configuration Management server.

The following configuration file and definition files are displayed and can be edited:

Transfer configuration file

Log file-trap action definition file

Log file-trap startup definition file

Event log-trap action definition file

Local action execution definition file

The following table describes the menu items available from the menu bar of the Display/Edit Profiles window.

Table 5‒21: Menu items available from the menu bar of the Display/Edit Profiles window

Menu

Command

Description

File

Close

Closes the Display/Edit Profiles window.

Edit

Exclusive Editing Settings

Edits the configuration file in exclusive mode.

Release Exclusive Editing

Releases exclusive editing of the configuration file.

Save Configuration File

Saves the configuration file to the IM Configuration Management server.

Copy

Copies the data that is selected in the node information display area for the configuration file. The user does not need to acquire exclusive editing rights before executing this command.

Cut

Copies the data that is selected in the node information display area for the configuration file, and deletes the selected data. The user must acquire exclusive editing rights before executing this command.

Paste

Pastes the copied or cut data to the node information display area for the configuration file. The user must acquire exclusive editing rights before executing this command.

Add Profile

Adds a profile for log file trapping.

Delete Profile

Deletes a profile for log file trapping.

Operation

Collect Profiles

Acquires the profile of the specified node from the host of an agent.

Save/Apply Profiles

Saves the contents of the configuration file residing on the IM Configuration Management server to the agent and applies the contents.

Save on the Server

Saves the configuration file to the IM Configuration Management server.

Apply by Reloading

Applies the contents of the configuration file residing on the IM Configuration Management server to the agent and reloads the contents.

Apply by Restarting

Applies the contents of the configuration file by restarting log file trapping. This command can be used only when a log file trap name for log file trapping is selected.

Apply by Sending File

Applies the contents of the configuration file by sending the file to JP1/Base. If the version of JP1/Base on the agent is earlier than 11-10, this command can be used only when a monitoring name for which a cluster ID has been specified is selected.

Rebuild Profile Tree

Acquires the profile list again from the agent, and re-displays the list displayed in the tree display area.

Start Process

Starts log file trapping of an agent.

Stop Process

Stops log file trapping of an agent.

View

Word Wrap

When the Valid Configuration Information area is displayed in the Display/Edit Profiles window, specifies whether to display all setting items in the window.

Help

Help

Displays Help.

Help Contents

Displays the Help contents.

Version Information

Displays the version information of IM Configuration Management - View.

When the profile list is collected from the agent, if the service corresponding to the profile information is not running, the profile information displayed in the tree display area becomes unavailable, and cannot be selected. The log file trapping function displays only currently running profiles. Note, however, that the function displays all profiles regardless of whether the functions for profiles are active if the version of JP1/Base is 09-10 or later.

For example, if an event service has not started, Event Forwarding Information in the profile list is unavailable and cannot be selected.

To select an unavailable profile, the user must start the corresponding service on the agent, choose the Operation menu and then choose Rebuild Profile Tree. If the log file trapping function on the agent has been started, Rebuild Profile Tree can be executed.

5.9.1 Valid Configuration Information page

The Valid Configuration Information page of the Display/Edit Profiles window displays the profile information that is valid in JP1/Base or for remote monitoring. This page has a tree display area and a node information display area. The tree display area displays in a tree structure the profile information that is valid in for JP1/Base or for remote monitoring. The node information display area displays the detailed information about nodes displayed in the tree display area.

The following figure shows an example of the Valid Configuration Information page.

Figure 5‒22: Valid Configuration Information page

Note that the following description is based on the agent configuration. The items displayed in the page for the remote monitoring configuration might be different from the items described below.

Tree display area

Displays the profile information that is valid in JP1/Base or for remote monitoring in a tree structure. The following describes the items displayed in the tree display area.

Table 5‒22: Items displayed in the tree display area (Valid Configuration Information page)

Item

Description

Plus sign (+) icon

A plus sign (+) icon is displayed when there are files under the setting name.

If the plus sign (+) icon is clicked, the setting name is expanded to show the files.

Minus sign (-) icon

A minus sign (-) icon is displayed when there are files under the setting name.

If the minus sign (-) icon is clicked, the expanded setting name is collapsed to hide the files.

Indicates a host name.

Indicates a product name.

or

Indicates a setting name. If there are files under the setting name, is displayed with a plus sign (+) or a minus sign (-) icon on the left.

If there are no files, is displayed.

Indicates a file name.

Node information display area

The node information display area on the Valid Configuration Information page displays valid configuration information about the display item selected in the tree display area.

The following describes the items displayed for each function selected in the tree display area.

(1) Event Forwarding

The following table describes the items displayed in the Valid Configuration Information area when Event Forwarding is selected.

Table 5‒23: Items displayed in the Valid Configuration Information area (Event Forwarding)

Item name

Level 1

Level 2

Level 3

Level 4

Level 5

Event Forwarding

Event Server Index

Event server

--

--

Forwarding Settings File

Forwarding filters

Filter

Destination (host)#

Conditions#

Suppression Filters

Filter Information

Suppression ID

Unit Time (sec)

Threshold-based (count)

Check Times (to start suppression)

Check Times (to stop suppression)

Suppression Destination

Conditions

Legend:

--: Not applicable

#

When the to-upper format is used in the forwarding settings file (forward) and no upper-level host exists, the transfer conditions are disabled and not displayed because there is no destination host.

The file displayed for Event Forwarding is the forwarding settings file (forward). If the user clicks this file, the current setting values are displayed. For details about this file, see the description of the forwarding settings file in the JP1/Base User's Guide.

(2) Log File Trapping

The following figure shows the items displayed in the Valid Configuration Information area when the profile information for the log file trap is selected.

Table 5‒24: Items displayed in the Valid Configuration Information area (Log File Trapping)

Item name

Level 1

Level 2

Level 3

Level 4

Level 5

Log File Trapping

ID

--

--

--

Startup options

Action definition file name [-f]

--

--

File monitoring interval (sec) [-t]

--

--

Event conversion max size (bytes) [-m]

--

--

Read from the start of log files [-h]

Not specified: 0

Specified: 1

--

--

Display command name (UNIX only) [-n]

--

--

Log data source program name [-p]

--

--

Retry specification for opening a log file [-r]

Not specified: 0

Specified: 1

--

--

Destination server name [-s]

--

--

Log file trap name [-a]

--

--

Use option [-u]

--

--

Specification for UNICODE file monitoring (Windows only) [-g]

In JP1/Base version 10-10 and earlier:

Not specified: 0

Specified: 1 (operates in UTF-16 mode)

In JP1/Base version 10-50 and later:

Not specified: Blank

-g or -g UTF-16 is specified: UTF-16

-g UTF-8 is specified: UTF-8

--

--

Specification of UNICODE file byte order (Windows only) [-b]

--

--

Monitored host [-o]

--

--

Regular expression type [-R]

basic: JP1-specific regular expression

extended: Extended regular expression

--

--

Log files

File name (full path)#1

--

Action Definition

Trap filters

MARKSTRS

MARKSTR

ACTDEFS

ACTDEF

File type

--

--

Record type

--

--

Number of header lines

--

--

Header size (bytes)

--

--

Number of retries

--

--

Retry interval (sec)

--

--

Number of held JP1 events

--

--

Held-events pass specification

--

--

Number of retries for opening a log file

--

--

Retry interval for opening a log file (sec)

--

--

Number of retries for reading a log file

--

--

Number of retries (file monitoring)

--

--

JP1 event for UPD type#2

--

--

JP1 event extended-attribute options

--

--

Legend:

--: Not applicable

#1:

When a Windows host is being monitored remotely, the paths of monitoring log files are displayed in the same format as the startup options in the Configuration File page.

Actual path of a monitoring log file:

\\host-name\shared-folder-name\file-name

Value to be specified as the path of the monitoring log file:

\shared-folder-name\file-name

Examples of displayed paths are as follows:

Example 1: \share\logdir\test01.log \share\logdir\test02.log

Example 2: "\share\log dir\test01.log" "\share\log dir\test02.log"

#2:

This item is displayed if the version of JP1/IM - Manager is 10 or later and the version of JP1/Base on the agent is 10 or later.

The following describes the files that are displayed for Log File Trapping, and the manuals that provide detailed information about the files.

Agent configuration

The current setting values of the log file trap action-definition file and the log-file trap startup definition file (jevlog_start.conf) are displayed. For details, see the descriptions of these files in the JP1/Base User's Guide.

Remote monitoring configuration

The current setting values of the remote-monitoring log file trap action-definition file are displayed. For details about this file, see Remote-monitoring log file-trap action definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(3) Event Log Trapping

The following figure shows the items displayed in the Valid Configuration Information area when the profile information of the event log trap is selected.

Table 5‒25: Items displayed in the Valid Configuration Information area (Event Log Trapping)

Item name

Level 1

Level 2

Level 3

Level 4

Level 5

Event Log Trapping

Action Definition

Trap filters

Filter

Trap name

Log type

Event ID

Conditions

Destination event server name

--

Number of retries

--

Retry interval (sec)

--

Monitoring interval (sec)

--

Matching level

--

Filter check level

--

JP1 event notifications

--

JP1 event extended-attribute options

--

Legend:

--: Not applicable

The following describes the files that are displayed for Event Log Trapping, and the manuals that provide detailed information about the files.

Agent configuration

The current setting values of the action definition file for event log trapping (ntevent.conf) are displayed. For details, see the description of this file in the JP1/Base User's Guide.

Remote monitoring configuration

The current setting values of the remote-monitoring event log trap action-definition file are displayed. For details about this file, see Remote-monitoring event log trap action-definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(4) Local Action

The following figure shows the items displayed in the Valid Configuration Information area when the profile information of the local action is selected.

Table 5‒26: Items displayed in the Valid Configuration Information area (Local Action)

Item name

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Local Action

Execution Definition

Common Block

JP1 user name

--

--

Event ID issuing specification

--

--

Control option string

--

--

Action Blocks

Action Block

Action name

--

Event filter conditions

Conditions

Command

--

Event ID issuing specification

--

Suppression time

--

JP1 user name

--

Environment-variable file name

--

Command option

--

Legend:

--: Not applicable

The file displayed for Local Action is the local action execution definition file (jbslcact.conf). If the user clicks this file, the current setting values are displayed. For details about this file, see the description of that file in the JP1/Base User's Guide.

(5) Authentication Server

The following are the items displayed in the Valid Configuration Information area when the profile information of the authentication server is selected:

Primary server name

Blocked status of the primary server

Secondary server

Blocked status of the secondary server

Authentication server information is set by using the jbssetupsrv command (Windows) or the jbssetusrsrv command (UNIX). For details about these commands, see the relevant descriptions in the JP1/Base User's Guide.

(6) JP1 User-Permissions Level

The following figure shows the items displayed in the Valid Configuration Information area when the profile information of the JP1 user-permission level is selected.

Table 5‒27: Items displayed in the Valid Configuration Information area (JP1 User-Permissions Level)

Item name

Level 1

Level 2

Level 3

Level 4

Level 5

JP1 User-Permission Level

User permissions level

Permissions Level

JP1 user name

--

Authority level for JP1 resource groups

Resource groups

Permissions levels

Legend:

--: Not applicable

The file displayed for JP1 User-Permissions Level is the user permission level file (JP1_UserLevel). If the user clicks this file, the current setting values are displayed. For details about the user permission level file, see the description of that file in the JP1/Base User's Guide.

(7) Registered JP1 Users

The following figure shows the items displayed in the Valid Configuration Information area when the profile information of the JP1 user registration is selected.

Table 5‒28: Items displayed in the Valid Configuration Information area (Registered JP1 Users)

Item name

Level 1

Level 2

Level 3

Registered JP1 Users

JP1 Users

User name

Information for Registered JP1 User is set by using the jbsadduser command. For details about the jbsadduser command, see the description of that command in the JP1/Base User's Guide.

(8) OS User Mapping

The following are the items displayed in the Valid Configuration Information area when the profile information of the OS user mapping is selected:

JP1 user name

Server host name

OS user name

The file displayed for OS User Mapping is the user mapping definition file (jp1BsUmap.conf). If the user clicks this file, the current setting values are displayed. For details about the user mapping definition file, see the description of that file in the JP1/Base User's Guide.

5.9.2 Configuration File page

The Configuration File page in the Display/Edit Profiles window is used to display the configuration file or definition files saved on an IM Configuration Management server. If the user has exclusive editing rights, the user can edit the configuration file or definition files. To acquire exclusive editing rights, in the tree display area of the Display/Edit Profiles window, click JP1/Base as a JP1 product name or Remote Monitoring as a remote monitoring profile. Then, from the Edit menu, choose Exclusive Editing Settings.

The Configuration File page has a tree display area and a node information display area. The tree display area displays the configuration files and definition files managed by the IM Configuration Management server in a tree structure. The node information display area displays detailed information about the configuration files and definition files displayed in the tree structure.

The following figure shows an example of the Configuration File page.

Figure 5‒23: Configuration File page

Tree display area

Displays the configuration files and definition files managed by the IM Configuration Management server in a tree structure. The following table describes the items displayed in the tree display area.

Table 5‒29: Items displayed in the tree display area (Configuration File page)

Item

Description

Plus sign (+) icon

A plus sign (+) icon is displayed when there are files under the setting name.

If the plus sign (+) icon is clicked, the setting name is expanded to show the files.

Minus sign (-) icon

A minus sign (-) icon is displayed when there are files under the setting name.

If the minus sign (-) icon is clicked, the expanded setting name is collapsed to hide the files.

Indicates a host name.

Indicates a product name.

or

Indicates a setting name. If there are files under the setting name, is displayed with a plus sign (+) or a minus sign (-) icon on the left.

If there are no files, is displayed.

Indicates a file name.

Node information display area

The Configuration File area corresponding to the configuration file or definition file selected in the tree display area appears in the node information display area on the Configuration File page.

The following describes the items displayed in the Configuration File area.

Table 5‒30: Items displayed in the Configuration File area

Item

Description

Configuration file contents

Displays information about the configuration file selected in the tree display area. For the items displayed in Configuration file contents, see 5.9.1 Valid Configuration Information page.

Status

Displays Collection status, Collection date/time, Application status, and Application date/time for the configuration file selected in the tree display area.

Collection status

Displays one of the following collection statuses for the configuration file:

- Not collected

- Collected

- Collection failed

Collection date/time

Displays the time#1 on the manager that information was collected in the JP1/IM - View locale.

Collection date/time is updated when any of the following occurs: the profiles are collected in a batch operation (Batch Collect Profiles), the configuration file is collected, the configuration file is applied, or the profiles are applied in a batch operation (Batch Reflect Profiles).

Application status

Displays one of the following application statuses for the configuration file:

- Blank (nothing displayed)

This indicates that the settings file does not exist on the server or settings have been applied. For example, this status arises immediately after the settings file is imported or if the process is stopped.

- Applied

This indicates that the settings file has been applied and the target process is running.

- Reflection failed#2

This indicates that the settings file could not be applied due to an error.

- Saved on the server#2

This indicates that the created or edited settings file saved on the server has not been used by the target process.

Application date/time

Displays the time on the agent that information was applied correctly in the JP1/IM - View locale.

Application date/time is updated when the profiles are applied in a batch operation (Batch Reflect Profiles) or the configuration file is applied.

Saving/application

Applied contents

Apply

Applies the settings to the system managed by IM Configuration Management.

Save

Saves the settings to the server on which IM Configuration Management is running.

Application method

Reload is chosen as the application method.

#1

Indicates the time on the manager on which IM Configuration Management is running.

#2

If there are settings files whose status is Application failed or Saved on the server, an icon indicating an error state is added to the relevant host icon in the tree display area. If this icon is displayed, check for problems with the settings files. If no settings files are being used, display of the error-state icon might be annoying. The following describes how to suppress displaying that icon.

For remote monitoring log file trapping or JP1/Base log file trapping:

From the Edit menu, choose Delete Profile to delete unnecessary settings files.

For remote-monitoring event-log trapping:

From the Operation menu, choose Start Process to start the process. Then, from the Operation menu, choose Stop Process to stop the process.

For JP1/Base event log trapping:

Stop the service on the target host. Then, from the Operation menu, choose Rebuild Profile Tree to re-create the settings files.

The contents of the Configuration File page change when an item under the Log File Trapping node is selected in the tree display area. The following figure shows an example of the Configuration File page displayed when the agent is a Windows host.

Figure 5‒24: Example of the Configuration File page (when an item under Log File Trapping selected)

The items described in the following table will additionally be displayed on the Configuration File page.

Table 5‒31: Items additionally displayed on the Configuration File page (when an item under Log File Trapping selected)

Display item

Description

Startup Options

Monitoring log file

For JP1/Base, specify the paths to the log files that are specified in the log-file trap startup definition file (log file names specified for the jevlogstart command#1 of JP1/Base).

For remote monitoring, specify the paths to the log files (log file names specified for the jcfallogstart#1 or jcfallogdef#1 command).

The following shows the characters that cannot be used in monitoring log file names.

For JP1/Base:

< (0x3c), > (0x3e), and | (0x7c)

For remote monitoring:

< (0x3c), > (0x3e), | (0x7c), * (0x2a), and ? (0x3f)

Note that if a UNIX host is to be monitored, the path names of the log files to be monitored can have alphanumeric characters, hyphens (-), underscores (_), periods (.), and slashes (/). Log files whose path name includes characters other than these might not be monitored normally.

The following shows the maximum number of monitoring log file names that can be specified:

- Log file trapping in Windows: 32

- Log file trapping in UNIX: 100

- Remote-monitoring log file trapping: 32

To specify multiple paths for Monitoring log file, use a space as a separator. If a path specified for Monitoring log file includes spaces, enclose the path in double quotation marks ("). The maximum length of the character string#2 that can be specified is 1,920 bytes.

If a Windows host is to be monitored remotely, the \\host-name part existing in the actual path name must be excluded from each path specified for Monitoring log file as shown below:

Actual path of a monitoring log file:

\\host-name\shared-folder-name\file-name

Value to be specified for Monitoring log file:

\shared-folder-name\file-name

The following shows examples:

Example 1: \share\logdir\test01.log \share\logdir\test02.log

Example 2: "\share\log dir\test01.log" "\share\log dir\test02.log"

Startup locale

This item is displayed if the agent is a UNIX host.

A combination of the character encoding and LANG values can be selected from the drop-down list.

The following shows an example of the Startup locale drop-down list.

For details about the Startup locale drop-down list, see Table 5-32 Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in a Japanese OS), Table 5-33 Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in an English OS), and Table 5-34 Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in a Chinese OS).

Additional options

For JP1/Base, this text box specifies options for the log-file trap startup definition file (options for the normal jevlogstart command#1 or the cluster-specific jevlogstart command#1 of JP1/Base). The following options can be specified:

• File monitoring interval (-t option)

• Event conversion max size (-m option)

• Read from the start of log files (-h option)

• Display command name (-n option)

• Log data source program name (-p option)

• Retry specification for opening a log file (-r option)

• Destination server name (-s option)

• Specification for UNICODE file monitoring (-g option)

• Specification for UNICODE file byte order (-b option)

• Source host name (-x option)

For remote monitoring, this text box specifies additional options (options for the jcfallogstart command#1 or the jcfallogdef command#1). The following options can be specified:

• File monitoring interval (-t option)

• Event conversion max size (-m option)

• Log data source program name (-p option)

• Retry specification for opening a log file (-r option)

• Monitored host (-o option)

• Character encoding (-c option)

The maximum length of the character string that can be specified in the text box is 1,024 bytes.#2

Filter

This item is enabled only when SSH connection is being used.

A regular expression is specified as a predefined filter. Note that the regular expression specified here cannot include the following characters: single quotation marks ('), double quotation marks ("), left angle brackets (<), and right angle brackets (>).

Start the process automatically when the log file trap service starts#3

Select this if you want to start log file trapping automatically when the agent host is restarted or the log file trap service is restarted.

Saving/application

The following items are displayed in Application method when Apply is selected in Applied contents:

Restart#4

Select this to apply the new settings in the settings file by restarting the host.

Send a file

Select this to apply the new settings in the settings file by sending the file.

#1: For details about the normal jevlogstart command and the cluster-specific jevlogstart command, see the chapter on commands in the JP1/Base User's Guide. For details about the jcfallogstart and jcfallogdef commands, see the chapter on commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

#2: If the total number of characters used in Monitoring log file and Additional options exceeds 1,920 bytes, the KNAN20042-E error message is output to report an entry error. If this message is output, divide the log file trap specification.

#3: This is only displayed when LOGFILETRAP_AUTO_START_CONTROL in the common definition information is 00000001 (enabled). LOGFILETRAP_AUTO_START_CONTROL in the common definition information is defined in the profile management environment definition file (jp1cf_profile_manager.conf). For details, see Profile management environment definition file (jp1cf_profile_manager.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

#4: If the startup option for log file trapping or parameters other than MARKSTR and ACTDEF in the log file trap definition file is changed during operation, the change can be applied by selecting Restart. These changes cannot be applied by selecting Apply by Reloading.

Similarly, after the startup option for event log trapping or the server parameter in the action definition file for event log trapping is changed during operation, the change can be applied by selecting Restart. These changes cannot be applied by selecting Apply by Reloading.

The following table describes the settings that can be selected by using the Startup locale drop-down list.

Table 5‒32: Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in a Japanese OS)

Item name displayed in the drop-down list

Encoding

LANG value

Agent host's OS

Displayed by default

SJIS/ja_JP.SJIS

Shift JIS

ja_JP.SJIS

HP-UX

Y

SJIS/japanese

japanese

N

EUC/ja_JP.eucJP

EUC

ja_JP.eucJP

N

EUC/japanese.euc

japanese.euc

N

UTF-8/ja_JP.utf8

UTF-8

ja_JP.utf8

N

C

C

C

N

EUC/ja

EUC

ja

Solaris

Y

EUC/japanese

japanese

N

EUC/ja_JP.eucJP

ja_JP.eucJP

N

SJIS/ja_JP.PCK

Shift JIS

ja_JP.PCK

N

UTF-8/ja_JP.UTF-8

UTF-8

ja_JP.UTF-8

N

C

C

C

N

SJIS/Ja_JP

Shift JIS

Ja_JP

AIX

Y

SJIS/Ja_JP.IBM-932

Ja_JP.IBM-932

N

EUC/ja_JP

EUC

ja_JP

N

EUC/ja_JP.IBM-eucJP

ja_JP.IBM-eucJP

N

UTF-8/JA_JP

UTF-8

JA_JP

N

UTF-8/JA_JP.UTF-8

UTF-8

JA_JP.UTF-8

N

C

C

C

N

UTF-8/ja_JP.UTF-8

UTF-8

ja_JP.UTF-8

Linux

Y

UTF-8/ja_JP.utf8

ja_JP.utf8

N

SJIS/ja_JP.sjis

Shift JIS#

ja_JP.sjis

N

SJIS/ja_JP.SJIS

ja_JP.SJIS

N

C

C

C

N

UTF-8/en_US.UTF-8

en_US.utf8

N

UTF-8/en_US.utf8

en_US.utf8

N

C

C

C

Other than the above

Y

Legend:

Y: This item is displayed by default.

N: This item is not displayed by default.

#: This encoding is valid only when an agent host's OS is SUSE Linux.

Table 5‒33: Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in an English OS)

Item name displayed in the drop-down list

Encoding

LANG value

Agent host's OS

Displayed by default

C

C

C

HP-UX

Y

Solaris

AIX

C

C

Linux

Y

UTF-8/en_US.UTF-8

en_US.utf8

N

UTF-8/en_US.utf8

en_US.utf8

N

C

C

Other than the above

Y

Legend:

Y: This item is displayed by default.

N: Not the default value

Table 5‒34: Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in a Chinese OS)

Item name displayed in the drop-down list

Encoding

LANG value

Agent host's OS

Displayed by default

GB18030/zh_CN.gb18030

GB18030

zh_CN.gb18030

HP-UX

Y

UTF-8/zh_CN.utf8

UTF-8

zh_CN.utf8

N

C

C

C

N

GB18030/zh_CN.GB18030

GB18030

zh_CN.GB18030

Solaris

Y

GB18030/zh_CN.GB18030@pinyin

zh_CN.GB18030@pinyin

N

GB18030/zh_CN.GB18030@radical

zh_CN.GB18030@radical

N

GB18030/zh_CN.GB18030@stroke

zh_CN.GB18030@stroke

N

UTF-8/zh.UTF-8

UTF-8

zh.UTF-8

N

UTF-8/zh_CN.UTF-8

zh_CN.UTF-8

N

UTF-8/zh_CN.UTF-8@pinyin

zh_CN.UTF-8@pinyin

N

UTF-8/zh_CN.UTF-8@radical

zh_CN.UTF-8@radical

N

UTF-8/zh_CN.UTF-8@stroke

zh_CN.UTF-8@stroke

N

C

C

C

N

GB18030/Zh_CN.GB18030

GB18030

Zh_CN.GB18030

AIX

Y

GB18030/Zh_CN

Zh_CN

N

UTF-8/ZH_CN

UTF-8

ZH_CN

N

UTF-8/ZH_CN.UTF-8

ZH_CN.UTF-8

N

C

C

C

N

GB18030/zh_CN.gb18030

GB18030

zh_CN.gb18030

Linux

Y

UTF-8/zh_CN.utf8

UTF-8

zh_CN.utf8

N

C

C

C

N

UTF-8/en_US.UTF-8

en_US.UTF-8

N

UTF-8/en_US.utf8

en_US.utf8

N

C

C

C

Other than the above

Y

Legend:

Y: This item is displayed by default.

N: This item is not displayed by default.

The following table describes whether the items in each configuration file or definition file can be edited, and the operation by which the edited items are applied.

Table 5‒35: Items for each configuration file

No.

Profile

Settings file

Item in the settings file

Editing

Operation to apply changes

Item on the Valid Configuration Information page

1

Event Forwarding

Transfer setting file in JP1/Base

to-upper or to event-server-name

Y

Reload

Destination (host)

2

Event filter for forwarding

Conditions

3

suppress

ID

unit-of-time

threshold-value

confirmation-count

destination

Suppression of event forwarding:

Suppression ID

Unit Time (sec)

Threshold-based (count)

Check Times (to start or end suppression)

Destination (host)

4

Event filter for suppressing forwarding

Conditions

5

Log File Trapping

Log-file trap startup definition file in JP1/Base

--

N

--

Action definition file name (full path) [-f]

6

Additional option -t

Y

Restart

File monitoring interval (sec) [-t]

7

Additional option -m

Event conversion max size (bytes) [-m]

8

Additional option -h

Read from the start of log files [-h]

9

Additional option -n

Display command name [-n]

10

Additional option -p

Log data source program name [-p]

11

Additional option -r

Retry specification for opening a log file [-r]

12

Additional option -s

Destination server name [-s]

13

--

N

--

Log file trap name [-a]

14

Additional option -u

Y

Restart

Use option [-u]

15

Additional option -g

Specification for UNICODE file monitoring (Windows only) [-g]

16

Additional option -b

Specification of UNICODE file byte order (Windows only) [-b]

17

Locale

--

18

Additional option -x

Specification of source host name [-x]

19

Monitoring log file

Log Files > File name (full path)

20

Start the process automatically when the log file trap service starts (SKIP option)

Y

Reload

--

21

JP1/Base log file trap definition file

MARKSTR

Y

Reload

MARKSTRS > MARKSTR

22

ACTDEF

ACTDEFS > ACTDEF

23

FILETYPE

Y

Restart

File type

24

RECTYPE

Record type

25

HEADLINE

Number of header lines

26

HEADSIZE

Header size (bytes)

27

retry-times

Number of retries

28

retry-interval

Retry interval (sec)

29

hold-count

Number of held JP1 events

30

keep-event

Held-events pass specification

31

open-retry-times

Number of retries for opening a log file

32

open-retry-interval

Retry interval for opening a log file

33

read-retry-times

Number of retries for reading a log file

34

upd-output-event

JP1 event for UPD type#1

35

unset-extattr

JP1 event extended-attribute options

36

Event Log Trapping

Action definition file for event log trapping in JP1/Base

server

N

--

Destination event server name

37

retry-times

Y

Reload

Number of retries

38

retry-interval

Retry interval (sec)

39

trap-interval#2

Monitoring interval (sec)

40

matching-level

Matching level

41

filter-check-level

Filter check level

42

jp1event-send

JP1 event notifications

43

trap-name

Trap name

44

filter

Filter > Log type

45

eventid

Event ID

46

filter

Filter > Conditions

47

Local Action

Local action execution definition file in JP1/Base

usr

Y

Reload

Common Block > JP1 user name

48

var

Common Block > Environment-variable file name

49

evt

Common Block > Event ID issuing specification

50

cnt-opt

Common Block > Control option string

51

act

Action Block > Action name

52

cnd

Action Block > Event filter

53

det

Action Block > Suppression time

54

var

Action Block > Environment-variable file name

55

cmd

Action Block > Command

56

cmd-opt usrprofile

Action Block > Command Option

57

evt

Action Block > Event ID issuing specification

58

Remote Log File Trapping

Startup option for remote-monitoring log file trapping

Additional option -t

Y

Restart

File monitoring interval (sec) [-t]

59

Additional option -m

Event conversion max size (bytes) [-m]

60

Additional option -p

Log data source program name[-p]

61

Additional option -r

Retry specification for opening a log file [-r]

62

--

N

--

Destination server name [-s]

63

--

Log file trap name [-a]

64

--

Monitored host [-o]

65

--

Regular expression type

66

Monitoring Log File Locale

Y

Restart

--

67

Monitoring log file

File name under Log Files

68

Filter

--

69

Remote-monitoring log file trap action-definition file

retry-times

Y

Restart

Number of retries for connecting to the event service

70

retry-interval

Retry interval for connecting to the event service (sec)

71

open-retry-times

Number of retries for opening a log file

72

open-retry-interval

Retry interval for opening a log file (sec)

73

hold-count

Number of held JP1 events

74

keep-event

Held-events pass specification

75

FILETYPE

File type

76

HEADLINE

Number of header lines

77

MARKSTR

Y

Reload

MARKSTR under MARKSTRS

78

ACTDEF

ACTDEF under ACTDEFS

79

nset-extattr

JP1 event extended-attribute options

80

Remote Event Log Trapping

Startup option for remote-monitoring event-log trapping

--

N

--

Monitored host [-o]

81

--

Destination event server name

82

--

Regular expression type

83

--

Y

Restart

Filter > Log type [-filter]

84

Remote-monitoring event log trap action-definition file

retry-times

Y

Reload

Number of retries

85

retry-interval

Retry interval (sec)

86

open-retry-times

Number of retries when collecting event log data

87

open-retry-interval

Retry interval for collecting event log data (sec)

88

trap-interval

Monitoring interval (sec)

89

matching-level

Matching level

90

filter-check-level

Filter check level

91

filter

Filter > Conditions

Legend:

Y: Can be edited.

N: Cannot be edited.

--: Cannot be specified.

#1: This item can be edited only when the version of JP1/Base on the agent is 10 or later.

#2: The version of JP1/Base is 11-00 or later, trap-interval is not required to be set.

Note that the contents of the Startup Options area displayed when Event Log Trapping is selected in the tree display area for the remote monitoring configuration vary depending on whether a WMI/NetBIOS connection is selected or another connection is used.

Startup Options

Use the check boxes in this area to select the logging levels to be specified in the predefined filter.

If no log types are selected, all Windows event log data is collected because a predefined filter is not used.

If log types are selected, only the Windows event log data that matches the selectedlog type is collected by using a predefined filter.

5.10 Add Profile window

The Add Profile window is used to add profiles for log file trapping or for remote-monitoring log file trapping. These profiles can be added only when the version of JP1/Base on the agent is 09-10 or later.

The following figures show examples of the Add Profile window that is displayed.

Figure 5‒25: Example of the Add Profile window displayed when adding a profile for log file trapping

Figure 5‒26: Example of the Add Profile window displayed when adding a profile for remote-monitoring log file trapping

Log file trap name

Use this text box to enter the name under which log file traps and remote monitoring log file traps will trap log files.

A character string having from 1 through 30 bytes can be entered. The character string can use alphanumeric characters, hyphens (-), and underscores (_).

The first character must be an alphanumeric character. Alphabetic characters are not case sensitive.

For details on log file trap names, see the following manuals:

For log trap files, see the description of the jevlogstart command and the log-file trap startup definition file in the JP1/Base User's Guide.

For remote monitoring log file traps, see jcfallogstart in Chapter 1.Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Cluster ID

Use this check box to determine whether to specify a cluster ID.

For details on cluster IDs, see the description of the log-file trap startup definition file in the JP1/Base User's Guide.

Enable

To specify a cluster ID, select the Enable check box.

By default, this check box is cleared.

ID

Enter a cluster ID in this text box. A character string having no more than two bytes can be entered. You can specify a value in the range from 0 to 99. The default is 0.

This text box is enabled only when the Enable check box is selected.

5.11 Login User List window

The Login User List window is used to display the users who are logged in to IM Configuration Management - View. If another user has exclusive rights, the exclusive editing status of that user is displayed. A user with IM Configuration Management administrator role permissions can forcibly release the exclusive rights of another user.

The following figure shows an example of the Login User List window.

Figure 5‒27: Login User List window

The following describes the items displayed in the Login User List window.

Table 5‒36: Items displayed in the Login User List window

Item

Displayed information

User name

The name of a user who is logged in to IM Configuration Management - View.

Example: jp1admin

Host

The name of the host the user is logged in to.

Example: HostA

IP address

The IP address of the host the user is logged in to.

Example: 10.208.40.40

Login date/time

The date and time that the user logged in.

Example: 2008/01/01 12:24:31

Exclusive editing status

One of the following type of exclusive editing rights that a user can have:

Editing profile(s)

Editing IM configuration

Editing host properties

Editing business group

Release Exclusive Editing button

When this button is clicked, the exclusive editing rights of the user selected in the Login User List window are released. Note that this operation can be executed only by a user with IM Configuration Management administrator permissions. Note that if the exclusive editing rights are released, the data being edited by the released user is discarded.

Help

Displays Help.

5.12 Execution Results window

The Execution Results window is used to list messages related to the application of information or the result of collection.

The following figure shows an example of the Execution Results window.

Figure 5‒28: Execution Results window

The following table describes the items displayed in the Execution Results window.

Table 5‒37: Items displayed in the Execution Results window

Item

Description

Host

The name of a host on which an operation was executed.

Example: HostA

Completion status

One of the following completion statuses:

Normal

Warning

Error

Completion date/time

The date and time that the processing was completed.

Example: 2008/01/01 12:24:31

Message

List of the messages related to the selected host.

Example: KNAN22017-E

Stop/Close button

Clicking the Stop button cancels the processing currently being executed.

When the processing ends, the Stop button changes to the Close button.

Clicking the Close button closes the Execution Results window.

Help button

Displays Help.

5.13 Exchange Hosts window

The Exchange Hosts window is used to replace a host with another host while maintaining the relationship between the upper-level and lower-level hosts. The user can use this window to replace a host whose system is being configured because of additions or changes to the system configuration with another host.

The following figure shows an example of the Exchange Hosts window.

Figure 5‒29: Exchange Hosts window

The following describes the items displayed in the Exchange Hosts window.

Host before the exchange

This text box displays the host name selected in the tree display area of the Edit Agent Configuration window or the Edit Remote Monitoring Configuration window.

Host after the exchange

The user enters the name of the host that will replace another host. From 0 to 255 bytes can be specified. The specifiable characters are alphanumeric characters, hyphens (-), and periods (.).

Help button

Displays Help.

5.14 Create Business Group window

The Create Business Group window is used to create a new business group.

The following figure shows an example of the Create Business Group window.

Figure 5‒30: Example of the Create Business Group window

The following describes the items displayed in the Create Business Group window.

Business group name

This text box specifies the name of the business group being created. Alphabetic characters are case sensitive. Control characters, slashes (/), and commas (,) cannot be used. A character string that begins or ends with a space cannot be specified. The business group name must be unique in the system. A character string having from 1 through 255 bytes can be specified. The initial value is blank.

Do not use any environment-dependent character for business group names. Such a character might cause character corruption.

Assigned JP1 resource group name

This text box specifies the JP1 resource group name that will be assigned to the business group being created. Specify the name assigned to the resource group in JP1/Base. The characters that can be used are printable ASCII characters other than tabs, spaces, and the following symbols: " / [ ] ; : | = , + ? < >. A character string having from 0 through 64 bytes can be specified. The default is blank.

Comment

This text box specifies a comment about the business group being created. Any characters other than control characters can be used. A character string having from 0 through 80 bytes can be specified. The default is blank.

5.15 Edit Business Group Basic Information window

The Edit Business Group Basic Information window is used to edit the basic information about a business group. When the changes made on this window are applied, the business group and monitoring groups in the following definitions in the central console are also updated:

Severe event definitions

Event search conditions

Event acquisition filter (common exclusion-conditions in extended mode)

Event receiver filter

View filter

Correlation event generation definition

Automated action definition

Conditions for updating the list of action results

Command button definition

Severity changing definition

Display message change definitions

Event-source host mapping definition

The following figure shows an example of the Edit Business Group Basic Information window.

Figure 5‒31: Example of the Edit Business Group Basic Information window

The following describes the items displayed in the Edit Business Group Basic Information window.

Business group name

This text box specifies the name of the business group being edited. Alphabetic characters are case sensitive. Control characters, slashes (/), and commas (,) cannot be used. A character string that begins or ends with a space cannot be specified. The business group name must be unique in the system. A character string having from 1 through 255 bytes can be specified. The default is the name of the business group that was selected for editing.

Do not use any environment-dependent character for business group names. Such a character might cause character corruption.

Assigned JP1 resource group name

This text box specifies the JP1 resource group name that will be assigned to the business group being edited. The characters that can be used are printable ASCII characters other than tabs, spaces, and the following symbols: " / [ ] ; : | = , + ? < >. A character string having from 0 through 64 bytes can be specified. The default is the JP1 resource group name for the business group that was selected for editing.

Comment

This text box specifies a comment about the business group being edited. Any characters other than control characters can be used. A character string having from 0 through 80 bytes can be specified. The default is the comment about the business group that was selected for editing.

5.16 Create Monitoring Group window

The Create Monitoring Group window is used to create a new monitoring group.

The following figure shows an example of the Create Monitoring Group window.

Figure 5‒32: Example of the Create Monitoring Group window

The following describes the items displayed in the Create Monitoring Group window.

Monitoring group name

This text box specifies the name of the monitoring group being created. Alphabetic characters are case sensitive. Control characters, slashes (/), and commas (,) cannot be used. A character string that begins or ends with a space cannot be specified. The monitoring group name must be unique in the same system hierarchy level. A character string having from 1 through 255 bytes can be specified. The initial value is blank.

Do not use any environment-dependent character for Monitoring group names. Such a character might cause character corruption.

Comment

This text box specifies a comment about the monitoring group being created. Any characters other than control characters can be used. A character string having from 0 through 80 bytes can be specified. The default is blank.

5.17 Edit Monitoring Group window

The Edit Monitoring Group window is used to edit the basic information about a monitoring group. When the changes made on this window are applied, the business group and monitoring groups in the following definitions in the central console are also updated:

Severe event definitions

Event search conditions

Event acquisition filter (common exclusion-conditions in extended mode)

Event receiver filter

View filter

Correlation event generation definition

Automated action definition

Conditions for updating the list of action results

Command button definition

Severity changing definition

Display message change definitions

Event-source host mapping definition

The following figure shows an example of the Edit Monitoring Group window.

Figure 5‒33: Example of the Edit Monitoring Group window

The following describes the items displayed in the Edit Monitoring Group window.

Monitoring group name

This text box specifies the name of the monitoring group being edited. Alphabetic characters are case sensitive. Control characters, slashes (/), and commas (,) cannot be used. A character string that begins or ends with a space cannot be specified. The monitoring group name must be unique in the same system hierarchy level. A character string having from 1 through 255 bytes can be specified. The default is the name of the monitoring group that was selected for editing.

Do not use any environment-dependent character for Monitoring group names. Such a character might cause character corruption.

Comment

This text box specifies a comment about the monitoring group being edited. Any characters other than control characters can be used. A character string having from 0 through 80 bytes can be specified. The default is the comment about the monitoring group that was selected for editing.

5.18 Add or Delete Affiliated Hosts window

The Add or Delete Affiliated Hosts window is used to add a host to a business group or monitoring group, or delete a host from a business group or monitoring group.

The following figure shows an example of the Add or Delete Affiliated Hosts window.

Figure 5‒34: Example of the Add or Delete Affiliated Hosts window (displayed for a business group)

The following describes the items displayed in the Add or Delete Affiliated Hosts window.

Host List

This list displays hosts that can be added. This list does not display hosts that have already been added. When a host is being added to a business group, this list does not display any hosts that belong to other business groups. When a host is being added to a monitoring group, this list displays hosts of the business group that the monitoring group belongs to (other than those that already belong to the monitoring group).

The following table lists and describes the items displayed in Host List.

Table 5‒38: Items displayed in Host List

Display item

Description

Host

Displays host names in this column.

Comment

Displays comments in this column.

Monitoring Group

Displays the paths to monitoring groups that hosts belong to. The hierarchy levels in each path are separated by using a slash (/). If a host belongs to multiple monitoring groups, commas (,) are used to separate the paths to them.

Added Hosts

This list displays hosts that have already been added.

The items displayed in this list are the same as those that are displayed in Host List.

Add

Clicking this button adds the hosts selected in Host List to Added Hosts.

Delete

Clicking this button deletes the hosts selected in Added Hosts.

5.19 Change Monitoring Group Name window

The Change Monitoring Group Name window is used to rename monitoring group names. This window can open when the user attempts to paste a monitoring group by selecting Edit, Business Group, and then Paste on the Business Group page of the IM Configuration Management window. If the destination node contains a monitoring group or host having the same name as the monitoring group being pasted, the Change Monitoring Group Name window opens.

The following figure shows an example of the Change Monitoring Group Name window.

Figure 5‒35: Example of the Change Monitoring Group Name window

The following describes the items displayed in the Change Monitoring Group Name window.

Monitoring group name

This text box specifies the new name to be assigned to the monitoring group. Alphabetic characters are case sensitive. Control characters, slashes (/), and commas (,) cannot be used. A character string that begins or ends with a space cannot be specified. The monitoring group name must be unique in the same system hierarchy level. A character string having from 1 through 255 bytes can be specified. The default is the current monitoring group name followed by (n), where n is a number from 2 to 999.

Do not use any environment-dependent character for Monitoring group names. Such a character might cause character corruption.

5.20 System Common Settings window

The System Common Settings window is used to save and manage settings as system common settings. This window is also used to set information for JP1/IM - Manager if remote monitoring is to be performed by IM Configuration Management.

5.20.1 WMI/NetBIOS page

The System Common Settings window has the WMI/NetBIOS page, which is displayed when JP1/IM - View is connected to the Windows version of JP1/IM - Manager. Specify settings if you want to set the authentication information for WMI connections as common values. This page is not displayed when the IM configuration management viewer is connected to the UNIX version of JP1/IM - Manager.

The following figure shows an example of the WMI/NetBIOS page.

Figure 5‒36: Example of the WMI/NetBIOS page

The following describes the items displayed on the WMI/NetBIOS page.

User name

Specify a user who has Administrator permission on the monitored host. Alphabetic characters are not case sensitive. The user name can use alphanumeric characters and symbols other than control characters. A character string having from 0 through 255 bytes can be specified. The previously specified user name is used as the initial value. If no user name has previously been specified, a blank is displayed.

This item cannot be omitted if there are entries in other text boxes on the page.

Password

This text box specifies the password. Alphabetic characters are case sensitive. The password can use alphanumeric characters and symbols other than control characters. A character string having from 0 through 255 bytes can be specified. The previously specified password is used as the initial value, but the characters are masked by asterisks (*). If no password has previously been specified, a blank is displayed.

This item cannot be omitted if there are entries in text boxes other than User name.

Password confirmation

This text box specifies the password again for confirmation. The characters that can be used, the maximum length, and the default value are the same as those for the Password text box.

Domain name

This text box specifies the domain name. Alphabetic characters are not case sensitive. The domain name can use alphanumeric characters and symbols other than control characters. A character string having from 0 through 255 bytes can be specified. The default is the previously specified character string. If no character string has been specified, the default is blank.

5.20.2 SSH page

This page is used to set SSH connection information if the monitoring targets of UNIX are to be monitored.

The following figure shows an example of the SSH page.

Figure 5‒37: SSH Example of the SSH page

The following describes the items displayed on the SSH page.

User name

This text box specifies a user name. Alphabetic characters are not case sensitive. The user name can use alphanumeric characters and symbols other than control characters. A character string having from 0 through 255 bytes can be specified. The default is root.

Port number

This text box specifies a port number. You can specify a numeric value in the range from 1 to 65,535. The default is the previously specified value. If no value has been specified, the default is 22.

Private key file name

Specify a private key file by absolute path. In UNIX, characters in the file path are case sensitive. Alphabetic characters are not case sensitive. The file name can use any characters other than control characters. A character string having from 0 through 4,096 bytes can be specified. Do not enclose the path in double-quotation marks ("), even if it contains spaces. If a file name has already been specified, input complete is displayed. If no file name has been specified, a blank is displayed.

5.20.3 IM Host Account page

The System Common Settings window has the IM Host Account page, which is displayed when JP1/IM - View is connected to the Windows version of JP1/IM - Manager. This page is not displayed when the IM configuration management viewer is connected to the UNIX version of JP1/IM - Manager. When you change the settings of the IM Host Account page, restart the JP1/IM - Manager service.

The following figure shows an example of the IM Host Account page.

Figure 5‒38: Example of the IM Host Account page

The following describes the items displayed on the IM Host Account page.

User name

Specify the user account that starts the collection process for remote monitoring. Specify a user who has Administrator permission on the host where JP1/IM - Manager is installed. Alphabetic characters are not case sensitive. The user name can use alphanumeric characters and symbols other than control characters. A character string having from 0 through 255 bytes can be specified. The previously specified user name is used as the initial value. If no user name has previously been specified, a blank is displayed.

This item cannot be omitted if there are entries in other text boxes on the page.

For cautionary notes that relate to the IM host account in the system common settings, see 8.6.9(2) Precautions for the IM host account of the System Common Settings in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

Password

This text box specifies the password. Alphabetic characters are case sensitive. The password can use alphanumeric characters and symbols other than control characters. A character string having from 0 through 255 bytes can be specified. The previously specified password is used as the initial value, but the characters are masked by asterisks (*). If no password has previously been specified, a blank is displayed.

This item cannot be omitted if there are entries in text boxes other than User name.

Password confirmation

This text box specifies the password again for confirmation. The characters that can be used, the maximum length, and the default value are the same as those for the Password text box.

Domain name

This text box specifies the domain name. Alphabetic characters are not case sensitive. The domain name can use alphanumeric characters and symbols other than control characters. A character string having from 0 through 255 bytes can be specified. The previously specified domain name is used as the initial value. If no domain name has previously been specified, a blank is displayed.

Index

A

Action Log Details window[1]

Action Log window[1]

Action Parameter Definitions window[1]

Action Parameter Detailed Definitions (Extended Event Information) (for compatibility) window[1]

Action Parameter Detailed Definitions (for compatibility) window[1]

Action Parameter Detailed Definitions window[1], [2]

Add Display Message Change Definition Settings window[1]

Add or Delete Affiliated Hosts window[1]

Add panel window[1]

Add Profile window[1]

Add Severity Change Definition Settings window[1]

Auto-generation - Select Configuration window[1]

B

background colors[1]

Preferences[1]

Background Image Settings window[1]

Basic Information Settings window[1]

BJEX

windows displayed during management of response-waiting events[1]

C

Change Monitoring Group Name window[1]

Common Condition Detailed Settings window[1]

Common Condition Settings window[1]

Common Exclusion-Condition Settings (Extended) window[1]

Common Exclusion-Conditions Settings window[1]

Conditions for Updating List of Action Results window[1]

Configuring the Dashboard tab[1]

conventions

diagrams[1]

fonts and symbols[1]

version numbers[1]

Create Business Group window[1]

Create Monitoring Group window[1]

Create New Monitoring Node window[1]

D

Dashboard window[1]

Detailed Settings for Event Receiver Filter window[1]

diagram conventions[1]

Display/Edit Profiles window[1]

Configuration File page[1]

Valid Configuration Information page[1]

Display Message Change Definition Settings window[1]

Display Message Change Definitions window[1]

E

Edit Agent Configuration window[1]

Edit Basic Information window[1], [2]

Edit Business Group Basic Information window[1]

Edit Event Details window[1]

Edit Extended Attributes (for compatibility) window[1]

Edit Extended Attributes window[1]

Edit Host Properties window[1]

Edit Individual Condition window[1]

Edit Monitoring Group window[1]

Edit Remote Monitoring Configuration window[1]

Edit Visual Monitoring Window List window[1]

Event Acquisition Conditions List window[1]

Event Acquisition Settings (for compatibility) window[1]

Event Acquisition Settings window[1]

Event Console window[1]

Monitor Events page[1]

Search Events page[1]

Severe Events page[1]

Event Details window[1]

Event display start-time specification area[1]

Event-Information Mapping Definitions window[1]

Event-Information Mapping Detailed Definitions window[1]

Event Search Conditions (Program-Specific Information in Extended Attribute) window[1]

Event Search Conditions window[1]

Event Search Detailed Conditions (Program-Specific Information in Extended Attribute) window[1]

Exchange Hosts window[1]

Execute Command window[1]

Execution Results window[1]

Extended Attribute (Common Information/Specific Information) Settings window[1]

F

font conventions[1]

for acquiring events for which specific severity level has been defined and JP1/SES events[1]

G

Guide window[1]

I

IM Configuration Management window[1]

Host List page[1]

Integrated Operation Viewer Window

Add node dialog box[1]

Custom UI tab[1]

Details area[1]

Displaying search result format[1]

Events area[1]

Job flow tab[1]

Metrics that can be retrieved from linked products[1]

Operating status area[1]

overview[1]

Performance tab[1]

Related node tab[1]

Repeated event list window[1]

Suggestion tab[1]

Sunburst chart format[1]

Tree chart format[1]

Trends tab[1]

J

JP1/AS

windows displayed during management of response-waiting events[1]

L

List of Action Results window[1]

List of Definition Files for Managers and List of Definition Files(host-name) windows[1]

List of IM Client window[1]

List of Integrated Agents window[1]

List of Lower Managers window[1]

List of Repeated Event Conditions window[1]

List of Response Action Results window[1]

Login User List window[1], [2]

Login window[1]

Login window of Central Consol and Central Scope[1]

Login window of IM Configuration Management[1]

Login window of the Intelligent Integrated Management Base[1]

M

memo entries setting function[1]

menu items

in Edit Agent Configuration window[1]

in Edit Remote Monitoring Configuration window[1]

menu items available from menu bar of Display/Edit Profiles window[1]

menu items available from menu bar of IM Configuration Management window[1]

menu items available from menu bar of Monitoring Tree (Editing) window[1]

menu items available from menu bar of Monitoring Tree window[1]

menu items of Event Console window[1]

Monitoring Tree (Editing) window[1]

Monitoring Tree window[1]

N

Notes on Dashboard window[1]

notes on operations in windows[1]

O

Open Visual Monitoring Window window[1]

P

Preferences window[1]

Preview Command Execution Content window[1]

Preview Execution Script of Response Action window[1]

Properties

Event-Issue Conditions page[1]

Status-Change Condition page[1]

Properties window[1]

Basic Information page[1]

General page[1]

R

Register Host window[1]

Related Events (Correlation) window[1]

Related Events (Summary) window[1]

Remote Monitoring Settings window[1]

Repeated Event Condition Settings window[1]

Basic Settings page[1]

Repeated Event Condition Settings window (Options page)

Options page[1]

Response Action Results window[1]

restrictions on search function by JP1/Base version[1]

Run Response Action window[1]

S

Search Events page[1]

Search window[1]

Select Hosts window[1]

Select Icon window[1]

Setting Dashboard window[1]

Settings for Event Receiver Filter window[1]

Settings for View Filter window[1]

Severe Event Definitions window[1]

Severe Events page[1]

Severity Change Definition Settings window[1]

Show Initial Secret window[1]

slider[1]

Status-Change Condition Settings window[1]

status icons[1]

symbol conventions[1]

syntax conventions[1]

System Common Settings window[1]

System Environment Settings window[1]

Communication page[1]

Display page[1]

General page[1]

T

Tool Launcher window[1]

V

version number conventions[1]

View List of Filters window[1]

View Severity Change Definitions window[1]

Virtual Manager Settings window[1]

Visual Icon Selection window[1]

Visual Monitoring (Editing) window[1]

Visual Monitoring window[1]

W

when consolidation start event or repeated events cannot be displayed[1]

when correlation source events cannot be displayed in Related Events list[1]

Window related to response action[1]

windows

Action Log[1]

Action Log Details[1]

Action Parameter Definitions[1]

Action Parameter Detailed Definitions[1], [2]

Action Parameter Detailed Definitions (Extended Event Information) (for compatibility)[1]

Action Parameter Detailed Definitions (for compatibility)[1]

Add Display Message Change Definition Settings window[1]

Add or Delete Affiliated Hosts[1]

Add Profile[1]

Add Severity Change Definition Settings window[1]

Auto-generation - Select Configuration[1]

Background Image Settings[1]

Basic Information Settings[1]

Change Monitoring Group Name[1]

Common Condition Detailed Settings[1]

Common Condition Settings[1]

Common Exclusion-Condition Settings (Extended) window[1]

Common Exclusion-Conditions Settings[1]

Conditions for Updating List of Action Results[1]

Create Business Group[1]

Create Monitoring Group[1]

Create New Monitoring Node[1]

Detailed Settings for Event Receiver Filter[1]

Display/Edit Profiles[1]

Display/Edit Profiles (Configuration File page)[1]

Display/Edit Profiles (Valid Configuration Information page)[1]

Display Message Change Definition Settings window[1]

Edit Agent Configuration[1]

Edit Basic Information[1], [2]

Edit Business Group Basic Information[1]

Edit Event Details[1]

Edit Extended Attributes[1]

Edit Extended Attributes (for compatibility)[1]

Edit Host Properties[1]

Edit Individual Condition[1]

Edit Monitoring Group[1]

Edit Remote Monitoring Configuration[1]

Edit Visual Monitoring Window List[1]

Event Acquisition Conditions List[1]

Event Acquisition Settings[1]

Event Acquisition Settings (for compatibility)[1]

Event Console[1]

Event Console (Monitor Events page)[1]

Event Console (Search Events page)[1]

Event Console (Severe Events page)[1]

Event Details[1]

Event-Information Mapping Definitions[1]

Event-Information Mapping Detailed Definitions[1]

Event Search Conditions[1]

Event Search Conditions (Program-Specific Information in Extended Attribute)[1]

Event Search Detailed Conditions (Program-Specific Information in Extended Attribute)[1]

Exchange Hosts[1]

Execute Command[1]

Execution Results[1]

Extended Attribute (Common Information/Specific Information) Settings window[1]

Guide[1]

IM Configuration Management[1]

IM Configuration Management (Business Group page)[1]

IM Configuration Management (IM Configuration page)[1]

List of Action Results[1]

List of Repeated Event Conditions window[1]

Login[1]

Login User List[1], [2]

Monitoring Tree[1]

Monitoring Tree (Editing)[1]

notes[1]

Open Visual Monitoring Window[1]

Preferences[1]

Preview Command Execution Content[1]

Properties[1]

Properties (Basic Information page)[1]

Properties (Event-Issue Conditions page)[1]

Properties (General page)[1]

Properties (Status-Change Condition page)[1]

Register Host[1]

Related Events (Correlation)[1]

Related Events (Summary)[1]

Remote Monitoring Settings[1], [2]

Repeated Event Condition Settings window[1]

Repeated Event Condition Settings window (Basic Settings page)[1]

Repeated Event Condition Settings window (Options page)[1]

Search[1]

Select Hosts[1]

Select Icon[1]

Settings for Event Receiver Filter[1]

Settings for View Filter[1]

Severe Event Definitions[1]

Severity Change Definition Settings window[1]

Status-Change Condition Settings[1]

System Common Settings[1]

System Environment Settings[1]

System Environment Settings (General page)[1]

System Environment Settings window (Communication page)[1]

System Environment Settings window (Display page)[1]

Tool Launcher[1]

View List of Filters[1]

View Severity Change Definitions window[1]

Virtual Manager Settings[1]

Visual Icon Selection[1]

Visual Monitoring[1]

Visual Monitoring (Editing)[1]

windows (when linkage with BJEX is enabled)

Enter Response window[1]

Event Console window[1]

Event Details window[1]

Event Search Conditions window[1]

filter condition definition windows[1]

Preferences window[1]

Related Events windows[1]

window transitions[1]

windows (when linkage with JP1/AS is enabled)

Enter Response window[1]

Event Console window[1]

Event Details window[1]

Event Search Conditions window[1]

filter condition definition windows[1]

Preferences window[1]

Related Events windows[1]

window transitions[1]

windows displayed during management of response-waiting events[1]

Windows related to Option[1]

window transitions[1]