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

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

2.1.4 Setup procedure (for Windows)

This subsection describes how to set up PFM - RM for Platform.

[Figure] indicates the following setup items:

Organization of this subsection
(1) Registering PFM - RM for Platform
(2) Setting up an instance environment
(3) Setting the monitored host
(4) Network settings
(5) Changing the log file size
(6) Changing performance data storage locations
(7) Setting the connection-target PFM - Manager
(8) Action log output settings

(1) Registering PFM - RM for Platform

To achieve central management of PFM - RM for Platform in the Performance Management system, you must register PFM - RM for Platform into PFM - Manager and PFM - Web Console.

You must register PFM - RM for Platform at the following times:

The following figure shows the procedure for registering PFM - RM for Platform.

Figure 2-6 Procedure for registering PFM - RM for Platform (for Windows)

[Figure]

Notes about registering PFM - RM for Platform
  • Register PFM - RM for Platform before you set up an instance environment.
  • If you install different versions of PFM - RM for Platform on separate hosts, set up old versions before you set up new versions.
  • If you install PFM - RM for Platform on the same host as where PFM - Manager is installed, the jpcconf agent setup command executes automatically.
  • When PFM - RM for Platform is registered, folders named RM Platform are created on the Reports and Alarms pages of PFM - Web Console. If you have already created a folder or file named RM Platform on the Reports page, you must rename it before starting the registration procedure.

The following subsections describe how to register PFM - RM for Platform.

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

Copy the setup files from the PFM - RM host to the hosts where PFM - Manager and PFM - Web Console are installed.

To copy the setup files:

  1. Stop PFM - Web Console.
    If PFM - Web Console is running, stop it.

  2. Copy the setup files in the binary mode.
    Copy the files from the PFM - RM host to the PFM - Manager and PFM - Web Console hosts.
    The following table lists the source file storage locations and the copy destination locations.

    Table 2-2 Setup files to be copied (for Windows)

    No. Source (setup files for PFM - RM for Platform) Target
    Program name OS Target folder
    1 PFM-RM-for-Platform-installation-folder\setup\jpcagt7w.EXE PFM - Manager Windows PFM-Manager-installation-folder\setup
    2 PFM-RM-for-Platform-installation-folder\setup\jpcagt7u.Z UNIX /opt/jp1pc/setup/
    3 PFM-RM-for-Platform-installation-folder\setup\jpcagt7w.EXE PFM - Web Console Windows PFM-Web-Console-installation-folder\setup
    4 PFM-RM-for-Platform-installation-folder\setup\jpcagt7u.Z UNIX /opt/jp1pcwebcon/setup/

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

At the PFM - Manager host, execute the setup command for PFM - RM for Platform.

Execute the following command:

jpcconf agent setup -key RMPlatform

Notes about executing the command
Before you execute the command, stop all Performance Management programs and services. An error may occur if the jpcconf agent setup command is executed before all Performance Management programs and services have stopped completely. If an error has occurred, re-execute the jpcconf agent setup command.

After you have executed the setup command at the PFM - Manager host, you may delete the setup files for PFM - RM for Platform that were copied to the PFM - Manager.

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

At the PFM - Web Console host, execute the setup command for PFM - RM for Platform.

Execute the following command:

jpcwagtsetup

After you have executed the setup command at the PFM - Web Console host, you may delete the setup files for PFM - RM for Platform that were copied to the PFM - Web Console.

(2) Setting up an instance environment

Set up an instance environment for PFM - RM for Platform at the PFM - RM host. To set multiple instance environments, repeat this procedure.

Notes about setting instance environments
Before you set instance environments, make sure that the procedure described in 2.1.1(5) Environment settings required for collecting performance data (for Windows) has been completed and the correct environment has been set up.

The table below lists and describes the instance environment setting items. Check this information before you start the operation.

Table 2-3 Instance environment setting items for PFM - RM for Platform (for Windows)

No. Item name Description Setting Default Whether updatable by the jpcconf inst setup command
1 Interval Specifies a collection interval for the collection process. Specify a value in the range from 60 to 3,600 (seconds). 300 U
2 Std_Category#1 Specifies whether the collection process is to collect basic information (PI and PI_CPU records). Specify one of the following values:
  • Y: Collect
  • N: Do not collect
 Y U
3 Disk_Category#1 Specifies whether the collection process is to collect disk information (PI_PDSK and PI_LDSK records). Specify one of the following values:
  • Y: Collect
  • N: Do not collect
 Y U
4 Network_Category#1 Specifies whether the collection process is to collect network information (PI_NET record). Specify one of the following values:
  • Y: Collect
  • N: Do not collect
 Y U
5 RMHost_User Specifies the user account#2 used at the PFM - RM host. From 1 to 256 bytes of characters can be specified.
The tab character cannot be used.		 -- U
6 RMHost_Password Specifies the password for the account used at the PFM - RM host. The characters entered in this item are not displayed on the screen. If you specify this password, you will be prompted to confirm by re-entering the same password. From 1 to 256 bytes of characters can be specified.
The tab character cannot be used.		 -- U
7 RMHost_Domain Specifies the domain name to which the account used at the PFM - RM host belongs.
  • If this account belongs to a workgroup, specify nothing.
 From 1 to 256 bytes of characters can be specified.
The tab character cannot be used.		 No domain name is specified. U
8 Log_Size Specifies the maximum size of one agent log file. #3 Specify a value in the range from 1 to 32 (megabytes).
A value of 3 or greater is recommended.		 3 U

Legend:
U: Updatable
--: Not set by default

#1
The Std_Category, Disk_Category, and Network_Category settings take precedence over the collection settings for the individual records.
For example, if you set Std_Category to N (do not collect), a PI record is handled as follows:
[Figure] The PI record information is not recorded in the Store database.
[Figure] If an attempt is made to display a real-time report based on PI records, the KAVJS5001-I error message is displayed.
[Figure] If an alarm is bound to a PI record, that alarm will not function.

#2
If you run PFM - RM for Platform in a cluster system, specify an account that can log onto both the executing node and the standby node using the same user name and password.

#3
The following formula can be used to estimate the agent log file size:
Agent log (kilobytes) = ((a x 24 x 3600)/b x 4)/(4 x 1024)
Legend:
a: Number of days agent logs are stored
b: Interval value of the instance
For agent logs, the maximum number of files collected for each instance is (8 + the number of monitoring targets x 4). If there is not enough free space on the hard disk, agent logs result in an output error. For details about agent logs, see 7.3 Log information.

Use the jpcconf inst setup command to set up an instance environment.

To set up an instance environment:

  1. Execute the jpcconf inst setup command.
    The command sets an instance environment with an instance name of inst1:
     
jpcconf inst setup -key RMPlatform -inst inst1
    For details about the jpcconf inst setup command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

  2. Set up an instance environment for PFM - RM for Platform.
    Enter each instance environment setting for PFM - RM for Platform according to the command's instructions. For details about each instance environment setting, see Table 2-3. After you enter each setting, press the Enter key. To use a displayed default value, simply press the Enter key.
    The following example sets all instance environment settings to the default values:
    C:\Program Files\Hitachi\jp1pc\tools>jpcconf inst setup -key RMPlatform -inst inst1
 Interval                 [300]                :<Enter>
 Std_Category             [Y]                  :<Enter>
 Disk_Category            [Y]                  :<Enter>
 Network_Category         [Y]                  :<Enter>
 
 RMHost_User                                   :rmuser<Enter>
 RMHost_Password                               :rmpass#1<Enter>
                                      Re-enter :rmpass#1<Enter>
 RMHost_Domain            []                   :<Enter>
 Log_Size (MB)            [3]                  :<Enter>
KAVE05080-I The instance environment is now being created. (servicekey#2=RMPlatform, inst=inst1)
KAVE05081-I The instance environment has been created. (servicekey#2=RMPlatform, inst=inst1)

    #1
    Re-entry of the password is prompted. The entered password is not displayed on the screen.

    #2
    If PFM - Manager's product name display function is disabled, agt7 is displayed for servicekey.

When all the settings have been entered, the instance environment is configured. The following table shows the folder structure of an instance environment.

Table 2-4 Folder structure of an instance environment (for Windows)

No. Storage folder File name Description
1 PFM-RM-for-Platform-installation-folder#1\agt7\agent\instance-name jpcagt.ini Service startup initialization file of Remote Monitor Collector
2 jpcagt.ini.lck Lock file for the service startup initialization file of Remote Monitor Collector (for each instance)
3 jpcagt.ini.model#2 Sample of a service startup initialization file of Remote Monitor Collector
4 status.dat Intermediate file for internal processing
5 tstatuses.dat Virtual Agent status information#3
6 targetlist.ini List of monitoring targets
7 grouplist.ini List of groups
8 GARULES.DAT Grouping rule description file
9 targets Storage folder for remote agent
10 groups Storage folder for group agent
11 log Storage folder for log files
12 PFM-RM-for-Platform-installation-folder#1\agt7\store\instance-name *.DB Performance data file
13 *.IDX Index files for performance data files
14 *.LCK Lock files for performance data files
15 jpcsto.ini Service startup initialization file of Remote Monitor Store
16 jpcsto.ini.model#2 Model file for the service startup initialization file of Remote Monitor Store
17 status.dat Intermediate file for internal processing
18 *.DAT Definition file for a data model
19 dump Export folder
20 backup Backup folder
21 partial Partial backup folder
22 import Import folder
23 log Storage folder for log files

#1
If you run a logical host, replace PFM-RM-for-Platform-installation-folder with environment-folder\jp1pc. An environment folder is a folder on the shared disk that is specified when the logical host is created.

#2
Use these sample files when you want to restore the settings to their initial values from when the instance environment was configured.

#3
Created when the health check function is enabled.

To change an instance environment, re-execute the jpcconf inst setup command and then update each instance environment setting. For details about updating the instance environment settings, see 2.6.2 Updating an instance environment.

You can change some settings by using PFM - Web Console to edit properties. For details about the information that can be changed by editing properties, see E.1 List of properties of the Remote Monitor Store service.

In an instance environment, the service IDs and Windows service names are as follows:

Service IDs in an instance environment
  • For the Remote Monitor Collector service
    7Ainstance-number instance-name[host-name]
  • For the Remote Monitor Store service
    7Sinstance-number instance-name[host-name]
  • For the Group Agent service
    7Ainstance-number instance-name[All@host-name]
In PFM - RM for Platform, the instance name specified in the jpcconf inst setup command is displayed.
If the host name of the PFM - RM host is host1, and inst1 is specified as the instance name, the service IDs will be as follows:
  • For the Remote Monitor Collector service
    7A1inst1[host1]
  • For the Remote Monitor Store service
    7S1inst1[host1]
  • For the Group Agent service
    7A1inst1[All@host1]
For details about the service IDs, see the naming rules provided in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Windows service names in an instance environment
  • For the Remote Monitor Collector service
    PFM - RM for Platform instance-name
  • For the Remote Monitor Store service
    PFM - RM Store for Platform instance-name
If inst1 is specified as the instance name, the service names will be as follows:
  • For the Remote Monitor Collector service
    PFM - RM for Platform inst1
  • For the Remote Monitor Store service
    PFM - RM Store for Platform inst1
For details about the Windows service names, see the naming rules provided in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide. For details about the Windows service names when a logical host is used for operation, see the chapter that describes cluster system configuration and operation in the Job Management Partner 1/Performance Management User's Guide.

(3) Setting the monitored host

Set information about the monitored host that was specified in (2) Setting up an instance environment. You can set multiple monitored hosts for a single instance. To set multiple monitored hosts, repeat this procedure.

Notes about setting a monitored host

The table below lists and describes the settings for the monitored host. Check this information before you start operations.

Table 2-5 Settings for the monitored host in PFM - RM for Platform

No. Item name Description Setting Default Whether updatable by the jpcconf target setup command
1 Target Host Specifies the name of the monitored host. Specify a host name that can be resolved.#1
The specified monitored host name is used during performance data collection and health checking. If JP1/IM or NNM is linked, this name is also used as the event host name.		 From 1 to 32 bytes of alphanumeric characters and the hyphen (-) are permitted.
The name cannot begin with a hyphen (-).
The specified value must be unique within the instance.#2		 -- U
2 User Specifies the user#3 used to connect to the monitored host. From 1 to 256 bytes of characters are permitted.
The tab character is not permitted.		 -- U
3 Password Specifies the password used to connect to the monitored host.
This information is not displayed on the screen. When the password is specified, re-entry of the password is requested.		 From 1 to 256 bytes of characters are permitted.
The tab character is not permitted.		 -- U
4 Domain Specifies the name of the domain to which the monitored host belongs.
If the host belongs to a workgroup, specify nothing.		 From 0 to 256 bytes of characters are permitted.
The tab character is not permitted.		 No domain name is specified. U

Legend:
U: Updatable
--: Not set by default

#1
To collect performance data and perform health checking, the name must be resolvable at least by the PFM - RM host.
If the JP1/IM linkage facility is used, the name must be resolvable by the JP1/IM host. If the OpenView linkage facility is used, the name must be resolvable by the PFM - Manager host as well as the NNM host.

#2
All cannot be used because it is a reserved word for group agents.

#3
The specified user must be a member of the monitored host's Administrators, Performance Log Users, or Performance Monitor Users group.
If the OS of the monitored host is Windows Server 2008, the UAC security function is enabled, and an account other than Built-in Administrator is used, then that account must have been set as a member of the Performance Log Users or Performance Monitor Users group.

To set the monitored host, use the jpcconf target setup command.

To set the monitored host:

  1. Execute the jpcconf target setup command.
    In PFM - RM for Platform, we recommend that you specify the host name of the monitored host as the monitoring target.
    The following example sets the monitored host targethost1 with instance name inst1 as the monitoring target:
     
jpcconf target setup -key RMPlatform -inst inst1 -target targethost1
    For details about the jpcconf target setup command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

  2. Set up the monitoring target for PFM - RM for Platform.
    Enter settings for the monitored host according to the command's instructions. For details about the settings for the monitored host, see Table 2-5. After you enter each setting, press the Enter key to set it. To use a displayed default value, press the Enter key.
    The following shows an example of setting up a monitoring target:

    Monitored host to be set up:
    [Figure] Host name: targethost1
    [Figure] User: user1
    [Figure] Password: pass1
    [Figure] Domain: domain1
     
C:\Program Files\Hitachi\jp1pc\tools>jpcconf target setup -key RMPlatform -inst inst1 -target targethost1
 Target Host              []                   :targethost1<Enter>
 User                                          :user1<Enter>
 Password                                      :pass1#1<Enter>
                                      Re-enter :pass1#1<Enter>
 Domain                   []                   :domain1<Enter>
KAVE05361-I The monitoring target is now being added. (servicekey#2=RMPlatform, inst=inst1, target=targethost1)
KAVE05362-I The monitoring target has been added. (servicekey#2=RMPlatform, inst=inst1, target=targethost1)

    #1
    Re-entry of the password is requested. The entered password is not displayed on the screen.

    #2
    If PFM - Manager's product name display function is disabled, agt7 is displayed for servicekey.

When entry of all settings is completed, an environment for the monitoring target is configured. The following table shows the folder structure of the monitoring target environment.

Table 2-6 Folder structure of the monitoring target environment

No. Storage folder File name Description
1 PFM-RM-for-Platform-installation-folder#\agt7\agent\instance-name\targets monitoring-target-name.ini Monitoring target settings file
2 monitoring-target-name.ini.model Sample of a monitoring target settings file
3 PFM-RM-for-Platform-installation-folder#\agt7\agent\instance-name\targets\monitoring-target-name -- Work folder for the monitoring target

Legend:
--: Not applicable

#
If you run a logical host, replace PFM-RM-for-Platform-installation-folder with environment-folder\jp1pc.

The following service IDs are added by the monitoring target settings:

Service IDs to be added
  • Remote Agent service
    7Ainstance-number instance-name[monitoring-target-name@host-name]
    The instance name and monitoring target name will be the values specified in the jpcconf target setup command.
    If you specify host1 as the host name of the PFM - RM host, inst1 as the instance name, and targethost1 as the monitoring target name, the service ID will be as follows:
    7A1inst1[targethost1@host1]
For details about the service IDs, see the naming rules provided in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

If you want to change information about the monitoring target, re-execute the jpcconf target setup command and update the information. For details about updating a monitoring target, see 2.6.3 Updating a monitoring target.

You can change some settings by using PFM - Web Console to edit properties. For details about the information that can be changed by editing properties, see E.3 List of properties of remote agents and group agents.

(4) Network settings[Figure]

You must specify network settings only if you need to change the network environment settings for the network configuration where Performance Management is used.

There are two types of network environment settings, as described below. Change network settings as necessary.

(5) Changing the log file size[Figure]

The operation status of Performance Management is output to log files unique to Performance Management. This setting is required in order to change the size of these log files.

These unique log files are called the common message log.

For the common message log, two files with a size of 2,048 kilobytes each are used by default. For details about changing the common message log, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

(6) Changing performance data storage locations[Figure]

These settings are required in order to change the following settings for the performance data that is managed by PFM - RM for Platform:

Note:
If you use a logical host for operation, replace PFM-RM-for-Platform-installation-folder with environment-folder\jp1pc.

For details about changing performance data storage locations, see 2.6.1 Changing performance data storage locations.

(7) Setting the connection-target PFM - Manager

You must specify on the PFM - RM host information about the PFM - Manager that manages PFM - RM for Platform. The jpcconf mgrhost define command is used to make this setting.

Notes about setting the connection-target PFM - Manager
  • Only one PFM - Manager can be set as the connection destination even when multiple PFM - RMs are installed on the same host. A different PFM - Manager cannot be specified for each PFM - RM.
  • If PFM - RM for Platform and PFM - Manager are installed on the same host, then the PFM - Manager on the local host is the connection-target PFM - Manager. In this case, you cannot change the connection-target PFM - Manager to any other PFM - Manager. To connect to PFM - Manager on a remote host, install PFM - RM for Platform on a different host than for PFM - Manager.

To set the connection-target PFM - Manager:

  1. Stop the Performance Management programs and services.
    If any Performance Management programs and services are running on the local host, stop all of them before starting the setup procedure. If Performance Management programs and services are running during execution of the jpcconf mgrhost define command, a message is displayed that asks you to terminate them.
    For details about how to stop services, see the chapter that describes starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.

  2. Execute the jpcconf mgrhost define command with the host name of the connection-target PFM - Manager specified.
    The following shows an example of command execution when the connection-target PFM - Manager is located on the host01 host:
    jpcconf mgrhost define -host host01

(8) Action log output settings[Figure]

These settings are required in order to output action logs at the following times:

An action log contains log information about exceeded threshold values caused by factors such as system overloads; its output is linked with the alarm function. For details about the action log output settings, see I. Outputting Action Log Data.

[Contents][Back][Next]

[Trademarks]

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