Contents

• Notices

• Summary of amendments

• Preface

• Part 1: Overview

  • 1. Overview of Performance Management

    • 1.1 Need for operation monitoring in an enterprise system

      • 1.1.1 Why is operation monitoring necessary?

      • 1.1.2 Using Performance Management for operation monitoring and the performance data that can be collected

      • 1.1.3 Products provided by Performance Management

    • 1.2 Features of Performance Management

      • 1.2.1 Centralized monitoring of the operating status of large and complex enterprise systems

      • 1.2.2 Use in mission-critical systems that demand high reliability and availability

      • 1.2.3 Easily create and operate an operations monitoring system

      • 1.2.4 Select a suitable monitoring method

      • 1.2.5 Set a range that can be monitored by each user

• Part 2: Design

  • 2. Design of Operation Monitoring Systems that Use Performance Management

    • 2.1 General procedure for configuring an operation monitoring system and the range supported by Performance Management

    • 2.2 Performance Management: from design to operation

    • 2.3 Designing the configuration of an operation monitoring system

      • 2.3.1 Examining the system configuration of Performance Management

      • 2.3.2 Examining the availability of monitoring managers

      • 2.3.3 Examining cluster configurations

      • 2.3.4 Examining network configurations

    • 2.4 Designing the operation of an operation monitoring system

      • 2.4.1 Examining user management methods and the use of business groups

      • 2.4.2 Examining monitoring agent management methods

      • 2.4.3 Examining the items to be monitored

      • 2.4.4 Examining alarm table binding methods

      • 2.4.5 Examining data backup methods

      • 2.4.6 Examining Store database storage methods

      • 2.4.7 Examining measures to take when the operation monitoring system itself malfunctions

      • 2.4.8 Estimating the required hard drive space for Performance Management

    • 2.5 Design of the operation of large systems

      • 2.5.1 Important considerations for configuring JP1/Performance Management in large systems

      • 2.5.2 Important considerations for operating JP1/Performance Management in large systems

  • 3. Performance Management Functions

    • 3.1 Performance Management services

      • 3.1.1 Overview of services

      • 3.1.2 Displaying and specifying services (the product name display function)

    • 3.2 Functions for collecting and managing performance data

      • 3.2.1 Performance data

      • 3.2.2 Flow of performance data collection

      • 3.2.3 Performance data management function and how to configure the function

      • 3.2.4 Summarizing the performance data

      • 3.2.5 Store database storage methods

      • 3.2.6 Functions specific to Store 2.0

      • 3.2.7 General procedure for installing Store version 2.0

    • 3.3 Functions for alerting the user when the system reaches a critical state

      • 3.3.1 Alarm event data

      • 3.3.2 Issuing alarm events

      • 3.3.3 Summarizing the alarm event data and the maximum number of records

      • 3.3.4 Triggers for sending alarms

      • 3.3.5 Considerations for monitoring the alarm status in units of instances

    • 3.4 Functions for detecting faults in the operation monitoring system itself

      • 3.4.1 Overview of the health check function and the status management function

      • 3.4.2 Using the monitoring results obtained from the health check function

      • 3.4.3 Using the monitoring results obtained from the status management function

    • 3.5 Functions for automatically restarting operation monitoring system services

    • 3.6 Function for obtaining a list of settings

    • 3.7 Monitoring console functions of Performance Management

      • 3.7.1 Monitoring agents in an Agents tree

      • 3.7.2 Monitoring agents using logs

    • 3.8 Functions monitored in a business group

    • 3.9 Performance Management commands

      • 3.9.1 Commands used to set up the system

      • 3.9.2 Commands used to operate the system

      • 3.9.3 Commands used to start and stop the system

      • 3.9.4 Settings to limit the host subject to command processing

    • 3.10 Notes

      • 3.10.1 Notes on the time setting of a monitoring target machine

      • 3.10.2 Notes on the Japanese-language environment

      • 3.10.3 Notes on environments in which multiple languages coexist

      • 3.10.4 Notes on temporary files

      • 3.10.5 Notes on using Windows

      • 3.10.6 Notes on displaying real-time reports

• Part 3: Configuration

  • 4. Installation and Setup (in Windows)

    • 4.1 Installation and setup

      • 4.1.1 Before installation and setup

      • 4.1.2 Process flow for installation and setup

      • 4.1.3 Installation procedures

      • 4.1.4 PFM - Manager setup procedure

      • 4.1.5 PFM - Web Console setup procedure

      • 4.1.6 Configuring a web browser to use the monitoring console

    • 4.2 Uninstallation and unsetup

      • 4.2.1 Before uninstallation and unsetup

      • 4.2.2 Uninstallation procedures

      • 4.2.3 Deleting service information

    • 4.3 Specifying and changing the Performance Management system configuration

      • 4.3.1 Specifying and changing the network configuration

      • 4.3.2 Changing the PFM - Manager for the connection destination

      • 4.3.3 Specifying and changing the monitoring host name in a Performance Management system

      • 4.3.4 Changing the monitoring host name of PFM - Manager

      • 4.3.5 Changing the monitoring host name of PFM - Agent or PFM - RM

      • 4.3.6 Notes on changing monitoring host names

      • 4.3.7 Optional PFM - Agent-specific procedure to be performed when the monitoring host name is changed

      • 4.3.8 Changing the physical host name after operation has started

      • 4.3.9 Changing the physical host name of PFM - Manager

      • 4.3.10 Changing the physical host name of PFM - Agent or PFM - RM

      • 4.3.11 Changing the physical host name of the monitoring target of PFM - RM

      • 4.3.12 Changing the physical host name of PFM - Web Console

      • 4.3.13 Optional PFM - Agent-specific procedure to be performed when the physical host name is changed

      • 4.3.14 Changing the storage directory for bookmark definition information

      • 4.3.15 Changing the settings for encrypted communication between a web browser and the monitoring console server

      • 4.3.16 Changing the port number settings

    • 4.4 Changing the Performance Management operation method

      • 4.4.1 Setting the size of the log file for the common message log

      • 4.4.2 Changing the storage location of event data

      • 4.4.3 Specifying communication line disconnection settings

      • 4.4.4 Configuring the functionality for binding multiple alarm tables

      • 4.4.5 Changing IP address settings

      • 4.4.6 About the operation settings of PFM - Manager, PFM - Agent, and PFM - RM

      • 4.4.7 Changing PFM - Web Console settings

      • 4.4.8 Setup and unsetup of Store 2.0

      • 4.4.9 Enhancing file permissions

      • 4.4.10 Configuring the product name display function

      • 4.4.11 Configuring the function for outputting measurement values when alarms recover to the normal status

      • 4.4.12 Specifying the option for limiting remote operation of Agent hosts and the option for restricting viewing of service information from Agent hosts

      • 4.4.13 About changing the language environment

    • 4.5 Settings required to read manuals with a Web browser

      • 4.5.1 Setting procedure

      • 4.5.2 Reading manuals

  • 5. Installation and Setup (in UNIX)

    • 5.1 Installation and setup

      • 5.1.1 Before installation and setup

      • 5.1.2 Process flow for installation and setup

      • 5.1.3 Installation procedures

      • 5.1.4 PFM - Manager setup procedure

      • 5.1.5 PFM - Web Console setup procedure

      • 5.1.6 Configuring a Web browser to use the monitoring console

    • 5.2 Uninstallation and unsetup

      • 5.2.1 Before uninstallation and unsetup

      • 5.2.2 Uninstallation procedures

      • 5.2.3 Deleting service information

    • 5.3 Specifying and changing the Performance Management system configuration

      • 5.3.1 Specifying and changing the network configuration

      • 5.3.2 Changing the PFM - Manager for the connection destination

      • 5.3.3 Specifying and changing the monitoring host name in a Performance Management system

      • 5.3.4 Changing the monitoring host name of PFM - Manager

      • 5.3.5 Changing the monitoring host name of PFM - Agent or PFM - RM

      • 5.3.6 Notes on changing monitoring host names

      • 5.3.7 Optional PFM - Agent-specific procedure to be performed when the monitoring host name is changed

      • 5.3.8 Changing the physical host name of a server after operation has started

      • 5.3.9 Changing the physical host name of PFM - Manager

      • 5.3.10 Changing the physical host name of PFM - Agent or PFM - RM

      • 5.3.11 Changing the physical host name of the monitoring target of PFM - RM

      • 5.3.12 Changing the physical host name of PFM - Web Console

      • 5.3.13 Optional PFM - Agent-specific procedure to be performed when the monitoring host name is changed

      • 5.3.14 Changing the storage directory for bookmark definition information

      • 5.3.15 Changing the settings for encrypted communication between a web browser and the monitoring console server

      • 5.3.16 Changing the port number settings

    • 5.4 Changing the Performance Management operation method

      • 5.4.1 Setting the size of the log file for the common message log

      • 5.4.2 Changing the storage location of event data

      • 5.4.3 Specifying communication line disconnection settings

      • 5.4.4 Configuring the functionality for binding multiple alarm tables

      • 5.4.5 Changing IP address settings

      • 5.4.6 About the operation settings of PFM - Manager, PFM - Agent, and PFM - RM

      • 5.4.7 Changing PFM - Web Console settings

      • 5.4.8 Setup and unsetup of Store version 2.0

      • 5.4.9 Configuring the product name display function

      • 5.4.10 Configuring the function for outputting measurement values when alarms recover to the normal status

      • 5.4.11 Specifying the option for limiting remote operation of Agent hosts and the option for restricting viewing of service information from Agent hosts

      • 5.4.12 About changing the language environment

    • 5.5 Settings required to read manuals with a Web browser

      • 5.5.1 Setting procedure

      • 5.5.2 Reading manuals

• Appendixes

  • A. Limits

    • A.1 System configuration

    • A.2 Displaying PFM - Web Console

    • A.3 Store database size

    • A.4 Number limits for alarms and alarm tables

    • A.5 Maximum numbers of users and business groups that can be managed by Performance Management

    • A.6 Limits related to folder management

    • A.7 Limits related to monitoring of performance data

    • A.8 Limit to the actions that are associated with alarms

    • A.9 Recommended file size for the automatic bind settings file

  • B. Naming Rules

    • B.1 Naming rules for service IDs and service keys

    • B.2 Correspondence between the service names in Performance Management and in Windows

    • B.3 List of service keys for PFM - Agent version 08-11 or earlier (when the product name display function is enabled)

  • C. System Estimates

    • C.1 Memory requirements

    • C.2 Disk space requirements

    • C.3 Disk space requirements when running on a cluster system

    • C.4 Disk space requirements when executing the jpctool db backup and jpctool db dump commands on the Store database

    • C.5 Disk space requirements when using report cache files

    • C.6 Estimates and settings when multiple PFM - Agents and PFM - RMs are connected to PFM - Manager

    • C.7 Estimating the memory size when the report display function or the monitoring suspension function is used

    • C.8 Estimating the amount of data flowing over a network

  • D. List of System Resources for Which Kernel Parameters Need to Be Adjusted

  • E. Checking Version Information

    • E.1 How to check the version information of PFM - Manager

    • E.2 How to check the version information of PFM - Web Console

    • E.3 How to check the version information of PFM - Base

    • E.4 How to check the version information of PFM - Agent and PFM - RM

  • F. Migration Steps and Notes on Migration

    • F.1 Changing the product configuration for Performance Management

    • F.2 Relation between 08-00 or later of PFM - Web Console and 07-00 or earlier of PFM - View

    • F.3 Installation order during migration from 07-10 or earlier to 08-00 or later

    • F.4 Upgrading Performance Management programs

    • F.5 Notes on migration (version 11-00 or later)

    • F.6 Notes on migration (version 10-00 or later)

    • F.7 Notes on migration (version 09-00 or later)

    • F.8 Notes on migration (version 08-00 or later)

    • F.9 Performing an unsetup of NNM linkage

  • G. Version Compatibility

    • G.1 Version compatibility of the system configuration

    • G.2 Compatibility among data model versions

    • G.3 Displaying data models in PFM - Web Console

    • G.4 Version compatibility of system configurations when operating PFM - RM

  • H. Outputting Action Log Data

    • H.1 Types of events output to the action log

    • H.2 Format for saving action log files

    • H.3 Format of output action log data

    • H.4 Settings for outputting action log data

  • I. Health Check Agent

    • I.1 Records

    • I.2 Overview of monitoring template

    • I.3 Monitoring template (alarm)

    • I.4 Monitoring template (report)

  • J. Version Changes

    • J.1 Changes in version 11-50

    • J.2 Changes in version 11-10

    • J.3 Changes in version 11-01

    • J.4 Changes in version 11-00

    • J.5 Changes in version 10-50

    • J.6 Changes in version 10-10

    • J.7 Changes in version 10-00

    • J.8 Changes in version 09-50

    • J.9 Changes in version 09-10

    • J.10 Changes in version 09-00

  • K. Reference Material for This Manual

    • K.1 Related publications

    • K.2 Conventions: Abbreviations for product names

    • K.3 Conventions: Acronyms

    • K.4 Conventions: Product names, service IDs, and service keys

    • K.5 Conventions: Folder path names in this manual

    • K.6 Conventions: KB, MB, GB, and TB

  • L. Glossary

• Index

To Page Top