Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference

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

2.1.4 Setting up PFM - Agent for Platform

This section explains the set up procedure needed for using PFM - Agent for Platform.

[Figure] indicates setup items that may be required depending on the usage environment or optional setup items that are used for changing the default settings.

Organization of this subsection
(1) Setting the LANG environment variable
(2) Registering PFM - Agent for Platform
(3) Network setup
(4) Changing the log file size
(5) Changing the performance data storage destination
(6) Setting up PFM - Manager for the connection destination of PFM - Agent for Platform
(7) Setting up the action log

(1) Setting the LANG environment variable

The following table shows a LANG environment variable that can be used on PFM - Agent for Platform.

Before setting LANG environment variables, you must check that the language environment to be set is correctly installed and configured. If it is not correctly installed and configured, characters may be garbled or definition data may be rewritten inappropriately.

Note:
The language used for the common message log is determined by the LANG environment variable that is set when a service is started or a command is executed. For that reason, character strings of more than one language code may coexist.

Table 2-3 LANG environment variable used on PFM - Agent for Platform

OS Language type LANG environment variable value
HP-UX, Solaris, AIX, Linux English C

(2) Registering PFM - Agent for Platform

To use PFM - Manager and PFM - Web Console to centrally manage PFM - Agent, you need to register PFM - Agent for Platform in PFM - Manager and PFM - Web Console.

When the version of PFM - Manager is 09-00 or later, you do not need to perform the procedure explained here, because PFM - Agent is automatically registered. However, you must manually register the PFM - Agent instances whose data model version is not provided in the PFM - Manager Release Notes. For details about data model versions for PFM - Agent for Platform, see I. Version Compatibility.

The following figure shows the flow for registering PFM - Agent.

Figure 2-4 PFM - Agent registration flow

[Figure]

Note
  • If you add the same version of PFM - Agent for Platform to a Performance Management system on which PFM - Agent for Platform information is already registered, you need not register PFM - Agent.
  • If the data model version of PFM - Agent for Platform is 3.0 or 4.0, setup for updating the data model version is not necessary.
  • When installing PFM - Agent for Platform of differing versions on different hosts, set up the older version first and then the new version.
  • When you install PFM - Agent on the same host as PFM - Manager, the jpcconf agent setup (jpcagtsetup) command is automatically executed. When the message KAVE05908-I New agent setup ended successfully. is output to the common message log, check the result. If the command was not executed correctly, re-execute it. For details about command execution, see the chapter on commands in the manual Job Management Partner 1/Performance Management Reference.

(a) Copying the PFM - Agent for Platform setup files

Copy the setup files located at the host on which PFM - Agent for Platform was installed to the host on which PFM - Manager and PFM - Web Console are installed. To copy the setup files:

  1. If PFM - Web Console is active, stop it.

  2. Copy the PFM - Agent setup files in the binary mode.
    The table below shows the file storage locations and copying destinations.

    Table 2-4 Setup files to be copied

    Copy destination PFM - Agent setup files
    PFM program name OS Copy destination directory
    PFM - Manager Windows PFM-Manager-installation-folder\setup\ /opt/jp1pc/setup/jpcagtuw.EXE
    UNIX /opt/jp1pc/setup/ /opt/jp1pc/setup/jpcagtuu.Z
    PFM - Web Console Windows PFM-Web-Console-installation-folder\setup\ /opt/jp1pc/setup/jpcagtuw.EXE
    UNIX /opt/jp1pcwebcon/setup/ /opt/jp1pc/setup/jpcagttu.Z

(b) Executing the setup command on the PFM - Manager host

In PFM - Manager, execute the following command to set up PFM - Agent for Platform:

jpcconf agent setup -key UNIX (jpcagtsetup agtu)
Note
If you execute the jpcconf agent setup (jpcagtsetup) command when the Performance Management programs and services of the local host on which the command is being executed have not completely stopped, an error may occur. In this case, make sure the Performance Management programs and services have stopped completely, and then re-execute the jpcconf agent setup (jpcagtsetup) command.

After this operation is finished, you may delete the PFM - Agent setup files located on the PFM - Manager host.

(c) Executing the setup command on the PFM - Web Console host

In PFM - Web Console, execute the following command to set up PFM - Agent for Platform:

jpcwagtsetup

After this operation is finished, you may delete the PFM - Agent for Platform setup files located on the PFM - Web Console host.

(3) Network setup[Figure]

This is necessary only when you need to change the settings according to the network configuration that uses Performance Management.

In network setup, you can specify the following two items:

(4) Changing the log file size[Figure]

The operational status of Performance Management is output to Performance Management's own log file. This log file is called the common message log. For the common message log, two files, each with 2,048 KB capacity by default, are used. You can change the file size if necessary.

For details, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

(5) Changing the performance data storage destination[Figure]

This is necessary only if you want to change the storage destination for the database for storing the performance data managed by PFM - Agent for Platform, the backup destination, or the export destination directory.

By default, performance data is stored in the following locations:

For details, see 2.4.1 Changing the storage location of performance data.

(6) Setting up PFM - Manager for the connection destination of PFM - Agent for Platform

On the host on which PFM - Agent is installed, set up the PFM - Manager that manages that PFM - Agent. To set up PFM - Manager for the connection destination, use the jpcconf mgrhost define (jpcnshostname) command.

Note
  • Even when multiple copies of PFM - Agent are installed on the same host, you can specify only a single PFM - Manager as the connection destination. You cannot specify a different PFM - Manager for each PFM - Agent.
  • When PFM - Agent and PFM - Manager are installed on the same host, PFM - Manager for the connection destination becomes the PFM - Manager of the local host. In this case, you cannot change the PFM - Manager for the connection destination to another PFM - Manager.

To set up PFM - Manager for the connection destination:

  1. Stop Performance Management programs and services.
    Before executing a setup operation, stop all Performance Management programs and services on the local host if they are active. For details about how to stop services, see the chapter explaining how to start and stop Performance Management in the manual Job Management Partner 1/Performance Management User's Guide.
    If Performance Management programs and services are active when you attempt to execute the jpcconf mgrhost define (jpcnshostname) command, a message is displayed asking the user whether to stop those programs and services.

  2. Specify the host name of the PFM - Manager host at the connection destination and execute the jpcconf mgrhost define (jpcnshostname) command.
    For example, if the PFM - Manager host at the connection destination is on host01, specify the following:
    jpcconf mgrhost define -host host01 (jpcnshostname -s host01)

(7) Setting up the action log[Figure]

You can log information in the action log when, for example, PFM services start and stop, and the status of the connection to PFM - Manager changes. The action log stores history information that is output in conjunction with the alarms for thresholds related to system load and other conditions.

For details about how to set up the action log, see J. Outputting Action Log Data.

[Contents][Back][Next]

[Trademarks]

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