Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide

[Contents][Glossary][Index][Back][Next]

Appendix L. Glossary

agent
In JP1/IM, a host managed by a manager, or a program managed by a manager program.
JP1/Base acts as the agent program in a JP1/IM system, receiving processing requests from JP1/IM - View and JP1/IM - Manager, and performing tasks such as managing JP1 events and executing commands.
Each agent runs JP1/Base, which provides the core functionality for the JP1/IM system.

auto-generation
A function that automatically generates a monitoring tree in the JP1/IM Central Scope.
By generating a tree automatically, and then customizing it to suit your mode of operation, you can easily set up an environment to perform system monitoring based on a monitoring tree.
A monitoring tree represents the system to be monitored by JP1/IM in tree format, with the nodes to be monitored arranged upon it. Every node in the tree needs to be defined, and the JP1/IM auto-generation function can produce this huge amount of definition information automatically. Using this function, you can automatically collect definition information from the hosts to be monitored by JP1/IM, and automatically create a monitoring tree. If the system is reconfigured, you can extract the differences between the new and existing monitoring trees as difference information.

automated actions
A function that automatically executes a command as an action when a specific JP1 event is received.
Using an automated action, you can, for example, execute a command to inform the system administrator of an important event that occurred while JP1/IM was monitoring the system. In an automated action definition, you can specify conditions for executing the action and the command to be executed as the action.

basic attribute
Information (an attribute) held by all JP1 events.
See also JP1 event.

basic information
Basic information held by the monitoring nodes that make up a monitoring tree in the JP1/IM Central Scope.
In the case of a monitoring group, the name that identifies the group is basic information.
For example, you can assign a group name such as Daily accounting routines or Database server group to jobs or servers grouped according to the monitoring objectives.
In the case of a monitoring object, the information for identifying the object is basic information.
For example, you can define a combination of information, such as a jobnet name together with a host name, for identifying the monitoring object within the system.
Basic information can be used, for example, when searching for monitoring nodes or in the conditions (individual conditions in a status change condition) for identifying the node concerned when a JP1 event occurs in the job or resource being monitored.

Central Console
A program that enables integrated system management by centrally managing events in the system based on JP1 events.
In the Central Console, events occurring on the various hosts in the system are managed using JP1 events. The more important JP1 events, which need to be managed or dealt with in some way, are forwarded to a manager where they can be centrally managed. By monitoring these JP1 events in a viewer (the Event Console window), the user can monitor the whole system.
The Central Console also supports automated actions that execute a command automatically in response to specific JP1 events, and provides functionality for operating on the system from a viewer.
These features of the Central Console enable the user to efficiently perform the monitoring, error investigation, and troubleshooting tasks involved in system management.

Central Scope
A program that enables objective-oriented system monitoring via a graphical user interface matched to the objectives of the system administrator.
In the Central Scope, the hosts, programs, jobs, and other system resources that need to be monitored are displayed in a tree view in a Monitoring Tree window. Because the relationships between the monitored objects are presented visually, the user has a clear picture of the likely impact of any problem in the system.
The Visual Monitoring window lets you display key resources and functions that you need to watch closely in a map view. You can arrange the monitoring points as icons on a map, organizational chart, or other background image. This allows the administrator to centrally monitor the system, no matter how large, from the required viewpoints.

cluster system
A system in which multiple servers work together as a single system.
A cluster system is designed to ensure uninterrupted job processing and to enhance availability by having another server continue processing if a failure occurs. The processing of another server taking over processing is known as failover.
If the active server (primary node) fails, the standby server (secondary node) takes over. Because the job processing is switched from the active to the standby node, a cluster system is also called a node switching system.
Cluster systems include load-sharing systems with multiple servers that perform parallel processing. In this manual, however, cluster system refers only to failover functionality for preventing interruption of job processing.

command execution log
A generic name for the database in which an execution log is recorded when a command is executed from JP1/IM - View or a command is executed in an automated action.
The logs for command execution from JP1/IM - View and for command execution in automated actions are managed separately. The file names generated in practice are as follows.
  • Command execution logs for command execution from JP1/IM - View: CMDISAMLOGV8.*
  • Command execution logs for command execution in automated actions: ACTISAMLOGV8.*

common condition
A status change condition that applies to all monitoring objects of the same type in the JP1/IM Central Scope.
See also status change condition.

common definition information
A database containing the definition parameters for the JP1 execution environment.
Common definition information is managed by JP1/Base and is used by JP1/Base, JP1/IM, JP1/AJS, and JP1/Power Monitor 06-02 or later. The database resides on a local disk of each server, and the definition parameters are sorted according to the physical host or logical host to which they apply.
When JP1 is used in a cluster system, the logical host settings in the common definition information residing on the primary and secondary servers must be identical. For this reason, after completing the setup and environment settings on the primary server, you must copy the defined parameters to the secondary server.

common exclusion conditions
Conditions that form part of an event acquisition filter and consist of a group of conditions for filtering out JP1 events monitored by JP1/IM.

configuration definition
Information defining the configuration of the system managed by JP1/IM.
A configuration definition defines the hierarchy of managers and agents in JP1/IM. Managers can be defined at different levels. For example, you can define lower-level base managers under a higher-level integrated manager.
Configuration definitions are managed by the JP1/IM configuration management functionality.
The information about the host relationships defined in a configuration definition can be used in JP1/IM to specify the hosts to which important JP1 events should be forwarded, for example, or to define the target host for executing a command in an automated action.

configuration management
Functionality for managing the hosts in the JP1/IM system as a hierarchy of managers and agents.
You can manage the system configuration by using IM Configuration Management, or by editing the definition files directly.
Configuration definition information is used to manage the hosts.
See also IM Configuration Management and configuration definition.

consolidated display of repeated events
A function that summarizes identical JP1 events received in succession by JP1/IM - View into a single JP1 event for display on the Monitor Events page or Severe Events page of the Event Console window. By using this function, you can prevent other important JP1 events from being overlooked.
Under this function, an event that summarizes identical JP1 events is known as a consolidation event. There are two types of consolidation events: an event in which repeated events are still being consolidated (event being consolidated) and an event in which the consolidation processing has been completed (consolidation completion event).
The first of identical JP1 events received by JP1/IM - View is known as a consolidation start event. The subsequently received identical JP1 events are called repeated events, and events that are not repeated, and therefore not consolidated, are known as non-consolidation events.

consolidation completion event
See consolidated display of repeated events.

consolidation event
See consolidated display of repeated events.

consolidation start event
See consolidated display of repeated events.

correlation event
A JP1 event issued by correlation processing. JP1/IM can issue a new JP1 event as a correlation event whenever a related JP1 event is issued. The correlation event and the association between the JP1 events can be defined by the user as a correlation event generation definition.

correlation event generation definition
A definition for issuing correlation events, specifying which types of JP1 events to associate, and the nature of the issued correlation event. A correlation event generation definition consists of a correlation event generation condition name, a filtering condition for the correlation target range, one or more event conditions, a timeout period, an event correlation type, a duplicate attribute value condition, a maximum correlation number, a correlation approval event, and a correlation failure event.

correlation source event
A JP1 event that triggers issue of a correlation event. Correlation source events can be listed in the Related Events (Correlation) window.
See also correlation event.

Cosminexus
A core product used to build application server-based systems for developing and running business applications that provide high performance and reliability.

delay monitoring
Monitoring of the execution time of an automated action, from start to completion. Delay monitoring is able to detect and notify the user of any automated action that fails to complete within a set time.

event acquisition filter
A filter for setting detailed conditions about the JP1 events to be acquired by JP1/IM - Manager for display in the Event Console window.
You can use an event acquisition filter to acquire events in JP1/SES format or to suppress acquisition of specific JP1 events.

event being consolidated
See consolidated display of repeated events.

event buffer
An area of memory used by JP1/IM - Manager (JP1/IM - Central Console) to store JP1 events extracted from the event service of JP1/Base.
JP1 events are stored in the event buffer when:
  • JP1/IM - Manager (JP1/IM - Central Console) starts
  • JP1 events are stored in the event database of JP1/Base
JP1/IM - View acquires events from the event buffer, not directly from the event service of JP1/Base.

Event Console window
A JP1/IM - View windows that shows the JP1 events received by the Central Console in a time series. The Event Console window is the first window that appears when you log in to JP1/IM - Central Console.
JP1/IM centrally manages the events generated on the various hosts by recording them as JP1 events and forwarding the more important ones to a JP1/IM manager. By viewing these JP1 events in the Event Console window, you can centrally monitor events occurring in the system.

event display start-time specification
When you use the integrated monitoring database, you can change the JP1 events listed in the Event Console window of JP1/IM - View by specifying a date and time or by moving the slider in the event display start-time specification area.

event generation condition
A condition that determines the type of status change in a monitoring node in the JP1/IM Central Scope that will cause the node to issue a JP1 event.
A monitoring node manages the status of the job or resource it is monitoring based on JP1 events issued by that job or resource. By defining an event generation condition, a JP1 event can be issued when a monitoring node changes status (that is, when a problem of some kind occurs in the job or resource being monitored), enabling early detection and swift response to any problems.
The JP1 event issued as a result of this condition has the event ID 00003FB0.

event guide function
A function that displays guide information in the JP1/IM Central Console for investigating and resolving JP1 events that occur during system monitoring.
By displaying troubleshooting procedures and other advice on handling JP1 events that could impact on the system, you can reduce the system administrator's workload when a problem occurs.
The event guide function displays guidance targeted to a specific JP1 event. The JP1/IM Central Scope provides a similar function, but targeted to a specific monitoring node.
See also guide function.

event ID
One of the attributes of a JP1 event. An event ID is an identifier indicating the program that issued the event and the nature of the JP1 event. It is a basic attribute and has the attribute name B.ID.
Event IDs are hexadecimal values, such as 7FFF8000.
Event IDs are uniquely assigned by each of the programs in the JP1 series. For details on the JP1 events issued by a specific program, see the documentation for the product concerned.
The values from 0 to 1FFF, and from 7FFF8000 to 7FFFFFFF, are available as user-specifiable event IDs.
A JP1 event is an 8-byte number consisting of a basic code (upper four bytes) and extended code (lower four bytes). Usually only the basic code is used, representing a 4-byte event ID. The extended code is 0, except in special cases, as when set by the user in the API. When both the basic and extended codes need to be included, they are joined with a colon (:) and appear as 7FFF8000:0, for example.

event level
One of the attributes of a JP1 event, indicating the severity of an event that occurred in the system.
The event level is common information in the extended attributes of a JP1 event, and the attribute name is E.SEVERITY.
Event levels are Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.

event receiver filter
A filter for setting conditions, for individual JP1 users, about the JP1 events that can be viewed in the Event Console window.
Use an event receiver filter when you want to restrict the JP1 events that can be viewed by a particular user who performs operational tasks.

exclusion condition
A filter condition that filters out JP1 events that match the condition. An exclusion condition can be specified in an event acquisition filter, view filter, severe events filter, event receiver filter, or event search.

extended attribute
Information (an attribute) held by a JP1 event, optionally set by the source program when issuing a JP1 event.
See also JP1 event.

failover
Uninterrupted JP1 processing by transferring JP1 operations to another server when a failure occurs on the active server. Or, switching by the system administrator of the server that is currently executing JP1 processing.
Because the server on a secondary node takes over from the server on the primary node, failover is also known as node switching.

forwarding filter
A filter set on each JP1/IM host, specifying conditions for the JP1 events to be forwarded from that host and the destination manager to which they are sent.
These settings are registered with the JP1/Base event service, and are known as a forwarding filter in JP1/IM.
In JP1/IM, events occurring in the system are centrally managed as JP1 events. To enable centralized management, JP1 events are forwarded to JP1/IM managers. The particular types of JP1 events to be forwarded are defined in a forwarding filter.

general monitoring object
A monitoring object whose target can be set by the user. A system-monitoring object when edited becomes a general monitoring object.
The monitoring node type is User Monitoring Object.
See also monitoring object.

guide function
A function that displays error causes and action procedures in the JP1/IM Central Scope relating to problems occurring in the system.
By displaying troubleshooting procedures and other advice on handling problems arising during system monitoring, you can reduce the system administrator's workload at the initial response stage.
The guide function displays guidance targeted to a specific monitoring node. The JP1/IM Central Console provides a similar function, but targeted to a specific JP1 event.
See also event guide function.

health check function
A function that informs the user, by means of a JP1 event or notification command, when a hangup occurs in a JP1/IM or JP1/Base process.
The JP1/IM health check function can detect hangups in JP1/IM - Manager processes# and in the JP1/Base event service on managers. Detection is reported via a JP1 event or notification command.
The JP1/Base health check function can detect hangups in JP1/Base processes on the local host and on remote hosts. Detection is reported via a JP1 event.
By using the JP1/IM and JP1/Base health check functions in conjunction, you can quickly detect and respond to process errors in JP1/IM or in any instance of JP1/Base configured in the JP1/IM system.

#
The central scope service, IM Configuration Management service, and IM database service are not supported.

HiRDB
A database management system (DBMS) product for building a relational database scalable to business operations.

HP NNM
A generic name for a suite of integrated network management tools for managing the network configuration, performance, and failures.

IM Configuration Management
Functionality that lets you centrally manage the hierarchical structure and host settings of a system managed by JP1/IM, using the configuration management features of JP1/IM - Manager accessed from IM Configuration Management - View. By using IM Configuration Management, you can check JP1/Base service activity information and manage the status of the JP1/Base profiles on each host.
See also configuration management.

IM Configuration Management database
A database used by JP1/IM - Manager when implementing IM Configuration Management.

IM database
A database provided by JP1/IM - Manager. IM database is a generic term for the IM Configuration Management database and the integrated monitoring database.
See also IM Configuration Management database and integrated monitoring database.

incident
A single occurrence of an event that can lower the quality of an IT service or impede normal system operation.

individual condition
A status change condition defined for a specific monitoring object in the JP1/IM Central Scope.
See also status change condition.

initial status
The status when the JP1/IM Central Scope has no information about the status of a monitoring node in the monitoring tree.
See also status.

integrated monitoring database
A database provided by JP1/IM - Manager for use with the Central Console functionality.

JP1 common definition information
See common definition information.

JP1 event
Information for managing events occurring in the system within the JP1 framework.
The information recorded in a JP1 event is categorized by attribute as follows:
  • Basic attributes
    Held by all JP1 events.
    The basic attribute name for an event ID, for example, is written as B.ID (or simply ID).
  • Extended attributes
    Attributes that are optionally set by the program that issued the JP1 event. An extended attribute consists of the following common information and program-specific information:
    - Common information (extended attribute information in a standard format for all JP1 events)
    - Program-specific information (other information in a format specific to the program issuing the event)
    The extended attribute name for an event level, for example, is written as E.SEVERITY (or simply SEVERITY).
JP1 events are managed by the JP1/Base event service. Events generated in the system are recorded in a database as JP1 events.

JP1/AJS
A program for running jobs automatically.
Using JP1/AJS, you can execute processing in order according to a set schedule, or initiate processing when a specific event occurs.

JP1/Base
A program that provides the core functionality of JP1/IM.
JP1/Base carries out processing such as the sending and receiving of JP1 events, user management, and startup control. It also serves as the agent in a JP1/IM system.
JP1/Base is a prerequisite program for JP1/IM - Manager.

JP1/IM - Central Console
A feature of JP1/IM - Manager that provides the manager functionality of the Central Console. JP1/IM - Central Console oversees the entire system by centrally managing events in the system as JP1 events.
See also Central Console.

JP1/IM - Central Scope
A feature of JP1/IM - Manager that provides the manager functionality of the Central Scope. JP1/IM - Central Scope enables objective-oriented system monitoring matched to the requirements of the system administrator.
See also Central Scope.

JP1/IM - Manager
A program that enables integrated system management by providing centralized monitoring and operation across all system resources.
JP1/IM - Manager consists of three components: the Central Console, the Central Scope, and IM Configuration Management.

JP1/IM - Rule Operation
A program that supports rapid failure recovery by predefining recovery procedures or rules for the errors that may occur in the system, and executing them automatically.

JP1/IM - View
A GUI program that provides the viewer functionality for realizing integrated system management in JP1/IM.
The same JP1/IM - View is used with both JP1/IM - Manager and JP1/IM - Rule Operation. It can be connected to either program as required, for monitoring and managing the system.
This manual does not cover the use of JP1/IM - View connected to JP1/IM - Rule Operation.
See also viewer.

JP1/SES event
An event that was output by an obsolete JP1 product or by a product that does not support JP1 event output. JP1/SES events have basic attributes only (whereas JP1 events also have extended attributes).

JP1/Software Distribution
A generic name for a system that performs software distribution and client management as batch operations over a network.

jp1hosts information
Host information that associates JP1-specific host names with IP addresses.
This information can be used for customizing JP1 communication procedures in an environment with inter-connected networks, for example. jp1hosts information is managed by JP1/Base and is used by programs such as JP1/Base, JP1/IM, and JP1/AJS.
When jp1hosts information has been defined, the settings take precedence in JP1 communication over the OS hosts file settings. This allows you to associate host names and IP addresses differently from the OS settings, specifically for JP1 communication.

logical host
A logical server that provides the JP1 execution environment for running JP1 in a cluster system. If a failure occurs, a failover between logical hosts takes place.
Each logical host has a logical IP address and a shared disk, which are inherited at failover. A logical host consists of JP1 programs and other applications which run using the logical IP address and the shared disk.
At failover, the secondary node takes over the logical IP address and shared disk, and JP1 continues running. Thus, even if the physical server running JP1 is switched, other hosts can access the server using the same IP address and it appears that one host is operating continuously.

manager
A program whose role is to manage other programs or a host whose role is to manage other hosts in the JP1/IM system.
In the JP1/IM system, JP1/IM - Manager serves as the manager program, and manages the agent program JP1/Base.
The managers run JP1/Base, which provides the core functionality, and JP1/IM - Manager.

memo entry setting function
When you use the integrated monitoring database, this functionality allows users to set additional information about a JP1 event displayed in the Event Console window.

monitoring group
A group of monitoring objects in the JP1/IM Central Scope, or an icon in the Monitoring Tree window representing a group of monitoring objects.
Monitoring groups can be tailored to objectives. For example, you can define a job group or host group, depending on what you want to monitor.
The status of a monitoring group changes according to the highest severity among the statuses passed from the lower-level monitoring objects and groups it contains, or according to the conditions defined in a status change condition.

monitoring node
A generic name for any monitoring object or monitoring group that is part of a monitoring tree in the JP1/IM Central Scope.
See also monitoring object and monitoring group.

monitoring object
An object that you monitor using the JP1/IM Central Scope, or an icon in the Monitoring Tree window showing the status of an object being monitored.
When the Central Scope receives a JP1 event from an object being monitored, the event is judged using a status change condition, and the status of the monitoring object is displayed accordingly. (For example, a status change condition might set the status to Emergency on receipt of a JP1 event of Emergency level.) This allows you to manage the status of the various operations and resources being monitored in the system.

monitoring status
An attribute that determines whether to monitor the status of a monitoring node in the JP1/IM Central Scope.
There are two monitoring statuses: Monitor and Do not monitor.
When Monitor is set for a node, that node will react to any change in the status of whatever it is monitoring. In the case of a monitoring object, its status changes on receipt of a JP1 event that matches the monitoring conditions defined in a status change condition. In the case of a monitoring group, its status changes according to the highest severity among the statuses passed from its lower-level monitoring objects and groups (any status change in a monitoring node is always passed to the higher-level node), or according to the conditions defined in a status change condition. In JP1/IM - View, icons are color-coded to show the status of each monitoring node.
When Do not monitor is set for a node, its status does not change regardless of any JP1 event received from the job or host being monitored, or any status passed from a lower-level node. In JP1/IM - View, the icons of Do not monitor nodes are grayed out. You can set Do not monitor for a node when you need to maintain the resource it is monitoring, or when an automatically generated node does not need to be monitored.

monitoring tree
Functionality provided by the JP1/IM Central Scope for managing the objects being monitored in the system in form of a tree, drawn according to the viewpoints required by the system administrator. Monitoring tree may also refer to the Monitoring Tree window in JP1/IM - View which provides this functionality.
See also Central Scope.

node switching system
See cluster system.

non-consolidation event
See consolidated display of repeated events.

pass conditions
A set of conditions for JP1 events that you want to display (acquire). A pass condition can be specified in an event acquisition filter, view filter, severe events filter, event receiver filter, or event search.

physical host
A physical server configured in a cluster system in which JP1 operates. The term physical host is used in contrast with logical host (a logical server that can be failed over independently of the physical servers).

scroll buffer
An area of memory used by JP1/IM - View to store JP1 events extracted from the event buffer of JP1/IM - Manager.
A scroll buffer is kept for each of the Monitor Events page, Severe Events page, and Search Events page.
The JP1 events that JP1/IM - View displays on each page is determined by the contents of the scroll buffer for that page.
JP1 events are stored in the scroll buffer of the Monitor Events page, Severe Events page when:
  • JP1/IM - View starts#
  • The page is automatically refreshed#
  • The user selects Refresh in a menu or the toolbar
#: If Apply is selected for Automatic refresh in the Preferences window.
At the above times, JP1/IM - View communicates with JP1/IM - Manager as long as unacquired events are present in the event buffer. The number of events acquired in one transmission is determined by the value set in Num. of events to acquire at update in the Preferences window.
JP1 events are stored in the scroll buffer of the Search Events page when a user runs an event search.
The number of events acquired in one search is determined by the value set in Num. of events to acquire in 1 search in the Preferences window. To display the events that could not be acquired in one search, click Search for Next Event.

severe events filter
A filter that defines the severe events to be displayed in the Severe Events page of the Event Console window.
A severe event is a particularly important JP1 event that needs to be addressed, such as a failure of some sort. JP1/IM provides a Severe Events page so that users can reliably detect and deal with every severe event. On this page, as well as listing up only severe events, you can also manage the response status of each one.

severity level changing function
A function that lets users freely change the event level of a JP1 event, so that JP1 events can be managed in accordance with the system's operating environment.

status
The status of a resource being managed by a monitoring node in the JP1/IM Central Scope.
A monitoring node can have any of the following statuses: Emergency, Alert, Critical, Error, Warning, Normal, Debug, or Initial. Initial status means that the Central Scope does not yet have any information about the status of the resource being monitored.
For example, if a failure occurs and the node issues a JP1 event of Emergency level, the Central Scope will manage the event according to the status of the monitoring node.

status change condition
A condition that determines when to change the status of a monitoring object or monitoring group in the JP1/IM Central Scope.
  • Status change condition for a monitoring object
    Defines the types of JP1 events in the job or resource being monitored that will cause the monitoring object to change status. A status change condition for a monitoring object consists of one or more common conditions and individual conditions, and the resulting status when the status change condition is satisfied.
    A common condition is one that applies to all monitoring objects of the same type. For example, an event ID indicating that a job has ended abnormally is used for all monitoring objects that monitor jobs. A condition of this nature is defined as a common condition.
    An individual condition is one whose value is specific to the monitoring object concerned. For example, an individual condition might identify what is being monitored by a value such as the name of the job or the name of the host that executes the job. Conditions of this nature are defined as individual conditions. In the case of a system-monitoring object, the same attribute as specified in the basic information of the monitoring object is defined in the individual condition contained in a status change condition.
  • Status change condition for a monitoring group
    Defines the status of a lower-level node that will cause the monitoring group to change status. A status change condition for a monitoring group consists of a child node status, a comparison condition, and the resulting status when the status change condition is satisfied.
    Child node status refers to the status of a monitoring node at the next level below (immediately under) the monitoring group. When the child node status is set as Alert, for example, applicable statuses will include Emergency, which has higher priority than Alert.
    The comparison condition calculates lower-level nodes whose status has changed to the defined child node status, by a percentage or a count. The former is calculated as the number of child nodes in the specified status, as a percentage (%) of the total number of child nodes in the monitoring group. The latter is the number of child nodes in the specified status.

status monitoring
Monitoring for abnormal termination of an automated action. Status monitoring is able to detect and notify the user of any abnormally ended automated action whose status has changed to Fail, Error, or Error (Miss).

system information management
A structure for realizing integrated management of a system by centrally managing information about the system's myriad resources.

system-monitoring object
A monitoring object provided by the JP1/IM Central Scope.
Each system-monitoring object contains predefined basic settings for monitoring a particular product in the JP1 series. The use of such objects facilitates environment setup.
See also monitoring object.

Tool Launcher window
A JP1/IM - View window for registering and launching applications of the user's choice.
By registering applications needed for job processing in the Tool Launcher window, you can integrate operations under JP1/IM - View in running your JP1/IM system.
The Tool Launcher window has preset links for launching the GUI of products in the JP1 series.

variable binding
A variable binding of an SNMP trap. When a SNMP trap is converted into a JP1 event in JP1/Base, the variable bindings are read into the program-specific information contained in the extended attributes of the JP1 event.
As basic information, an SNMP trap indicates the source program (enterprise name) and the trap type (generic or specific). In addition, when detailed trap-specific information needs to be included, variable bindings (also written as VarBind) are appended to the SNMP trap when it is issued.
A variable binding contains an object identifier (OID) and data.
For details on SNMP traps, see RFC1157 and other network-related documentation. For details on the information contained in the variable bindings, see the manual for the specific program that issues SNMP traps.

view filter
A filter that sets conditions about the JP1 events to be displayed in the Event Console window.
Use a view filter when you want to temporarily restrict an event listing to specific JP1 events only.

viewer
A GUI program that provides purpose-built windows for integrated system management in JP1/IM. Viewer may also refer to the host running the GUI program.
The viewer connects to the Central Console, Central Scope, IM Configuration Management, system information management, and rule operation manager to perform system monitoring and management tasks.

virtual root node
Appears only when the monitoring range settings are enabled for the monitoring tree.
Unlike a monitoring object or monitoring group, the information in a virtual root node cannot be edited (in the Properties window). Neither can you change the node status or perform any other direct operations on the virtual root node. (Its status changes accordingly when the status of a monitoring node below it changes, but you cannot change the virtual root node status directly. To change its status, you must change the status of a lower-level monitoring node.)

Visual Icon
An icon displayed in the JP1/IM Central Scope which can be any size and based on any image. A visual icon is set as an attribute of a monitoring node. Because a visual icon can be any size, this feature offers the user a greater degree of freedom when creating monitoring windows. Visual Icon is displayed only in map view and in the Visual Monitoring window.

visual monitoring
Functionality provided by the JP1/IM Central Scope for displaying the objects in the system that need to be monitored particularly closely as icons arranged on a map, organizational chart, or other image. Visual monitoring may also refer to the Visual Monitoring window in JP1/IM - View which provides the map view functionality.
See also Central Scope.

Web page
A generic name for the GUI provided by another product and viewed in a Web browser (refers to the Web-based JP1/IM - View in the JP1/IM context).

Web-based JP1/IM - View
A light version of JP1/IM - View, forming part of JP1/IM - Manager (JP1/IM - Central Console). The program has a number of functional limitations, such as not being able to open the Tool Launcher window or Execute Command window. To use the Web-based JP1/IM - View, in addition to a Web browser, the Java Runtime Environment (JRE) and its accompanying plug-ins are required on the viewer. For details, see the Release Notes for JP1/IM - Manager. A Web server is required on the manager.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.