This subsection describes the setup required to operate Performance Management in a cluster system.
To add PFM - Agent for Service Response to an existing Performance Management system, you must perform setup to register PFM - Agent for Service Response.
You use PFM - Manager and PFM - Web Console to register PFM - Agent for Service Response.
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 Service Response, see H. Version Compatibility.
The procedure for doing so is the same as for a non-cluster system. For details about this procedure, see 2.1.4 PFM - Agent for Service Response setup procedure.
You must set up a logical host environment for PFM - Agent for Service Response on the executing node.
Make sure that the shared disk is online. If it is not online, bring it online using a cluster software operation or volume manager operation.
Execute the jpcconf ha setup (jpchasetup create) command to create a logical host environment. This command creates a logical host environment by copying necessary data to the shared disk and setting definitions for a logical host.
To set up a logical host environment for PFM - Agent for Service Response:
jpcconf ha setup -key SR -host jp1-halsr -d S:\jp1 (jpchasetup create agtv -lhost jp1-halsr -d S:\jp1)
jpcconf ha list -key all (jpchasetup list all)
Execute the jpcconf mgrhost define (jpcnshostname) command to set the PFM - Manager that manages PFM - Agent for Service Response. When the version of PFM - Manager is 09-00 or later, you do not need to perform the procedure explained here, because PFM - Agent for Service Response is automatically registered.
To set the connection-target PFM - Manager:
jpcconf mgrhost define -host jp1-hal -host jp1-halsr (jpcnshostname -s jp1-hal -lhost jp1-halsr)
For the start options for cluster operation, change the settings of the Probe action condition definition file.
Table 5-3 Shared file storage folders
Type of shared file | Shared file storage folder |
---|---|
Report file | folder-on-shared-disk\jp1pc\agtv\probe\report |
Temporary report file | folder-on-shared-disk\jp1pc\agtv\probe\tmp |
Measurement condition registration file | folder-on-shared-disk\jp1pc\agtv\probe\task\esp |
T:\shdsk\jp1pc\agtv\probe\report
T:\shdsk\jp1pc\agtv\probe\tmp
T:\shdsk\jp1pc\agtv\probe\task\esp
For details about setting other start options, see 2.1.4 PFM - Agent for Service Response setup procedure. For details about the Probe action condition definition file, see 7.2 Probe action condition definition file (esp.conf).
If you use the IE Recorder to define the IE scenarios, define the IE Recorder action condition definition file (jpcvierec.conf). For details about the IE Recorder action condition definition file, see 7.8 IE Recorder action condition definition file (jpcvierec.conf).
If you use the Web Recorder to define the Web transactions, define the Web Recorder action condition definition file (wr.conf). For details about the Web Recorder action condition definition file, see 7.9 Web Recorder action condition definition file (wr.conf).
If you use the user-defined commands, define the command registration file (espcommand.xml). For details about the command registration file, see 7.6 Command registration file (espcommand.xml).
The following shows the procedure for setting the log-on account for the Extensible Service IE Probe service on a logical host.
If you have other PFM - Manager or PFM - Agent programs to be set up on the same logical host in addition to PFM - Agent for Service Response, set them up at this stage.
For details about the setup procedure, see the chapter that describes operations in a cluster system in the Job Management Partner 1/Performance Management User's Guide, or in the applicable PFM - Agent manual.
These settings are required only when the Performance Management programs run in a network environment that uses a firewall. If you establish communication between Performance Management programs via a firewall, use the jpcconf port (jpcnsconfig port) command to set the port numbers.
For details about how to set port numbers, see the chapter that describes installation and setup, and the chapter that describes construction and operations in a cluster system, in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
You must also set the IP addresses if you will be specifying IP addresses in operating Performance Management in a network environment connected to multiple LANs. To do this, directly edit the contents of the jpchosts file.
For details about how to set IP addresses, see the chapter that describes installation and setup for Windows in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
Performance Management's operating status is output to a log file unique to Performance Management. This log is called the common message log; it consists of two files with a default size of 2,048 kilobytes each. This setting is required only when you wish to change this file size.
For details, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
Perform this setting only if you want to change the folder where the database of performance data managed by PFM - Agent is saved, backed up, exported, or imported.
For details, see 2.4.1 Changing the performance data storage destination.
This setting is required to output action log when alarm occur. 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 I. Outputting Action Log Data.
After you have created a logical host environment for PFM - Agent for Service Response, you must export the environment definition to a file. This export processing involves output of the definition information for the Performance Management program set up on the logical host to a file in the batch mode. If you are setting up other Performance Management programs on the same logical host, export the environment definitions after all setup processes have been completed.
To export the logical host environment definition:
jpcconf ha export -f lhostexp.txt (jpchasetup export -f lhostexp.txt)
Copy the logical host environment definition file exported in (k) Exporting the logical host environment definition from the executing node to the standby node.
Using a cluster software operation or volume manager operation, take the shared disk offline to complete the task. If you plan to continue using the shared disk, there is no need to take it offline.
Set up a logical host environment for PFM - Agent for Service Response on the standby node.
Import the export file that was copied from the executing node to the standby node.
To specify settings for executing at the standby node the Performance Management program on the logical host created at the executing node, use the jpcconf ha import (jochasetup import) command. If multiple Performance Management programs have been set up on a single logical host, the settings for all the programs are imported in the batch mode.
When executing this command, there is no need to keep the shared disk in online status.
To import the logical host environment definition:
jpcconf ha import -f lhostexp.txt (jpchasetup import -f lhostexp.txt)
jpcconf ha list -key all (jpchasetup list all)
You must copy from the executing node to the standby node the definition files created in (2)(d) Setting up the start options for PFM - Agent for Service Response.
Perform the procedure shown in (2)(e) Setting the log-on account for the service on the standby node.
To run a Performance Management program in a logical host environment, you must register the program in the cluster software and set up the environment in such a way that the Performance Management program starts and terminates from the cluster software.
This subsection describes the settings for registering PFM - Agent for Service Response in the cluster software.
This subsection describes the settings for registering PFM - Agent for Service Response in the cluster software.
For PFM - Agent for Service Response, you register in the cluster software the services listed in the table below.
Table 5-4 PFM - Agent for Service Response services to be registered in the cluster software
No. | Name | Service name | Dependency |
---|---|---|---|
1 | PFM - Agent Store for ServiceResponse [LHOST] | JP1PCAGT_VS [LHOST] | IP address resource Physical disk resource |
2 | PFM - Agent for ServiceResponse [LHOST] | JP1PCAGT_VA [LHOST] | Cluster resources listed in row 1 above. |
3 | PFM - Action Handler [LHOST] | JP1PCMGR_PH [LHOST] | IP address resource Physical disk resource |
4 | Extensible Service IE Probe | JP1PCVIE#1, #2 | IP address resource Physical disk resource |
5 | Extensible Service Probe | JP1ESP#1, #3, #4 | IP address resource Physical disk resource |
Replace LHOST with the logical host name. For example, if the logical host name is jp1-halsr, the service is PFM - Agent Store for Service Response [jp1-halsr], and the service name is JP1PCAGT_VS [jp1-halsr].
In the case of MSCS, you must register these services as MSCS resources. Set each resource as follows. Bold type indicates an MSCS setting:
Make sure that the Performance Management programs function normally by starting and terminating the programs from the cluster software on each node.
When you have finished setting up the Performance Management programs, set up an environment for them so that PFM - Web Console can be used to display monitored program operating status reports as appropriate to the operations, and so that it can send notifications to the user in the event of a problem on a monitored program.
For details about how to set up an environment for the Performance Management programs, see the chapter that describes construction and operation in a cluster system in the Job Management Partner 1/Performance Management User's Guide.