Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/IT Service Level Management Description, User's Guide, Reference and Operator's Guide


E. Glossary

access logs

Information about the requests and responses associated with a monitored target in ITSLM.

active server

Among the servers running in a cluster system, the server that is executing the business operations.

active system

A system that is initially started as an active server within a cluster system. Even if an active server becomes a standby server due to failover, this designation does not change.

All Web Access

A monitored target in ITSLM. All Web Access enables you to monitor average response time, throughput, and error rate for all requests and responses in the monitored service.

authentication server

A server that manages the access permissions of JP1 users.

One authentication server is required in each user authentication block. The administrator uses this server for centralized management of all JP1 users. When ITSLM is installed, the administrator must register JP1 user names on this server.

availability information

Data that is the result of monitoring whether a monitored service is running or has stopped.

availability monitoring

A monitoring method for determining availability, mean time to recovery (MTTR), mean time between failures (MTBF), and similar measures based on the availability information of the monitored service. Availability monitoring can be performed when PFM - Agent for Service Response is being used.

baseline

The metric indicating normative service performance and which serves as the basis for out-of-range value detection. It is created by averaging the accumulated historical service performance. In out-of-range value detection, when service performance is detected that veers substantially from this baseline, it is detected as a departure from the usual service performance.

BNF notation

A character-based meta-language for defining the syntax of program source code, networks, protocols, and other languages intended for computers.

business group

The unit around which Performance Management organizes the hosts to be monitored. Users assigned to a business group can view information collected by the monitoring agents monitoring the hosts in the business group.

cluster software

The software that provides overall management of a cluster system. The cluster software monitors whether the system is running normally, and when a problem is detected it executes failover to prevent operations from coming to a stop.

cluster system

A system configured as multiple linked server systems, designed to continue operation even if one system fails. The term failover describes the case where a normal system takes over processing that was being executed by a system where a failure occurred. If a failure occurs in the server currently executing applications (primary node), a standby server (secondary node) takes over and continues processing the applications. Therefore, a cluster system is also referred to as a node switching system.

The term cluster system can also mean load balancing based on parallel processing. In this manual, however, cluster system refers only to a system able to provide failover capability to prevent disruption of business operations.

configuration information

Information that is required to link to Performance Management, including information about the business groups to be monitored and the monitoring items for system performance monitoring and availability monitoring.

drilldown

A method of data analysis that proceeds from summary data into the details by expanding lower levels of the data, one level at a time.

event

Information indicating the occurrence of circumstances constituting an error or warning. If availability monitoring is being performed (when linked to Performance Management), an event also reports information that is normally relevant when a monitored service has recovered from a stop.

failover

In a cluster system, the process of a standby server taking over processing from a running server in the event of a failure in order to prevent interruption of the business operations.

ITSLM - Manager

A program that aggregates and analyzes HTTP packets collected by ITSLM - UR in order to monitor the status of services.

ITSLM - Manager is accessed in order to check the status of services being monitored.

ITSLM - UR

A program that runs on each switch, collecting HTTP packets of the requests and responses exchanged through the switch between the users of a service and the server that provides the service.

The collected results are sent to ITSLM - Manager.

JP1/Base

A program that is a prerequisite for ITSLM - Manager. JP1/Base provides event service functionality, and can manage the start order of services as well as send and receive JP1 events.

It is also used as an authentication server in ITSLM.

JP1 event

Information used in JP1 to manage events that occur in the system.

JP1 events use the following attributes to record events:

Basic attributes

All JP1 events have basic attributes.

For example, when attribute names are specified, B.ID (or just ID) is specified for the event ID.

Extended attributes

A program that issues JP1 events can specify any desired extended attributes. The extended attributes consist of the following common information and program-specific information:

[Figure] Common information (extended attribute information whose format is standardized according to the JP1 event)

[Figure] Program-specific information (information other than the common information whose format is specific to a program)

For example, when attribute names are specified, E.SEVERITY (or just SEVERITY) is specified for the severity.

The JP1 events are managed by the event service of JP1/Base. Events that occur in the system are recorded in the database as JP1 events.

JP1/IM

A program that consists of JP1/IM - Manager and JP1/IM - View.

JP1/IM - Manager is used to achieve integrated management of systems by providing for centralized monitoring and operation of the entire system.

JP1/IM - View provides the viewer function for enabling integrated management of systems in JP1/IM.

JP1 permission level

The representation of the types of operations a JP1 user is permitted to perform on management objects (resources). Operations are set depending on the type of management object (resource), such as job, jobnet, or event. The access permissions of JP1 users are managed in a format that combines several types of management objects (resources) and their associated operations.

ITSLM applies two JP1 permission levels, JP1_ITSLM_Admin (service group administrator) and JP1_ITSLM_User (service user).

JP1 user

A designation for one who uses ITSLM. The JP1 user is registered on the authentication server, which manages the user's access permissions to a remote host. The JP1 user name might differ from the user account registered in the OS.

logical host

In a cluster system, the logical server for purposes of failover. A logical host consists of three elements: services, a shared disk, and a logical IP address. In the case of ITSLM, the services are the Windows services that comprise ITSLM.

monitoring agent

A service in PFM -Agent or PFM - RM for collecting the system performance of hosts and middleware.

monitoring item

An item that is monitored in ITSLM for the purpose of maintaining service levels. In the case of service performance monitoring, the monitoring items are average response time, throughput, and error rate. In the case of system performance monitoring, it is the information collected by monitoring agents. In the case of availability monitoring, it is the information collected by PFM - Agent for Service Response.

Note that Performance Management must be linked in order to carry out system performance and availability monitoring.

out-of-range value detection

A monitoring method that detects indications of problems when the performance of a monitored service differs substantially from the usual service performance.

PDCA cycle

An approach to facilitating management of operations, employing four stages: Plan, Do, Check, and Act.

performance data

The data that used in ITSLM monitoring, consisting of the following:

  • Service performance data collected by ITSLM - UR

  • System performance data collected by monitoring agents (when linked to Performance Management)

  • Availability information data collected by PFM - Agent for Service Response (when linked to Performance Management)

PFM - Agent

One of the program products comprising Performance Management. PFM - Agent is a monitoring agent that is placed on the same host as a monitored target in order to monitor the performance information of systems such as hosts or middleware.

PFM - Agent has the following functions:

  • Monitoring of the performance of the monitored target

  • Collection and recording of data from the monitored target

Within PFM - Agent there are program products targeted at the application, database, or OS to be monitored.

PFM - Agent for Service Response

One of the program products comprising Performance Management. PFM - Agent for Service Response is a program that is installed on a host that is to be monitored; it monitors the availability information of monitored services.

PFM - Base

One of the program products comprising Performance Management. PFM - Base provides the core functions for achieving operation monitoring by Performance Management. PFM - Base is required in order to run PFM - Agent and PFM - RM.

PFM - Manager

One of the program products comprising Performance Management. PFM - Manager manages the Performance Management program products.

PFM - Manager receives requests from ITSLM - Manager, and then sends configuration information collected by the monitoring agent or PFM - Agent for Service Response to ITSLM - Manager.

PFM - RM

One of the program products comprising Performance Management. The PFM - RM program is a monitoring agent that is installed on hosts other than the host being monitored in order to carry out remote monitoring of performance information on systems such as hosts and middleware.

PFM - RM provides the following functions:

  • Monitoring of the performance of the monitored target

  • Collection and recording of data from the monitored target

Within PFM - RM there are program products targeted at the application, database, or OS to be monitored.

PFM - Web Console

One of the program products comprising Performance Management. PFM - Web Console provides capabilities for centralized monitoring of the Performance Management system in a Web browser.

RD area

A data storage area for a database. When the ITSLM setup process is run at the time of installation, RD areas are created in folders specified by an absolute path. In ITSLM, RD areas are used to provide data management while ITSLM is operating.

record

A format for storing data about system performance (performance data) collected by the monitoring agent when linked to Performance Management. The record type varies according to each database constituting the Store database.

sensitivity

A setting that determines the ease of detection by out-of-range value detection. The higher the sensitivity, the more likely detection becomes. The sensitivity is set in the Settings window.

service

A part of a business system.

service group

A unit for managing monitored targets for customers (for example, companies) that have outsourced their business systems. A service group is equivalent to a JP1 resource group in JP1/Base.

service group administrator

A user whose JP1 permission level is set to JP1_ITSLM_Admin.

A service group administrator can view service group information and information on monitored services within the service group, and is also able to set information in a monitored service.

service performance

Service performance refers to data resulting from monitoring average response time, throughput, and error rate, which are monitoring items.

service performance monitoring

A monitoring method for determining whether the performance of a monitored service has exceeded the values set for out-of-range value detection and SLO monitoring.

service user

A user whose JP1 permission level is set to JP1_ITSLM_User.

A service user can view service group information as well as information about the monitored services within the service group.

SLA (Service Level Agreement)

A contractual arrangement between an outsourcing company and an outsourced contractor that guarantees the quality of the service to be provided.

SLO (Service Level Objective)

A specific evaluation metric that is set for a monitoring item in order to comply with an SLA.

standby server

A server running in a cluster system that is waiting to take over operations in the event of a failure of the active server.

standby system

A system that is started initially as a reserve server in a cluster system. Even if a standby server becomes the active server due to failover, this designation does not change.

system definition file

A definition file (properties file) that specifies the details of how ITSLM functions. Host names, port numbers, and similar information are specified in the system definition file.

system performance

The monitoring results collected by monitoring agents by applying monitoring items to hosts and middleware when linked to Performance Management. System performance corresponds to performance data in Performance Management.

system performance monitoring

A monitoring method for monitoring whether the performance of a system running a monitored service has exceeded the values for out-of-range value detection or SLO monitoring that were set in ITSLM.

threshold value monitoring

A monitoring method for detecting if the performance of a monitored service has exceeded a set threshold value.

trend monitoring

A monitoring method that calculates trends in the performance of monitored services in order to detect in advance that a service performance threshold value is likely to be exceeded if a detected trend continues.

URI (Uniform Resource Identifier)

An identifier that points to an information resource on the Internet. The URI indicates the location and name of the information resource.

Web access

A monitored target in ITSLM that represents a combination of requests and responses.

Web transaction

A monitored target in ITSLM that represents a collection of business operations comprising multiple requests and responses included in the monitored service. The collection of operations is determined based on the URIs of the requests and responses, as well as the query and cookie information included in the URIs.