Job Management Partner 1/Performance Management User's Guide

[Contents][Glossary][Index][Back][Next]

9.3.3 Changing logical host names after starting operation

This subsection describes the procedures (performed on the Performance Management system) necessary for changing the host names of the PFM - Manager host, PFM - Agent host, or PFM - RM host after the Performance Management system has been configured.

To change a logical host name, you must first use the jpcconf host hostname command to change the monitoring host name.

If you execute the jpcconf host hostname command, all existing information, including definition and performance information, is inherited. For details on the jpcconf host hostname command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.

Organization of this subsection
(1) Changing the PFM - Manager logical host name
(2) Changing the PFM - Agent or PFM - RM logical host name
(3) Changing the PFM - Web Console logical host name
(4) Optional Agent-specific steps for host name changes

(1) Changing the PFM - Manager logical host name

You must work on the following hosts when changing the PFM - Manager logical host name:

The following figure shows the process flow for changing the host name.

Figure 9-18 Process flow for changing the PFM - Manager host name

[Figure]

Use the following procedure to set the display conditions (Each step corresponds to the step number in the figure above):

  1. Clear the settings for the health check agent.
    If you are using the health check function, you can delete the agent definitions for the health check agent using your PFM - Web Console browser (by deleting the definitions from the management folder in the Agents tree and removing the association between the alarm tables and the definitions). For details on how to change the agent definition, see 6. Monitoring Operations with Alarms.

  2. Stop services on the PFM - Web Console host.
    On the PFM - Web Console host connected to PFM - Manager for which you intend to change the host name, stop all Performance Management programs and services. To stop services, use the jpcwstop command.

  3. Stop services on the PFM - Agent or PFM - RM host.
    On the PFM - Agent or PFM - RM host connected to PFM - Manager for which you intend to change the host name, stop all Performance Management programs and services. To stop services, use the jpcspm stop command.

  4. Stop services on the PFM - Manager host.
    Use operations from the cluster software to stop Performance Management programs and services running on the executing node and the standby node. For details on how to stop programs and services, see the cluster software documentation.

  5. Cancel the registration of PFM - Manager from the cluster software.
    Delete the settings related to PFM - Manager on the logical host from the cluster software. For details on how to delete settings, see the cluster software documentation.

  6. Change the monitoring host name of PFM - Manager host.
    Execute the jpcconf host hostname command to change the monitoring host name.
    In the following example, the logical host name is changed from lhostA to lhostB.
     
jpcconf host hostname -lhost lhostA -newhost lhostB -d d:\backup -dbconvert convert
    For details on the jpcconf host hostname command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
    Reference note
    The directory specified with the -d option of the jpcconf host hostname command requires disk space equal to the total size of the PFM - Agent and PFM - RM Store databases on the specified host.
    For example, if PFM - Agent for Enterprise Applications and PFM - Agent for Oracle are located in the environment directory, the directory to be specified with the -d option will require disk space equal to the total size of the Store databases of the programs. You do not need to include the size of the Store database for the PFM - Manager Master Store service in the total size.

  7. Change the PFM - Manager logical host name.
    Change the PFM - Manager logical host name. Edit the settings in the hosts and jpchosts files, if necessary.

  8. Reconfigure the cluster software
    For details, see 9.2.2(4) Cluster software setting procedure.

  9. Perform any PFM - Agent-specific steps, if necessary.
    If PFM - Agent has been installed on the PFM - Manager host, the PFM - Agent-specific procedure might be necessary. The following table describes whether the PFM - Agent-specific procedure is necessary.

    Table 9-4 Whether the PFM - Agent-specific procedure is necessary

    Configuration Necessity and reference
    The version of PFM - Agent installed on the PFM - Manager host is 09-00 or later. Whether the PFM - Agent-specific procedure is necessary depends on PFM - Agent. For details on the PFM - Agent-specific procedure, see the chapters describing installation and setup in the PFM - Agent manuals.
    The version of PFM - Agent installed on the PFM - Manager host is before 09-00. The following PFM-Agent:
    • PFM - Agent for Enterprise Applications
    • PFM - Agent for Microsoft SQL Server
    		 The Agent-specific procedure is necessary. For details, see (4) Optional Agent-specific steps for host name changes.
    Other than the above (including the case where PFM - RM is installed on the PFM - Manager host) The Agent-specific procedure is not necessary.
    If a PFM - Agent-specific step is to be performed, complete the reference step shown in this table before proceeding to the next step.

  10. Start services on the PFM - Manager host.
    Use the cluster software to start all PFM - Manager services.

  11. Delete service information on the PFM - Manager host.
    Even though the PFM - Manager host name is changed, the service information of the Performance Management programs with the old host name remains the same. If you changed the PFM - Manager host name, you need to delete the old PFM - Manager service information. For example, to change the logical host name of the PFM - Manager host from lhostA to lhostB, execute the following command on the PFM - Manager host, and then delete all PFM - Manager service information from host lhostA.

    jpctool service delete -id P* -host lhostA -lhost lhostB
jpctool service delete -id 0* -host lhostA -lhost lhostB
    For details on the jpctool service delete command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.

  12. Restart services on the PFM - Manager host.
    Restart the PFM - Manager services using the cluster software to apply the deletion of the service information.

  13. Change the settings for PFM - Manager for the connection destination on the PFM - Agent or PFM - RM host.
    Change the settings for PFM - Manager for the connection destination on the PFM - Agent or PFM - RM host connected to PFM - Manager for which you have changed the logical host name. Use the jpcconf mgrhost define command to change the settings for PFM - Manager for the connection destination. For example, if the host name of PFM - Manager for the connection destination is changed to host01, specify and execute the command as follows:
      
jpcconf mgrhost define -host lhostB
    For details on the jpcconf mgrhost define command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.

  14. Start services on the PFM - Agent or PFM - RM host.
    Start the Performance Management programs and services on the PFM - Agent or PFM - RM host connected to PFM - Manager for which you have changed the logical host name. To start services, use jpcspm start command.

  15. Change PFM - Manager for the connection destination on the PFM - Web Console host.
    Change the settings for PFM - Manager for the connection destination on the PFM - Web Console host connected to PFM - Manager for which you have changed the logical host name. Change the information in the Windows initialization file (config.xml) to change the settings for PFM - Manager for the connection destination. For details, see the chapter describing installation and setup (in Windows) in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

  16. Start services on the PFM - Web Console host.
    Start the Performance Management programs and services on the PFM - Agent host connected to PFM - Manager for which you have changed the logical host name. To start services, use the jpcwstart command.

  17. Reconfigure the definition for the health check agent.
    If you have been using the health check function, reconfigure the definition (that has been cleared in step 1) of the health check agent after changing the host name.

  18. Update the alarm settings.
    In the following cases, you must update the alarm settings by using the jpctool alarm command of the PFM - Manager host or the monitoring console.
    • The action handler of the PFM - Manager host is specified for the action handler that executes actions.
      Edit the alarm to set PH1<new-pfm-manager-host-name> for the action handler that executes actions.
    • JP1 events are issued by actions.
      Set the JP1 event settings in the action again.
    For details on how to edit alarms, see 6. Monitoring Operations with Alarms.

  19. Update the JP1 system event settings.
    If either of the following conditions is met, use your PFM - Web Console browser to update the JP1 system event settings:
    • The old host name is specified as the name of the event server that connects to JP1 Base for JP1 system events.
    • The old host name is specified as the name of the monitoring console host for JP1 system events.

  20. Check whether the JP1 system event settings are properly updated.
    Check the following items after changing the logical host name:
    • Collection of performance data
      Make sure that the performance data can be collected for a period at least twice as long as the time period specified as the collection interval (Collection Interval).
    • Execution of the jpctool db dump command
      Make sure that there is no problem in outputting the collected performance data.
    • The report definitions and alarm definitions
      Make sure that there are no problems with the report definitions and alarm definitions created from the browser.
    • The actions
      Make sure that there is no problem in executing the created actions.

  21. Log on to the network management product (NNM) again if it is linked for operation monitoring.

(2) Changing the PFM - Agent or PFM - RM logical host name

You must work on the following hosts when changing the PFM - Manager or PFM - RM logical host name:

The following figure shows the process flow for changing the host name.

Figure 9-19 The process flow for changing the host name.

[Figure]

Use the following procedure to set the display conditions (Each step corresponds to the step number in the figure above):

  1. Delete the PFM - Agent or PFM - RM information.
    Use the PFM - Web Console browser to delete the agent definitions from the PFM - Agent or PFM - RM host whose logical host name will be changed (by deleting the definitions from the management folder in the Agents tree and removing the association between the alarm tables and the definitions).
    For details on how to change agent definitions, see 3. Monitoring Agents or 6. Monitoring Operations with Alarms.

  2. Stop the services on the PFM - Agent or PFM - RM host.
    Stop all Performance Management programs and services on the PFM - Agent or PFM - RM host for which you intend to change the logical host name. Use operations from the cluster software to stop Performance Management programs and the services running on the executing and standby nodes. For details on how to stop programs and services, see the cluster software documentation.

  3. Unregister PFM - Agent or PFM - RM from the cluster software.
    Delete the settings related to PFM - Agent or PFM - RM on the logical host from the cluster software. For details on how to delete settings, see the cluster software documentation.

  4. Change the monitoring host name for the PFM - Agent or PFM - RM host.
    Execute the jpcconf host hostname command to change the monitoring host name.
    In the following example, the logical host name is changed from lhostA to lhostB.
     
jpcconf host hostname -lhost lhostA -newhost lhostB -d d:\backup -dbconvert convert
    For details on the jpcconf host hostname command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
    Reference note
    The directory specified with the -d option of the jpcconf host hostname command requires disk space equal to the total size of the PFM - Agent and PFM - RM Store databases on the specified host.
    For example, if PFM - Agent for Enterprise Applications and PFM - Agent for Oracle are located in the environment directory, the directory to be specified with the -d option will require disk space equal to the total size of the Store databases of the programs. You do not need to include the size of the Store database for the PFM - Manager Master Store service in the total size.

  5. Change the PFM - Agent or PFM - RM logical host name.
    Change the PFM - Agent or PFM - RM logical host name. Edit the settings in the hosts and jpchosts files, if necessary.

  6. Configure the cluster software.
    For details, see 9.2.2(4) Cluster software setting procedure.

  7. Perform any PFM - Agent-specific steps, if necessary.
    The following table describes whether the PFM - Agent-specific procedure is necessary.

    Table 9-5 Whether the PFM - Agent-specific procedure is necessary

    Configuration Necessity and reference
    The monitoring host name to be changed is PFM - Agent version 09-00 or later. Whether the PFM - Agent-specific procedure is necessary, depends on PFM - Agent. For details on the PFM - Agent-specific procedure, see the chapters describing installation and setup in the PFM - Agent manuals.
    The monitoring host name to be changed is PFM - Agent for versions earlier than 09-00. The following PFM-Agent:
    • PFM - Agent for Enterprise Applications
    • PFM - Agent for Microsoft SQL Server
    		 The Agent-specific procedure is necessary. For details, see (4) Optional Agent-specific steps for host name changes.
    Other than the above (including the case where the monitoring host name to be changed is PFM - RM) The Agent-specific procedure is not necessary.
    If a PFM - Agent-specific step is to be performed, complete the reference step shown in this table before proceeding to the next step.

  8. Start services on the PFM - Agent or PFM - RM host.
    Start Performance Management programs and services from the cluster software on the PFM - Agent or PFM - RM host for which you have changed the logical host name.

  9. Delete service information on the PFM - Manager host.
    Even though the PFM - Agent or PFM - RM host name is changed, the service information of Performance Management programs to which the old host name is added remains the same. If you changed the PFM - Agent or PFM - RM host name, you need to delete the old PFM - Agent or PFM - RM service information. For example, to delete the information on the Agent Store service of PFM - Agent for Oracle on the lhostB, execute the following command on the PFM - Manager host:

    jpctool service delete -id OS* -host lhostB
    For details on the jpctool service delete command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.

  10. Restart services on the PFM - Manager host.
    Restart the PFM - Manager services using the cluster software to apply the changes made by the deleted service information.

  11. Delete the PFM - Agent or PFM - RM settings for the old logical host name.
    Use the PFM - Web Console browser to delete the agent definition of the PFM - Agent or PFM - RM host for which you changed the logical host name. After that, set the new definition for the agent. For details on how to change agent definitions, see 3. Monitoring Agents.

  12. Update the alarm settings.
    In the following cases, you must update the alarm settings by using the jpctool alarm command of the PFM - Manager host or the monitoring console.
    • When the action handler of the PFM - Agent or PFM - RM host is specified for the action handler that executes actions.
      Edit the alarm to set PH1<new-pfm-agent-or-pfm-rm-host-name> for the action handler that executes actions.
    • When JP1 events are issued by actions.
      Set the JP1 event settings in the action again.
    For details on how to edit alarms, see 6. Monitoring Operations with Alarms.

  13. Update the JP1 system event settings.
    If either of the following conditions is met, use your PFM - Web Console browser to update the JP1 system event settings:
    • The old host name is specified as the name of the event server that connects to JP1 Base for JP1 system events.
    • The old host name is specified as the name of the monitoring console host for JP1 system events.

  14. Check whether the JP1 system event settings are properly updated.
    Check the following items after changed the settings:
    • Collection of the performance data
      Make sure that the performance data can be collected for a period at least twice as long as the time period specified as the collection interval (Collection Interval).
    • Execution of the jpctool db dump command
      Make sure that there is no problem in outputting the collected performance data.
    • The report definitions and alarm definitions
      Make sure that there are no problems with the report definitions and alarm definitions created from the browser.
    • The actions
      Make sure that there is no problem in executing the created actions.

(3) Changing the PFM - Web Console logical host name

To change the PFM - Web Console logical host name:

  1. Stop services on the PFM - Web Console host.
    Use operations from the cluster software to stop Performance Management programs and services running on the executing node and the standby node. For details on how to stop programs and services, see the cluster software documentation.

  2. Cancel the registration of PFM - Web Console from the cluster software.
    Delete the settings related to PFM - Web Console on the logical host from the cluster software. For details on how to delete settings, see the cluster software documentation.

  3. Edit the PFM - Web Console host information in the Windows initialization file (config.xml) to refer to the new logical host name.
    This step is necessary when the logical host name has been set for the ownHost parameter in the <vsa> - <vserver-connection> tag of the Windows initialization file (config.xml).
    For details on how to edit the host information, see 9.2.3(3)(c) Setting up PFM - Web Console (logical host) and 9.2.3(3)(e) Copying the Windows initialization file (config.xml) to the executing node.

  4. If the integrated management product (JP1/IM) is linked for operation monitoring, change the host name specified in each applicable definition file or in the property value for each service.
    The location of the host name setting depends on the type of JP1 event that is used.
    For details on an integrated management product (JP1/IM), see 10. Linking with the Integrated Management Product JP1/IM for Operation Monitoring.

  5. If the network management product (NNM) is linked for operation monitoring, change the host name in the definition file.
    Change the PFM - Web Console host name specified in the NNM linkage definition file (jpcnnm.ini) to a new host name.
    For details, see 11.2.3(3) Modifying the NNM linkage definition file.

  6. Change the PFM - Web Console logical host name.

  7. Reconfigure the cluster software.
    For details on the setting procedure, see 9.2.3(4) Cluster software setting procedure.

  8. Start services on the PFM - Web Console host.
    Use operations from the cluster software to starts the PFM - Web Console services.

  9. If the integrated management product (JP1/IM) is linked, restart the product (JP1/IM).

(4) Optional Agent-specific steps for host name changes

This subsection describes the PFM - Agent-specific steps necessary to perform the following operations for each product:

For details on when it is necessary to perform these steps, see (1) Changing the PFM - Manager logical host name and (2) Changing the PFM - Agent or PFM - RM logical host name.

(a) In PFM - Agent for Enterprise Applications

Execute the jpcconf inst setup command for all created instance environments. For example, if an instance environment o246bci_SD5_00 exists in PFM - Agent for Enterprise Applications, execute the following command:

jpcconf inst setup -key agtm -inst o246bci_SD5_00 -lhost jp1-halr3

The jpcconf inst setup command is an interactive command that returns a command prompt when executed. At the ASHOST prompt, enter the new host name, and press the Enter key when the other prompts come up. If you press the Enter key at a prompt without entering a value, the existing value is assumed.

(b) In PFM - Agent for Microsoft SQL Server

Execute the jpcconf inst setup command for all created instance environments. For example, if an instance environment default exists in PFM - Agent for Microsoft SQL Server, execute the following command:

jpcconf inst setup -key agtq -inst default -lhost jp1-halSQL

The jpcconf inst setup command is an interactive command that returns a command prompt when executed. At the SQL_HOST prompt, enter the new host name, and press the Enter key when the other prompts come up. If you press the Enter key at a prompt without entering a value, the existing value is assumed.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.