Preface

This manual describes the functionality and records of JP1/Performance Management - Agent Option for Enterprise Applications.

Organization of this preface

Intended readers
Organization of this manual
Conventions: Diagrams
Conventions: Fonts and symbols
Conventions: Version numbers

■ Intended readers

This manual is intended for the following readers:

Users who wish to learn about the features provided by JP1/Performance Management - Agent Option for Enterprise Applications and about the records it collects.
Users who wish to design and run systems that use JP1/Performance Management to collect SAP R/3 performance data.

It is assumed that the reader is familiar with SAP R/3.

For details about how to configure and use systems that utilize JP1/Performance Management, we recommend that you also use the following manuals:

Performance Management: Getting Started (Operation and Performance Management)
JP1/Performance Management Planning and Configuration Guide
JP1/Performance Management User's Guide
JP1/Performance Management Reference

To Page Top

■ Organization of this manual

This manual is organized into the chapters listed below. The manual applies to all operating systems (OSs). Any information unique to a particular OS is so indicated.

Chapter 1: Overview of PFM - Agent for Enterprise Applications: This chapter provides an overview of PFM - Agent for Enterprise Applications, including a description of what you can do with the program.
Chapter 2: Performance Monitoring: This chapter describes performance monitoring using PFM - Agent for Enterprise Applications.
Chapter 3: Installation and Setup: This chapter explains how to install and set up PFM - Agent for Enterprise Applications.
Chapter 4: Operation in a Cluster System: This chapter describes the installation and setup of PFM - Agent for Enterprise Applications in a cluster system and the general operating procedures when PFM - Agent for Enterprise Applications is operated in a cluster system.
Chapter 5: Extracting System Log Information: This chapter explains how to use PFM - Agent for Enterprise Applications to extract system log information.
Chapter 6: Extracting CCMS Alert Information: This chapter explains how to use PFM - Agent for Enterprise Applications to extract CCMS alert information.
Chapter 7: Collecting Monitor Information: This chapter explains how to use PFM - Agent for Enterprise Applications to collect an SAP system's monitor information.
Chapter 8: Notes on Operating: This chapter describes the notes about the operations of PFM - Agent for Enterprise Applications.
Chapter 9: Monitoring Template: This chapter describes the monitoring template for PFM - Agent for Enterprise Applications.
Chapter 10: Records: This chapter describes the records for PFM - Agent for Enterprise Applications.
Chapter 11: Commands: This chapter describes the commands provided by PFM - Agent for Enterprise Applications.
Chapter 12: Messages: This chapter describes the format of the PFM - Agent for Enterprise Applications messages, lists the locations to which messages are output, shows which messages are output to syslog and the Windows event log, and describes the messages in detail.
Chapter 13: Error Handling Procedures: This chapter describes the actions to be taken for errors that might occur during operation, focusing on PFM - Agent.

To Page Top

■ Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

To Page Top

■ 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.`

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.
`{` `}`	One of the items enclosed in curly brackets and separated by a vertical bar must be specified.
\|	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 for mathematical expressions

This manual uses the following symbols in mathematical expressions:

Symbol	Meaning
x	Multiplication sign
/	Division sign

To Page Top

■ 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.

To Page Top