6.3.4 Setup

(a) Bringing the shared disk online

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.

(b) Setting up a logical host environment for PFM - Agent for Service Response

Execute the jpcconf ha setup 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:

1. Execute the jpcconf ha setup command to create a logical host environment.

   Execute the command as follows:

   jpcconf ha setup -key SR -host jp1-halsr -d S:\jp1

   Use -lhost to specify the logical host name. This example specifies jp1-halsr as the logical host name. If you use DNS, specify the logical host name without the domain name.

   Specify for the environment folder name in -d the name of a folder on the shared disk. For example, if -d S:\jp1 is specified, S:\jp1\jp1pc is created and then files for the logical host environment are created.

2. Execute the jpcconf hea list command to check the logical host settings.

   Execute the command as follows:

   jpcconf ha list -key all

   Make sure that the created logical host environment is valid.

(c) Setting up PFM - Manager for the connection destination of PFM - Agent for Service Response

Execute the jpcconf mgrhost define 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:

1. Execute the jpcconf mgrhost define command to set the connection-target PFM - Manager.

   Execute the command as follows:

   jpcconf mgrhost define -host jp1-hal -host jp1-halsr

   Specify the host name of the connection-target PFM - Manager in the -host option. If the connection-target PFM - Manager runs on a logical host, specify the logical host name of the connection-target PFM - Manager in the -host option. This example specifies jp1-hal as the PFM - Manager's logical host name.

   Use -lhost to specify the logical host name of PFM - Agent for Service Response. This example specifies jp1-halsr as the logical host name of PFM - Agent for Service Response.

   Although the above example shows interactive execution, you can also execute the jpcconf mgrhost define command non-interactively. For details about the jpcconf mgrhost define command, see the chapter that explains the commands in the manual JP1/Performance Management Reference.

(d) Setting up the start options for PFM - Agent for Service Response

For the start options for cluster operation, change the settings of the Probe action condition definition file.

1. Set the shared folder in shared_directory in the [Cluster] section of the Probe action condition definition file.

   Because PFM - Agent for Service Response shares information during switchover between the executing and standby systems, creates the files shown in the table below under the shared file storage folder.

   Table 6‒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

   The following describes the notes on shared file storage folder.

   • The required folders must have been created in advance under the folder on the shared disk.

   • The files related to the measurement condition registration file (esptask.dtd, esptask.xml) under installation-folder\agtv\probe\task\esp must have been copied in advance to the folder on the shared disk.

   Note:

   You can copy the related files to the measurement condition registration file (esptask.dtd, esptask.xml) to the folder on the shared disk, after setting up a logical host environment.

   • If you perform either of the following operations, the measurement condition registration file is created under the folder on the shared disk.

     - To specify the measurement condition on PFM - Web Console

     - To perform the simplified registration of IE scenario on the IE Recorder

   • If you edit the measurement condition registration file directly, edit the file on the physical host and then copy to the folder on the shared disk, or edit the measurement condition registration file on the shared disk directly.

   You must specify both of the following settings in the [Cluster] section of the Probe action condition definition file (esp.conf).

   • To specify the path corresponding to folder-on-shared-disk in the above table as the value of the shared_directory

   • To specify Y as the value of the cluster_flag

   The following shows an example of the configuration under the directory on the shared disk. In this example, you must specify T:\shdsk in shared_directory in the [Cluster] section of the Probe action condition definition file.

   Example: Specify T:\shdsk as the folder on the shared disk:

       T:\shdsk\jp1pc\agtv\probe\report
       T:\shdsk\jp1pc\agtv\probe\tmp
       T:\shdsk\jp1pc\agtv\probe\task\esp

2. Set Y as the value of the ie_service_flag in the [General] section of the Probe action condition definition file.

   If you measure the IE scenario, you must define this item.

   Note:

   When you upgrade PFM - Agent for Service Response, the Probe action condition definition file does not have the ie_service_flag entry in the [General] section. Add and set the ie_service_flag in the file.

For details about setting other start options, see 3.1.4 PFM - Agent for Service Response setup procedure. For details about the Probe action condition definition file, see 8.2 Probe action condition definition file (esp.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 8.4 Web Recorder action condition definition file (wr.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 8.8 IE Recorder action condition definition file (jpcvierec.conf).

If you use the user-defined commands, define the command registration file (espcommand.xml). For details about the command registration file, see 8.6 Command registration file (espcommand.xml).

(e) Setting the log-on account for the service

The following shows the procedure for setting the log-on account for the Extensible Service IE Probe service on a logical host.

1. From the Start menu of Windows, choose Settings, Control Panel, Administrative Tool, and then Services.

2. Select Extensible Service IE Probe service, from the Action menu, choose Properties, then the Properties of Extensible Service IE Probe dialog box appears.

3. Click the This account button on the Log On tab, then the Browse button is activated.

4. Specify a user account^# that executes the service in the Account text box. Click the Browse button, and you can specify the user account in the Select User dialog box.

   #

   Specify the user account that executes the service is the same as the account for measurement that you use to check replaying the operations in the IE Recorder.

5. Enter the password in the Password and Confirm password text boxes, and then click the OK button.

(f) Setting up the logical host environments of other Performance Management programs

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 JP1/Performance Management User's Guide, or in the applicable PFM - Agent manual.

(g) Setting up a network

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 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 JP1/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 JP1/Performance Management Planning and Configuration Guide.

Note:

Once you have edited the jpchosts file, copy it from the executing node to the standby node.

(h) Changing the log file size

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 JP1/Performance Management Planning and Configuration Guide.

(i) Changing the performance data storage destination

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 3.4.1 Changing the performance data storage destination.

(j) Setting up the action log

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.

(k) Exporting the logical host environment definition

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:

1. Execute the jpcconf ha export command to export the logical host environment definition.

   Output to an export file the definition information for the logical host environment that has been created so far. You can assign any name to the export file.

   For example, to export the logical host environment definition to the lhostexp.txt file, execute the following command:

   jpcconf ha export -f lhostexp.txt

   Although the above example shows interactive execution, you can also execute the jpcconf ha export command non-interactively. For details about the jpcconf ha export command, see the chapter that explains the commands in the manual JP1/Performance Management Reference.

(l) Copying the logical host environment definition file to the standby node

Copy the logical host environment definition file exported in (k) Exporting the logical host environment definition from the executing node to the standby node.

(m) Taking the shared disk offline

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.

(a) Importing the logical host environment definition

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 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:

1. Execute the jpcconf ha import command to import the logical host environment definition.

   Execute the following command:

   jpcconf ha import -f lhostexp.txt

   Although the above example shows interactive execution, you can also execute the jpcconf ha import command non-interactively. For details about the jpcconf ha import command, see the chapter that explains the commands in the manual JP1/Performance Management Reference.

   This command changes settings in such a way that the environment for the standby node becomes the same as in the export file. As a result, setup is performed for starting PFM - Agent for Service Response on the logical host.

   If fixed port numbers were set by the jpcconf port command during setup, they are also set in the same manner.

2. Execute the jpcconf ha list command to check the logical host settings.

   Execute the command as follows:

   jpcconf ha list -key all

   Make sure that the displayed information is the same as when jpcconf ha list command is executed at the executing node.

(b) Copying the definition files for PFM - Agent for Service Response

You must copy from the executing node to the standby node the definition files created in (3)(d) Setting up the start options for PFM - Agent for Service Response.

1. Copy from the executing node to the standby node the Probe action condition definition file (esp.conf).

   installation-folder\agtv\probe\conf

2. If you define the Web transactions, copy from the executing node to the standby node the Web Recorder action condition definition file (wr.conf) and the Web transaction files.

   installation-folder\agtv\probe\conf

   installation-folder\agtv\probe\webtrans

3. If you define the IE scenarios, copy from the executing node to the standby node the IE Recorder action condition definition file (jpcvierec.conf) and the IE scenario files.

   installation-folder\agtv\probe\conf

   installation-folder\agtv\probe\iescena

4. If you use the user-defined commands, copy from the executing node to the standby node the command registration file (espcommand.xml) and user-defined commands.

   installation-folder\agtv\probe\conf

   installation-folder\agtv\probe\user

5. If you register the passwords, copy from the executing node to the standby node the password file (esp.pdb).

   installation-folder\agtv\probe\passwd

6. If you want to apply server authentication and client authentication for HTTPS measurement, copy the certificate file to the standby node.

(c) Setting the log-on account for the service

Perform the procedure shown in (3)(e) Setting the log-on account for the service on the standby node.

(a) 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.

Important

For details about dependency settings when using a logical host for PFM - Manager in a cluster system, see the chapter that describes construction and operation in a cluster system in the JP1/Performance Management User's Guide.

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].

For WSFC, register these services as WSFC resources. Set each resource as follows:

• In Resource Type, register the resource as Generic Service.

• Set Dependencies as shown in Table 6-4.

• Do not set Startup parameters or Registry Replication.

• Set the Policies tab in Properties by taking into account whether you want a failover to occur in the event of a Performance Management program failure.

  For example, to trigger a failover when a failure occurs in PFM - Agent for Service Response, set the Policies tab as follows:

  • Select the If resource fails, attempt restart on current node radio button.

  • Select the If restart is unsuccessful, fail over all resources in this service or application check box^#.

  • In principle, set Maximum restarts in the specified period: to 3.

  #

  In the case of Windows Server 2012 or later, the If restart is unsuccessful, fail over all resources in this Role check box is used instead.

Note:

A service registered in the cluster is started and stopped from the cluster. Set Startup type to Manual so that the service will not be started automatically during OS startup. Immediately after setup is performed by the jpcconf ha setup command, the service is set to Manual.