3.1.4 Setup procedure for the Windows edition

(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 3‒6: Setup files to be copied (for Windows)

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

This example shows execution in the interactive mode, but you can also execute the jpcconf agent setup command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

Notes about executing the command

Before you execute the command, stop all Performance Management programs and services. An error might 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 might 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 might delete the setup files for PFM - RM for Platform that were copied to the PFM - Web Console.

(a) Instance environment setting items that must be specified depending on what is monitored in the instance

The instance environment setting items that must be specified differ depending on what is monitored in the instance. The following table lists and describes the instance environment setting items that must be specified for each monitoring target in the instance.

(b) Instance environment setting items and values

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

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

For details about how to execute the jpcconf inst setup command, see (d) Execution in the interactive mode and (e) Execution in the non-interactive mode.

For details about the jpcconf inst setup command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

(c) Instance environment setting items that are not displayed

Instance environment setting items are usually displayed by executing a command, but some might not be displayed depending on the contents of other setting items or for some other reason. The table below lists and describes conditions that prevent instance environment setting items from being displayed. It also shows the input values that are used in such cases.

(d) Execution in the interactive mode

1. Execute the jpcconf inst setup command.

   The following example sets up an instance environment using inst1 as the instance name:

   jpcconf inst setup -key RMPlatform -inst inst1

2. Set up an instance environment for PFM - RM for Platform.

   Enter each instance environment setting item for PFM - RM for Platform according to the instructions given by the command. For details about each instance environment setting item, see Table 3-9. After you input each setting item, press the Enter key. To use a displayed default value, simply press the Enter key.

   The following is a setting example in which the instance includes a monitored host running UNIX:

   C:\Program Files\Hitachi\jp1pc\tools>jpcconf inst setup -key RMPlatform -inst inst1
    UseCommonAccount   [N]                  :<Enter>
    Interval             [300]                :<Enter>
    Std_Category         [Y]                  :<Enter>
    Disk_Category        [Y]                  :<Enter>
    Network_Category     [Y]                  :<Enter>
    Ps_Category          [Y]                  :<Enter>
    RMHost_User#1                             :rmuser<Enter>
    RMHost_Password#1                         :rmpass#2<Enter>
    Re-enter#1                                :rmpass#2<Enter>
    RMHost_Domain#1      []                   :<Enter>
    SSH_Type             [putty]              :<Enter>
    SSH_Client           [] :C:\Program Files\PuTTY\plink.exe#3<Enter>
    Perl_Module          [] :C:\Perl\bin\perl.exe#3<Enter>
    Log_Size (MB)        [3]                  :<Enter>
   KAVE05080-I The instance environment is now being created. (servicekey#4=RMPlatform, inst=inst1)
   KAVE05081-I The instance environment has been created. (servicekey#4=RMPlatform, inst=inst1)

   #1

   This item is not displayed when Y is specified for UseCommonAccount.

   #2

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

   #3

   Enter this line if the instance includes monitored hosts running UNIX. There is no need to enter this line if all monitored hosts in the instance are running Windows.

   #4

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

(e) Execution in the non-interactive mode

1. Execute the jpcconf inst setup command to create a definition file template.

   Execute the command as follows:

   jpcconf inst setup -key RMPlatform -noquery -template definition-file-name

   Sections and labels that correspond to the instance environment setting items are output to a definition file. Note that the label of the Instance Definitions section is left blank.

2. Edit the definition file template created in step 1.

   Edit the setting values as required for the instance environment.

   For details about the product-specific labels to be specified in the definition file, see Table 3-9.

   Shown below is an example of a definition file for an instance environment in which the instance includes monitored hosts running UNIX. Specify values for the labels in the Instance Definitions section as required for the instance environment.

   [Common Definitions]
   Definition File Version=0001
    
   [Product Information]
   Product ID=7
    
   [Instance Definitions]
   UseCommonAccount=
   Interval=
   Std_Category=
   Disk_Category=
   Network_Category=
   Ps_Category=
   RMHost_User#1=rmuser
   RMHost_Password#1=rmpass
   RMHost_Domain#1=
   SSH_Type=putty
   SSH_Client= C:\Program Files\PuTTY\plink.exe#2
   Perl_Module= C:\Perl\bin\perl.exe#2
   Log_Size=

   #1

   There is no need to specify values for these items if Y is specified for UseCommonAccount.

   #2

   Enter this line if the instance includes monitored hosts running UNIX. There is no need to enter this line if all monitored hosts in the instance are running Windows.

3. Execute the jpcconf inst setup command to set up an instance environment for PFM - RM for Platform.

   The following example sets up an instance environment using inst1 as the instance name. For the -input option, specify the definition file edited in step 2.

   jpcconf inst setup -key RMPlatform -inst inst1 -noquery -input definition-file-name

Note:

If the definition file contains confidential information such as passwords, save the definition file in a secure location, and delete it after you have used it. If you want to transfer the definition file between hosts, we recommend that you use a secure file transfer protocol, such as Secure File Transfer Protocol (SFTP), which is FTP over an SSH tunnel.

When all of the settings have been completed, an instance environment can be built. The following table shows the folder structure of an instance environment.

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 3.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 F.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 JP1/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 JP1/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 JP1/Performance Management User's Guide.

You cannot set up an instance environment by using PFM - Web Console's facility to distributing agent-specific properties.

(f) Setting an offset value for starting performance data collection

You can set an offset value (in seconds) for starting performance data collection from monitoring targets on an instance-by-instance basis. By adjusting the offset values set for instances, you can make instances start collecting performance data at different times, thereby reducing the number of monitoring targets from which performance data is collected at a certain point in time.

For details about how to set an offset value, see 8. Definition Files in Service startup initialization file of Remote Monitor Collector (jpcagt.ini).

(a) Monitoring target setting items that must be specified depending on what is monitored

The monitoring target setting items that must be specified differ depending on what is monitored. The following table lists and describes these monitoring target setting items that must be specified for each monitoring target.

(b) Monitoring target setting items and values

The table below lists and describes the setting items and values for a monitored host. Check this information before you start operations.

Use the jpcconf target setup command to set up a monitored host.

For details about how to execute the jpcconf target setup command, see (d) Execution in the interactive mode and (e) Execution in the non-interactive mode.

For details about the jpcconf target setup command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

Legend:

--: No default is set.

#1

When the jpcconf target setup command is executed in the non-interactive mode, this item name is used as a product-specific label in the definition file. For details about commands in the non-interactive mode, see the chapter that describes commands in the manual JP1/Performance Management Reference.

#2

For health check monitoring, you can also specify hosts and hardware equipment that support the ICMP protocol (can communicate through ping command).

#3

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.

#4

Health check monitoring does not collect performance data.

#5

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

#6

If the specification is omitted, the host name of the PFM - RM host is assumed.

#7

If the monitored host is running Windows, the specified user must be a member of the monitored host's Administrators group, Performance Log Users group, or Performance Monitor Users group.

To perform operations such as Windows security audit, you also need permissions to execute such operations.

The type of records that can be collected differs according to the account type. For details about various account types and whether records can be collected, see 3.1.1(5)(a) Setting the user accounts.

If the monitored host is running Windows, note that the following check boxes in the General tab of the Administrator Properties window must not be selected:

- User must change password at next logon

- Account is disabled

In addition, if the monitored host specifies a domain user in an Active Directory environment, click the Account tab for that user, and then click the Log On To button to display the Logon Workstations window. In the Logon Workstations window, make sure that one of either of the conditions listed below exists there:

- The All computers option is selected.

- The following computers option is selected, and the host name of the monitored host is already registered.

If the monitored host resides in a work group environment, execute the gpedit.msc command to display the Local Computer Policy window, and select Computer Configuration, Windows Settings, Security Settings, Local Policies, and then Security Options. Then, make sure that the Network access: Sharing and security model for local accounts option is set to Classic - local users authenticate as themselves.

These notes also apply when User in common account information (wmi) is used.

#8

When the monitored host is running UNIX, use bash, bsh, or ksh for the login shell of the user to be specified.

This also applies when User in common account information (ssh) is used.

#9

This item is required if the monitored host is running Windows.

This also applies when Password in common account information (wmi) is used.

#10

When monitoring the local host, specify a local host name if all of the following conditions are satisfied:

• The PFM - RM host is a participant in a domain.

• The user of the PFM - RM host is used for connecting to the monitored host.

This also applies when Domain in common account information (wmi) is used. When using common account information, specify the local host name for Domain in common account information (wmi).

#11

This item is required if the monitored host is running UNIX.

Also, when operating PFM - RM for Platform in a cluster system, specify a file path that can be accessed from both the active server and the standby server.

This also applies when Private_Key_File in common account information (ssh) is used.

(c) Monitored host setting items that are not displayed

Monitored host setting items are usually displayed by executing a command, but some are not displayed depending on the contents of other setting items or for some other reason. The table below describes conditions that prevent monitored host setting items from being displayed. It also shows the input values that are used in such cases.

(d) Execution in the interactive mode

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 name of 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

2. Set up the monitoring target for PFM - RM for Platform.

   Enter setting items for the monitored host according to the instructions given by the command. For details about the setting items for the monitored host, see Table 3-16. After you input each setting item, press the Enter key to set it. To use a displayed default value, simply press the Enter key.

   The following is an example of the settings when the monitored host is running Windows:

   Conditions for the monitored host to be set up

   - Host name: targethost1

   - User: user1

   - Password: pass1

   - Domain: domain1

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

   #1

   This item is not displayed when Y is specified for UseCommonAccount.

   #2

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

   #3

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

   The following is an example of the settings when the monitored host is running UNIX:

   Conditions for the monitored host to be set up

   - Host name: targethost2

   - User: ssh-user

   C:\Program Files\Hitachi\jp1pc\tools>jpcconf target setup -key RMPlatform -inst inst1 -target targethost2
    Target Host          []                   :targethost2<Enter>
    UseCommonAccount     [N]                  :<Enter>
    TargetType           [wmi]                :ssh<Enter>
    User#1                                    :ssh-user<Enter>
    Private_Key_File     [] :C:\Program Files\PuTTY\agt7.ppk<Enter>
    Port                 [22]                 :<Enter>
   KAVE05361-I The monitoring target is now being added. (servicekey#2=RMPlatform, inst=inst1, target=targethost2)
   KAVE05362-I The monitoring target has been added. (servicekey#2=RMPlatform, inst=inst1, target=targethost2)

   #1

   This item is not displayed when Y is specified for UseCommonAccount.

   #2

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

   The following is an example of the settings for health check monitoring:

   Conditions for the monitored host to be set up

   - Host name: targethost3

   C:\Program Files\Hitachi\jp1pc\tools>jpcconf target setup -key RMPlatform -inst inst1 -target targethost3
    Target Host          []                   :targethost3<Enter>
    UseCommonAccount     [N]                  :<Enter>
    TargetType           [wmi]                :icmp<Enter>
   KAVE05361-I The monitoring target is now being added. (servicekey#=RMPlatform, inst=inst1, target=targethost3)
   KAVE05362-I The monitoring target has been added. (servicekey#=RMPlatform, inst=inst1, target=targethost3)

   #

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

(e) Execution in the non-interactive mode

1. Execute the jpcconf target setup command to create a definition file template.

   Execute the command as follows:

   jpcconf target setup -key RMPlatform -noquery -template definition-file-name

   Sections and labels that correspond to the monitored host setting items are output to a definition file. Note that the value for the label of the Target Definitions section is left blank.

2. Edit the definition file template created in step 1.

   Edit the template setting values as required for the monitored host.

   For details about the product-specific labels to be specified in the definition file, see Table 3-16.

   Shown below is an example of the coding of a definition file when the monitored host is running Windows. Specify values for the labels in the Target Definitions section as required for the monitored host.

   [Common Definitions]
   Definition File Version=0001
    
   [Product Information]
   Product ID=7
    
   [Target Definitions]
   Target Host=targethost1
   UseCommonAccount=
   TargetType=
   User#=user1
   Password#=pass1
   Domain#=domain1
   Private_Key_File=
   Port=

   #

   There is no need to specify a value for this item when Y is specified for UseCommonAccount.

   Shown below is an example of the coding of a definition file when the monitored host is running UNIX. Specify values for the labels in the Target Definitions section as required for the monitored host.

   [Common Definitions]
   Definition File Version=0001
    
   [Product Information]
   Product ID=7
    
   [Target Definitions]
   Target Host=targethost2
   UseCommonAccount=
   TargetType=ssh
   User#=ssh-user
   Password=
   Domain=
   Private_Key_File#= C:\Program Files\PuTTY\agt7.ppk
   Port=

   #

   There is no need to specify a value for this item when Y is specified for UseCommonAccount.

   Shown below is an example of the coding of a definition file for health check monitoring. Specify values for the labels in the Target Definitions section as required for the monitored host.

   [Common Definitions]
   Definition File Version=0001
    
   [Product Information]
   Product ID=7
    
   [Target Definitions]
   Target Host=targethost3
   UseCommonAccount=
   TargetType=icmp
   User=
   Password=
   Domain=
   Private_Key_File=
   Port=

3. Execute the jpcconf target setup command to set up the monitoring target for PFM - RM for Platform.

   The following example sets up a monitoring target where inst1 is the instance name and targethost1 is the monitored host. For the -input option, specify the definition file edited in step 2.

   jpcconf target setup -key RMPlatform -inst inst1 -target targethost1 -input definition-file-name -noquery

Note:

If the definition file contains confidential information such as passwords, save the definition file in a secure location, and delete it after you have used it. If you want to transfer the definition file between hosts, we recommend that you use a secure file transfer protocol, such as Secure File Transfer Protocol (SFTP), which is FTP over an SSH tunnel.

When all of the settings have been completed, a monitoring target environment can be built. The following table shows the folder structure of the monitoring target environment.

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 JP1/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 3.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 F.3 List of properties of remote agents and group agents.