Q. Glossary

Performance Management automatically executes an action when monitored data reaches a threshold. The following types of actions are available:

• Email transmission

• Command execution

• SNMP trap generation

• JP1 event generation

This is one of the PFM - Manager or PFM - Base services. This service executes an action.

Refers to PFM - RM, which collects performance data.

Information that defines the action that is to be taken or the event message that is issued when monitored data reaches a threshold.

A table summarizing one or more alarms that define the following types of information:

• Monitored object (process, TCP, Web service, for example)

• Monitored information (CPU usage, the number of bytes received in 1 second, for example)

• Monitored condition (threshold)

Binding means associating an alarm with an agent. When an alarm is bound, the user can be notified when the performance data collected by the agent reaches the threshold defined by the alarm.

A cluster system links together multiple server systems and operates them as a single system.

In this manual, cluster system refers to an HA cluster system unless otherwise specified.

See HA cluster system.

This is one of the PFM - Manager services. This service controls event delivery between services. It evaluates an alarm status, and when the threshold is exceeded, sends an alarm event and an agent event to both the Trap Generator service and PFM - Web Console.

Generally refers to the records and fields that each PFM - RM has. Data models are managed by version.

An ID assigned to each record of PFM - RM to indicate the database in which each record is stored. A database ID indicates the type of records that are stored in the database.

• PI: Indicates a database for storing records of the PI record type.

• PD: Indicates a database for storing records of the PD record type.

This is a report associated with a report or report field, and is used for displaying detailed information or related information about a report.

In server systems that comprise a cluster system, the node that is executing a job (the node on which the logical host is active).

A process of switching over the processing of the server that is executing jobs from the executing node to the standby node when an error occurs in a cluster system.

Individual operation information entries in a record. Each field serves as a monitoring item for Performance Management.

This is a 1-byte identifier indicating a function type of a Performance Management program, and is part of a service ID.

A cluster system for achieving high availability, designed to continue running even when an error occurs. When an error occurs on a server that is processing jobs, another server that has been on standby takes over job processing. In this way, jobs are not interrupted by an error and system availability is improved.

In this manual, cluster system refers to an HA cluster system unless otherwise specified.

A report that shows the status history of the monitored target.

In this manual, the term instance is used in the following ways:

• To indicate a recording format for records

  A record that is recorded on one line is referred to as a single-instance record, a record that is recorded on multiple lines is referred to as a multi-instance record, and each line in a record is referred to as an instance.

• To indicate the PFM - RM startup method

  When a single agent monitors targets on the same host, it is referred to as a single-instance agent. When multiple agents monitor targets on the same host, they are referred to as multi-instance agents. Each of these multi-instance agents is referred to as an instance.

This is an identifier that indicates a 1-byte control number used in internal processing, and that is part of a service ID.

A product that performs monitoring from the viewpoint of performance as experienced by the service users of a business system, and that supports service-level maintenance. Linkage with JP1/SLM can enhance monitoring of the operating status.

A period during which the consistency of the performance data collected into records can be guaranteed.

This is the logical server that becomes the executing environment for JP1 when it operates in a cluster system. When an error occurs, systems are switched on a logical host basis.

A logical host has its own IP address, and this IP address is inherited during a failover. Therefore, even when physical servers are switched because of an error, clients can use the same IP address to access the server, making it appear as though a single server is always running.

Management tools are various types of commands and GUI functions that are used to check service status and processing performance data. They can be used to perform the following types of operations:

• Displaying service configuration and status

• Saving and restoring performance data

• Exporting performance data to a text file

• Erasing performance data

This is one of the PFM - Manager services, and refers to PFM - Manager's main service.

This is one of the PFM - Manager services, and refers to the service that manages alarm events issued by each PFM - RM. The Master Store service uses a database for retaining event data.

Refers to a pre-defined alarm or report provided in PFM - RM. By using a monitoring template, you can easily prepare to monitor the operation status of PFM - RM without having to create complex definitions.

A record that is recorded on multiple lines. This record has a specific ODBC key field.

See Instance.

A PFM - Manager service that manages the service configuration information in the system.

Command execution method in which operator input required for command execution are provided by values in option specifications or in definition files.

Executing a command non-interactively saves work when configuring an operation monitoring system and can reduce user workload.

These fields display the primary keys that are necessary to use the data retrieved from records stored in the Store database on either PFM - Manager or PFM - Base. Some ODBC key fields are common to all records, while others are specific to individual records.

See Product Detail record type.

Operation status data of a resource collected from the monitored system.

A general term that refers to a group of software program products necessary for monitoring and analyzing performance-related problems of a system. Performance Management consists of the following five program products:

• PFM - Manager

• PFM - Web Console

• PFM - Base

• PFM - Agent

• PFM - RM

One of the program products comprising Performance Management. PFM - Agent is equivalent to a system monitoring function, and various types of PFM - Agents are available according to the application to be monitored, the database, and the OS. PFM - Agent has the following functions:

• Monitoring the monitored target

• Collecting and recording data from a monitored target

One of the program products comprising Performance Management. PFM - Base provides Performance Management with the core functions necessary for monitoring operations. PFM - Base is a prerequisite program product for running PFM - RM. PFM - Base has the following functions:

• Management tools such as various types of commands

• Common functions necessary for linking Performance Management to other systems

One of the program products comprising Performance Management. PFM - Manager is equivalent to the manager function and has the following functions:

• Management of the Performance Management program products

• Event management

Name that identifies a field stored in the Store database, and that is used to specify a field for a command, for example.

One of the program products in the Performance Management family. PFM - RM is responsible for system monitoring. Several types of PFM - RM are available, depending on the applications, database, and operating system to be monitored. PFM - RM provides the following features:

• Performance monitoring of target objects

• Collection and recording of data from monitored objects

Alias for the PFM - Manager name. The PFM - View name is a more intuitive name than the PFM - Manager name. For example, the PFM - Manager name INPUT_RECORD_TYPE becomes Record Type as a PFM - View name. The PFM - View name is used to specify a field in the GUI of PFM - Web Console, for example.

One of the program products comprising Performance Management. It provides Web application server functions for centrally monitoring the Performance Management system. PFM - Web Console has the following functions:

• GUI display

• Integrated monitoring and management functions

• Report definition and alarm definition

An environment specific to each server that makes up a cluster system. A physical host's environment is not inherited by another server during a failover.

This is a physical server on which a virtual environment operates, and it has various types of resources such as a CPU. Virtual machines on the same physical server share the physical server's resources.

See Product Interval record type.

This record type stores performance data that indicates the system status at a given point in time, such as detailed information about the process that is currently active. Use the PD record type when you want to know the system status at a given point in time, such as the following:

• The system's operation status

• The capacity of the file system currently being used

This is a one-byte identifier that indicates the program product of Performance Management to which the service of the applicable Performance Management program belongs, and that is part of a service ID.

This record type stores performance data for a given period of time (interval), such as the number of processes for 1 minute. Use the PI record type when you want to analyze changes or trends in the system status over time, such as the following:

• Trends in the number of system calls that occurred within a specified period of time

• Trends in the capacity of the file system being used

A report that indicates the current status of the monitored target.

A group of operation information entries categorized by their purpose. A monitoring agent collects operation information from each record. The types of records that can be collected vary depending on the agent program.

A PFM - RM service that collects performance data and evaluates the data according to the threshold values set in alarms.

A PFM - RM service that stores performance data in a database. A separate Remote Monitor Store service is provided with each PFM - Remote Monitor platform.

A report defines how performance data collected by PFM - RM is graphically displayed. It primarily defines the following types of information:

• Records to be displayed in a report

• Performance data display items

• Performance data display format (table, graph, and so on)

A unique ID assigned to a Performance Management program. When you use a command to check the system configuration of Performance Management, or when you back up the performance data of each agent, you need to execute the command by specifying the service ID of the Performance Management program. The service ID format varies depending on the settings of the product name display function. For details about the service ID format, see the chapter that explains the functions of Performance Management in the JP1/Performance Management Planning and Configuration Guide.

A record that is recorded on a single line. This record does not have a specific ODBC key field.

See Instance.

This is a status in which PFM - RM only has started. Even when the Master Manager service or Name Server service of PFM - Manager cannot be started because of an error, you can start PFM - RM by itself and collect performance data.

In server systems that comprise a cluster system, a standby node can assume the jobs that were being executed by the executing node when an error occurred on it.

This function manages the status of all services running on PFM - Manager and PFM - RM. Using the status management function, the system administrator can accurately assess the service startup or stoppage status on each host, and can therefore take the appropriate corrective actions quickly.

This database stores the performance data collected by Remote Monitor Collector service.

Name of the kernel component in the hypervisor that manages a system with logical partitioning feature.

Name of the communication and service component in the hypervisor that manages a system with logical partitioning feature.

This refers to a virtual machine that is provided by software and that uses virtual resources provided in the resources of a physical server.

See VMM.

Stands for Virtual Machine Manager, which is the kernel for controlling virtual machines.

This is the console for operating VMM.

This is the kernel portion of VMM.