10.2.2 Installing and setting up PFM - Manager

(a) Performing an additional setup for PFM - Agent or PFM - RM information

To perform integrated management of PFM - Agent or PFM - RM in a cluster system, register the agent information of PFM - Agent or PFM - RM in PFM - Manager for the executing node and the standby node.

If PFM - Agent or PFM - RM is already registered in PFM - Manager, you do not have to follow the procedure described below. If PFM - Agent or PFM - RM is not registered yet, manually register PFM - Agent or PFM - RM according to the procedure.

When all of the following conditions apply, manually register PFM - Agent or PFM - RM in PFM - Manager:

• The PFM - Agent or PFM - RM to be installed is of a product version that is not specified in the Release Notes for PFM - Manager.

• PFM - Agent or PFM - RM is installed on a host other than PFM - Manager.

If, however, the Release Notes for PFM - Agent or PFM - RM state that it is necessary to execute the setup command, execute the setup command.

The setup procedure is the same as for a non-cluster system. For details, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

(b) Making sure the shared disk is online

Make sure that the shared disk is online on the executing node. If the shared disk is not online, place it online by using the cluster software and the volume manager.

(c) Setting up the logical host environment for PFM - Manager

Set up the logical host environment for PFM - Manager on the executing node. Before performing setup, stop all the Performance Management programs and services throughout the entire system.

1. Create a logical host environment.

   Execute the jpcconf ha setup command to create a logical host environment for PFM - Manager.

   Use -lhost to specify the logical host name. For DNS operations, specify a logical host name that does not include a domain name. Specify the -d environment directory name for the directory name of the shared disk.

   For example, execute the following command to set up a logical host with jp1-ha1 as the logical host name and S:\jp1 as the environment directory.

   jpcconf ha setup -key Manager -lhost jp1-ha1 -d S:\jp1

   When this command is executed, the jp1pc directory is created under S:\jp1, and the files required in the logical environment are copied to the environment directory. The following figure shows an example.

   Figure 10‒12: Execution example of the jpcconf ha setup command

   When the command is executed, the required data is copied from the local disk of the executing node to the shared disk, and the settings required for use on the logical host are performed.

   If you set up a logical host for PFM - Manager, the connection-target PFM - Manager in the physical host environment is renamed to the specified logical host name.

   For details on the jpcconf ha setup command, see the chapters that describes commands in the manual JP1/Performance Management Reference.

2. Check the settings for the logical host environment.

   Execute the jpcconf ha list command to check the settings for the logical host, and make sure that the logical host environment that has been created is correct.

   jpcconf ha list -key all

   An example of executing this command is as follows:

   

   For details on the jpcconf ha list command, see the chapters that describes commands in the manual JP1/Performance Management Reference.

(d) Performing a setup for a logical host of PFM - Agent or PFM - RM

This procedure is required only when PFM - Agent or PFM - RM needs to be set up on the same logical host as PFM - Manager.

For details on the setup procedure, see the chapters that describe operations on cluster systems in the appropriate PFM - Agent or PFM - RM manual.

(e) Specifying network settings

To use logical host names or logical IP addresses for communication among PFM - Manager and PFM - Web Console, add the following line to the environment-directory\jp1pc\mgr\viewsvr\jpcvsvr.ini file.

java.rmi.server.hostname=logical-host-name-or-logical-IP-address

For details on the host names used for communication between PFM - Manager, PFM - Web Console, and JP1/SLM, see the description of port numbers in the appendixes of the manual JP1/Performance Management Reference.

If you need to change the IP address and port number to connect to another instance of PFM- Manager, use the following procedure:

• Setting up IPv6 communication

  When using Performance Management in an IPv6 environment, enable IPv6 support by executing the jpcconf ipv6 enable command on the PFM - Agent, PFM - RM, and PFM - Manager hosts.

  In a cluster system, execute the command on the executing and standby nodes.

  Note that only IPv4 communication is supported between PFM - Manager and PFM - Web Console.

  For details, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

• Setting the IP address

  To set the IP addresses, directly edit the content of the jpchosts file. If you have edited the jpchosts file, copy the file from the executing node to the standby node.

  For details on setting IP addresses, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

• Setting port numbers

  This procedure is necessary only when running Performance Management in a network environment with a firewall.

  For Performance Management communications via a firewall, use the jpcconf port define command to set a port number.

  For example, execute the following command to set all port numbers for services that exist on the host with the logical host name jp1-ha1 specified in the fixed values.

  jpcconf port define -key all -lhost jp1-ha1

  When this command is executed, definitions of the port numbers and service names (TCP service name beginning with jp1pc by default) for Performance Management are added to the services file.

  In this example, the jpcconf port define command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on setting port numbers, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

  For details on the jpcconf port define command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

• Setting the host name or IP address used for communication with PFM - Web Console and JP1/SLM

  In the following situations, define the host name or IP address of PFM - Manager in the jpcvsvr.ini file on the PFM - Manager host.

  • IP address translation (NAT translation) takes place between the PFM - Manager host and the PFM - Web Console host.

  • Multiple IP addresses are used between the PFM - Manager host and the PFM - Web Console host.

  • When linking with JP1/SLM, IP address translation (NAT translation) takes place between the PFM - Manager host and the JP1/SLM host.

  • When linking with JP1/SLM, Multiple IP addresses are used between the PFM - Manager host and the JP1/SLM host.

  For details, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

(f) Changing the log file size

The operating status of Performance Management is output to a dedicated log file called the common message log. This setting is required if you want to change this file size.

For details, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

(g) Specifying settings for the authentication mode

This setting is required only if you want to change the authentication mode of Performance Management from PFM authentication mode to JP1 authentication mode.

For details, see 2. Managing User Accounts and Business Groups.

(h) Specifying settings for access control based on business groups

This setting is required if you want to use business groups to manage users in Performance Management. You can enable or disable access control based on business groups by entering a setting in the startup information file (jpccomm.ini).

For details, see 2. Managing User Accounts and Business Groups.

(i) Changing the storage locations of event data

The settings below are required if you want to change the storage destination, backup destination, or export destination of the event data managed by PFM - Manager.

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

• Data storage folder: environment-directory\jp1pc\mgr\store\

• Backup folder: environment-directory\jp1pc\mgr\store\backup\

• Export folder: environment-directory\jp1pc\mgr\store\dump\

For details on how to change a destination, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

(j) Specifying settings for action log output

This setting is required if you want to output an action log when an alarm is issued. An action log is log information output in conjunction with the alarm function, when an aspect of the system (such as the system load) exceeds a threshold. For details on how to set this option, see the section describing action log output in an appendix of the JP1/Performance Management Planning and Configuration Guide.

(k) Configuring the health check function

To configure the health check function:

1. Check the settings of the health check function.

   Execute the following command on the PFM - Manager host on the executing node to display the setting of the health check function.

   jpcconf hc display

   When the command is executed, the setting for the health check function appears as follows:

   • If the health check function is enabled: available

   • If the health check function is disabled: unavailable

   For details on the jpcconf hc display command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

2. Change the setting of the health check function.

   Execute the following command on the PFM - Manager host on the executing node to set up the health check function, if necessary.

   • To enable the health check function:

   jpcconf hc enable

   • To disable the health check function:

   jpcconf hc disable

   For details on the jpcconf hc enable and jpcconf hc disable commands, see the chapter explaining the commands in the manual JP1/Performance Management Reference.

(l) Exporting the logical host environment definitions

When a logical host environment for PFM - Manager is created on the executing node, apply the settings information for the executing node to the standby node. First, export the logical host environment definitions for the executing node to a file. To set up a different instance of Performance Management on the same logical host, perform an export after all setup procedures are completed.

1. Execute the jpcconf ha export command.

   Export the logical host environment definitions to the desired file.

   For example, execute the following command to export the logical host environment definitions to the lhostexp.conf file.

   jpcconf ha export -f lhostexp.conf

   If the health check function is enabled for the PFM - Manager in the logical host environment you are exporting, the health check agent will be set up on the logical host. In this case, information relating to the health check agent will be exported.

   In this example, the jpcconf ha export command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf ha export command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

(m) Copying the file containing the logical host environment definitions to the standby node

Copy the file that has been exported in step (l) from the executing node to the standby node, so that it will be applied on the standby node.

Next, use operations of the cluster software or volume manager software to place the shared disk online, and finish the operations on the executing node. If this shared disk will continue to be used, it is not necessary to take it offline.

(n) Importing the file containing the logical host environment definitions

Import the exported file copied from the executing node to the standby node.

1. Execute the jpcconf ha import command.

   Import the logical host environment definitions to the standby node.

   For example, execute the following command if the export file name is lhostexp.conf.

   jpcconf ha import -f lhostexp.conf

   When the jpcconf ha import command is executed, the environment settings for the standby node are changed to the same environment as for the executing node. Therefore, the necessary settings are made to use PFM - Manager on a logical host.

   If the health check function is enabled for the PFM - Manager in the logical host environment you are importing, the health check agent will be set up on the logical host. In this case, information relating to the health check agent will be imported.

   In this example, the jpcconf ha import command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf ha import command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

2. Check the settings for the logical host environment.

   Execute the jpcconf ha list command in the same manner as for the executing node, to check the settings of the logical host.

   Execute the command as follows:

   jpcconf ha list -key all

   For details on the jpcconf ha list command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

(a) Registering PFM - Manager in the cluster software

To use PFM - Manager on a logical host, register it in the cluster software, and set the cluster software to control the starting and stopping of PFM - Manager.

For details on how to register PFM - Agents or PFM - RM in the cluster software, see the chapters that describe operations in cluster systems in the appropriate PFM - Agent or PFM - RM manual.

The setting contents for registering PFM - Manager in the cluster software are described below by using items for registration in Windows WSFC as examples.

For example, when running PFM - Manager in standalone mode on a logical host, register the services listed in the following table in the cluster software.

When running PFM - Manager on the same logical host as PFM - Agent or PFM - RM, register the services listed in the table below in the cluster software. In this example, the system is running PFM - RM for Platform and PFM - Agent for Oracle.

Place the logical host name wherever LHOST appears. The following is an example for a Name Server service for which the logical host name is jp1-ha1:

• Name

  PFM - Name Server [jp1-ha1]

• Service name

  JP1PCMGR_PN [jp1-ha1]

For WSFC, these services are registered as WSFC resources. The settings for each resource are as follows. The setting items for WSFC are indicated by [ ].

• [Resource Type] is registered as General-Purpose Service.

• See Table 10-2 PFM - Manager services to register in the cluster software (standalone mode) and Table 10-3 PFM - Manager services to register in the cluster software (on a host with PFM - Manager, PFM - RM for Platform, and PFM - Agent for Oracle installed) and specify Dependencies.

  For example, if the PFM - Master Store [LHOST] service is to be registered into cluster software, specify the service in such a manner that it is in a dependency with PFM - Master Manager [LHOST] service because a dependency with cluster resource 2 is required.

• Startup Parameters and Registry Replication are not specified.

• Specify the settings for the Policies tab in Properties according to whether a failover is performed when a problem occurs in Performance Management.

  For example, if you want to perform a failover in the event of a PFM - Manager failure, specify as follows:

  • Select the If resource fails, attempt restart on current node check box.

  • Select the If restart is unsuccessful, fail over all resources in this Role check box.

  • As a guideline, specify 3 in Maximum restarts in the specified period.

Important

• Starting and stopping of services registered on a cluster are controlled by the cluster software. Therefore, set [Startup Type] to [Manual] so that automatic startup is not performed when the OS starts up on the executing node and the standby node. Services are set to [Manual] immediately after setup by the jpcconf ha setup command. In addition, do not use the following command to perform a forced stop.

  jpcspm stop -key all -lhost logical-host-name -kill immediate

• When PFM - Manager is linked with integrated management products (JP1/IM), set dependency relationships in a way that allows services to start and stop in the following order:

  - JP1/Base services start before PFM - Manager services start.

  - PFM - Manager services stop before JP1/Base services stop.

(b) Checking starting and stopping from the cluster software

Perform operations to start and stop PFM - Manager from the cluster software in each node, and make sure that the operations are normal.