Job Management Partner 1/Performance Management User's Guide
This subsection describes the methods for installing and setting up PFM - Manager in a cluster system.
- Organization of this subsection
- (1) Process flow for installation and setup
- (2) Installation procedure
- (3) Setup procedure
- (4) Cluster software setting procedure
(1) Process flow for installation and setup
The following figure shows the process flow for installation and setup of PFM - Manager used on a logical host.
Figure 9-10 Process flow for installation and setup of PFM - Manager used on a logical host (in Windows)
- Notes:
- When PFM - Manager in a logical host environment is set up, PFM - Manager on the physical host environment can no longer be executed. However, the Action Handler service can still be executed, because it uses PFM - Agent or PFM - RM in the physical host environment.
When unsetup is performed on PFM - Manager in a logical host environment, PFM - Manager in the physical host environment can once again be executed.
- When PFM - Manager is set up in a logical host environment, the logical host environment inherits the PFM - Manager definitions from the physical host environment. However, the content of the Store database is not inherited. If unsetup is performed on PFM - Manager in the logical host environment, the definitions for the logical host environment and the Store database are deleted, and therefore switching to the physical host environment is not possible.
- Do not manually set JPC_HOSTNAME as an environment variable, because JPC_HOSTNAME is used by Performance Management as an environment variable. If you specify this setting, Performance Management will not run correctly.
- For PFM - Manager version 09-00 or later, when you set up a new instance of PFM - Manager in a logical host environment, the settings of the health check function in the physical host environment are inherited by the logical host environment. If necessary, you must modify the settings of the health check function.
- In a logical host environment, the function for setting monitoring-host names cannot be used. The jpccomm.ini file on a logical host is ignored, and the host name for the logical host is used.
The installation and setup procedures for PFM - Manager and the setting procedures for the cluster software are explained below.
In the procedure explanation, the image
indicates items to be performed on the executing node, and the image
indicates items to be performed on the standby node. In addition, the image
indicates setup items that are either required depending on the environment or can be performed if you want to set a value other than the default settings.
(2) Installation procedure
Perform a new installation of PFM - Manager on the executing node and the standby node. The installation procedure is the same as for a non-cluster system. For details, see the chapter describing installation and setup (in Windows) in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Note:
- The installation destination is the local disk. Do not install PFM - Manager on the shared disk.
(3) Setup procedure
Perform PFM - Manager setup on the executing node first. Next, export the logical host environment definitions for the executing node to a file. Finally, import the file containing the environment definitions to the standby node to apply the setup content from the executing node to the standby node.
Figure 9-11 Method for applying the content set up on the executing node to the standby node
Each setup procedure is explained below.
(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.
PFM - Manager version 09-00 or later automatically registers PFM - Agent or PFM - RM, so no additional setup is required for the PFM - Agent or PFM - RM information. However, if the release date of PFM - Agent or PFM - RM is later than that of PFM - Manager, PFM - Agent, or PFM - RM must be registered manually. For details on the release dates for PFM - Manager, PFM - Agent, and PFM - RM, see the Release Notes for each program.
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 Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Note:
- If you add another PFM - Agent or PFM - RM to the same host as PFM - Manager, an additional setup is not required.
(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 a logical host 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.
To set up a logical host:
- 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.
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.
jpcconf ha setup -key Manager -lhost jp1-ha1 -d S:\jp1
Figure 9-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.
For details on the jpcconf ha setup command, see the chapters that describes commands in the manual Job Management Partner 1/Performance Management Reference.
- 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.
An example of executing this command is as follows:
jpcconf ha list -key all
For details on the jpcconf ha list command, see the chapters that describes commands in the manual Job Management Partner 1/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 the logical host names for communications between 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-nameFor details on host names used for communications between PFM - Manager and PFM - Web Console, see the sections that describe port numbers in an appendix of the manual Job Management Partner 1/Performance Management Reference.
In addition, use the following procedure when changing IP addresses and port numbers according to the network configuration:
- 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 Job Management Partner 1/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.
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.
jpcconf port define -key all -lhost jp1-ha1
For details on setting port numbers, see the chapter describing installation and setup (in Windows) in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
For details on the jpcconf port define command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
(f) Changing the log file size
The operating status of Performance Management is output to a dedicated log file called the common message log. By default, the common message log uses two 2,048-KB files. This setting is required only if you want to change this file size.
For details, see the chapter describing installation and setup (in Windows) in the Job Management Partner 1/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.
(h) 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 Job Management Partner 1/Performance Management Planning and Configuration Guide.
(i) 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 Job Management Partner 1/Performance Management Planning and Configuration Guide.
(j) Configuring the health check function
![]()
To configure the health check function:
- 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.
When the command is executed, the setting for the health check function appears as follows:
jpcconf hc display
For details on the jpcconf hc display command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
- If the health check function is enabled: available
- If the health check function is disabled: unavailable
- 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.
For details on the jpcconf hc enable and jpcconf hc disable commands, see the chapter explaining the commands in the manual Job Management Partner 1/Performance Management Reference.
- To enable the health check function: jpcconf hc enable
- To disable the health check function: jpcconf hc disable
(k) 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.
To export the environment definitions:
- 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.
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.
jpcconf ha export -f lhostexp.conf
For details on the jpcconf ha export command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
(l) Copying the file containing the logical host environment definitions to the standby node
![]()
Copy the file that has been exported in step (f) 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.
(m) Importing the file containing the logical host environment definitions
Import the exported file copied from the executing node to the standby node.
To import the exported file containing the logical host environment definitions:
- 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.
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.
jpcconf ha import -f lhostexp.conf
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.
For details on the jpcconf ha import command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
- 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:
For details on the jpcconf ha list command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
jpcconf ha list -key all
(4) Cluster software setting procedure
Cluster software settings are required for both the executing node and the standby node.
The procedure is as follows:
(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 MSCS as examples. For PFM - Manager, register the services listed in the following table in the cluster.
Table 9-2 PFM - Manager services to be registered in the cluster software
No. Name Service name Dependencies 1 PFM - Name Server [LHOST] JP1PCMGR_PN [LHOST] IP address resources
Physical disk resources#2 PFM - Name Server [LHOST] JP1PCMGR_PN [LHOST] #1 cluster resources 3 PFM - Master Store [LHOST] JP1PCMGR_PS [LHOST] #2 cluster resources 4 PFM - View Server [LHOST] JP1PCMGR_PP [LHOST] #5 cluster resources 5 PFM - Correlator [LHOST] JP1PCMGR_PE [LHOST] #3 cluster resources 6 PFM - Trap Generator [LHOST] JP1PCMGR_PC [LHOST] #5 cluster resources 7 PFM - Action Handler [LHOST] JP1PCMGR_PH [LHOST] #3 cluster resources 8 PFM - Agent Store for HealthCheck [LHOST] JP1PCAGT_0S [LHOST] #3 cluster resources 9 PFM - Agent for HealthCheck [LHOST] JP1PCAGT_0A [LHOST] #8 cluster resources #: The shared disk drive that hosts the logical host environment directory created according to (c) in (3) above.
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 MSCS, these services are registered as MSCS resources. The settings for each resource are as follows. The setting items for MSCS are indicated by [ ].
- [Resource Type] is registered as General-Purpose Service.
- Set [Name], [Dependency], and [Service Name] as shown in Table 9-2 PFM - Manager services to be registered in the cluster software.
[Name] is the name for displaying the service, and [Service Name] is the name for specifying the service to be controlled by MSCS.
For example, when you register the PFM - Master Store [LHOST] service into the cluster software, because the PFM - Master Store [LHOST] service must have a dependent relationship with the No. 2 cluster resource, configure the PFM - Master Store [LHOST] service so that it has a dependent relationship with the PFM - Master Manager [LHOST] service.
- Do not set [Startup Parameter] and [Duplicate Registry].
- Specify the settings for the [Details] tab in Properties according to whether a failover is performed when a problem occurs in Performance Management.
For example, in order to enable failovers when problems occur in PFM - Manager, check the check boxes for [Restart] and [Apply to Group], and then set [Threshold], which indicates the number of times to attempt restarts, to 3, as a guide.
- Note
- 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
(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.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.