10.2.3 Installing and setting up PFM - Web Console

(a) Registering agent information in PFM - Web Console

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 - Web Console for the executing node and the standby node.

If PFM - Agent or PFM - RM is already registered in PFM - Web Console, 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 the following condition applies, manually register PFM - Agent or PFM - RM in PFM - Web Console:

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

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 additional setup for agent information in PFM - Web Console takes place where shown in Figure 10-13 Process flow for installation and setup of PFM - Web Console used on a logical host.

To register the agent information in PFM - Web Console:

1. Copy the setup file.

   Copy the PFM - Agent or PFM - RM setup files to the following locations on the PFM - Web Console executing and standby nodes.

   pfm - web console-installation-folder\setup\

   The setup file to be copied and the relevant procedure are the same as for when an additional setup is performed for PFM - Manager. For details, see the chapter describing installation and setup (in Windows) in the JP1/Performance Management Planning and Configuration Guide.

2. Execute the setup command on the standby node.

   Execute the jpcwagtsetup command on the standby node, and register the agent information.

   Execute the command as follows:

   jpcwagtsetup

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

Supplemental information:

When you register the agent information of PFM - Agent or PFM - RM in PFM - Web Console, you must restart PFM - Web Console. However, the restart after step 2 is not required because PFM - Web Console restarts when a failover occurs.

(b) Setting up PFM - Manager for the connection destination (logical host)

On the standby node, set the IP address and host name for PFM - Manager to which PFM - Web Console connects in the Windows initialization file (config.xml).

Specify the IP address or the host name of the PFM - Manager to connect to in host in the <vserver-connection> tag under the <vsa> tag. If the PFM - Manager to connect to is running on a cluster system, specify the logical IP address or the logical host name.

For details about the initialization file (config.xml), see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(c) Setting up PFM - Web Console (logical host)

Set the logical IP address or logical host name for PFM - Web Console in the Windows initialization file (config.xml) on the standby node.

Specify the logical IP address or the logical host name of the PFM - Web Console host in host in the <vserver-connection> tag under the <vsa> tag.

For details about the initialization file (config.xml), see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(d) Setting up the storage location for bookmark definition information

Set the folder to store the bookmark definition information in the Windows initialization file (config.xml) on the standby node.

Specify the folder for storing bookmark definition information in bookmarkRepository in the <bookmark> tag under the <vsa> tag. Specify a folder on the shared disk to ensure that the information is inherited if a failover occurs.

For details about the initialization file (config.xml), see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(e) Setting the storage location for process monitoring definition templates

Set the storage folder for process monitoring definition templates in the initialization file (config.xml) on the standby node.

Specify the folder for storing bookmark definition information in processMonitoringTemplatesRepository in the <process-monitoring> tag under the <vsa> tag. Specify a folder on the shared disk to ensure that the information is inherited if a failover occurs.

For details about the initialization file (config.xml), see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(f) Setting usrconf.cfg

If the language setting of the system locale differs from that of the usrconf.cfg file, change the setting of the usrconf.cfg file on the standby node.

If the system locale has been changed since passwords were set, check and, if necessary, revise the settings in the usrconf.cfg file.

For details about the option definition file (usrconf.cfg), see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(g) Setting encrypted communication between a web browser and the monitoring console server

If you will be using encrypted communication between a web browser and the monitoring console server, specify the settings in both PFM - Web Console and the web browser. For details, see the section on changing the settings for encrypted communication between a web browser and the monitoring console server in the JP1/Performance Management Planning and Configuration Guide.

(h) Copying the settings file to the executing node

Copy the Windows initialization file (config.xml) edited in (b), (c), (d), and (e) to the executing node.

Copy the file to the following location on the executing node:

installation-folder\conf

If the settings of the usrconf.cfg file on the standby node were changed in (f), you need to copy the file to the executing node. Copy the file to the following location on the executing node:

Installation folder\CPSB\CC\server\usrconf\ejb\PFMWebConsole

(i) Make sure the shared disk is online

Make sure that the shared disk is online on the execution node. If the shared disk is not online, place it online through the operation of the cluster software and the volume manager.

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

Use the setup files copied in (a) to perform an additional setup of the agent information for PFM - Agent or PFM - RM on the execution node.

1. Stop the PFM - Web Console services on the executing node.

   Use the jpcwstop command to stop the services if the PFM - Web Console services are not registered with the cluster software.

   When making changes to the Performance Management configuration such as adding PFM - Agent or PFM - RM after the services are registered with the cluster software, use the cluster software to stop the services. For details on changing the configuration of the cluster system, see 10.3 Changing the cluster system configuration (in Windows).

2. Execute the setup command on the executing node.

   Execute the command as follows:

   jpcwagtsetup

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

3. Start the PFM - Web Console service on the executing node.

   Start the PFM - Web Console services stopped in step 1.

(a) Registering PFM - Web Console in the cluster software

To use PFM - Web Console in a logical host environment, register it in the cluster software, and then set the cluster software to control the starting and stopping of PFM - Web Console.

The setting contents for registering PFM - Web Console in the cluster software are described below by using items for registration in Windows WSFC as examples. For PFM - Web Console, perform an additional registration of the services listed in the following table in the same cluster group as for PFM - Manager.

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

• Register resources as General-Purpose Service.

• Set [Name], [Service Name], and [Dependency] with reference to Table 10-4 PFM - Web Console 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 WSFC.

• Starting and stopping a service that is registered in the cluster are controlled by the cluster software. To prevent services from being started automatically when the OS starts, set Startup type to Manual on both the executing node and the standby node.

• Do not set [Duplicate Registry].

• On the Policies tab in Properties, select the If resource fails, attempt restart on current node check box. As a guideline, specify 3 in Maximum restarts in the specified period.

  Important

  • When you configure WSFC, use Failover Cluster Management and the cluster command provided by the cluster software. For details, see the documentation provided by Microsoft.

    1. Create the clustered PFM - Web Service service.

    Choose Failover Cluster Management in the Start menu to start the cluster software, and then create a clustered PFM - Web Service. Add the generic service (the PFM - Web Service), a client access point (Name, IP address), storage, and other resources to move between nodes when a failover occurs. Display the properties for each item, and set the resource dependencies and other cluster-related settings.

    2. Execute the cluster command.

    Open the command prompt as an administrator, and execute the following command:

    clusterΔresΔ"resource-name"Δ/privΔStartupParameters=""

    Δ represents a space. As resource-name, specify the resource name of the generic PFM - Web Service service. You can find out the resource name of the generic service in the Failover Cluster Management tool.

    3. Check the value in Setup parameters.

    From Failover Cluster Management, open the Properties page for the generic PFM - Web Service service, and make sure that the Setup parameters field is empty.

(b) Checking starting and stopping from the cluster software

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