Job Management Partner 1/Performance Management Planning and Configuration Guide

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

6.3.4 Changing the physical host name after the operation starts

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

First, identify the monitoring host name currently used by the Performance Management system. To identify the monitoring host name used by the Performance Management system, execute the following command. In this command, hostmode represents the method used to obtain the monitoring host name, and hostname represents the monitoring host name.

 
jpcconf host hostmode -display

Example
hostmode : uname
hostname : hostA

The following table describes the relationship between the monitoring host name and the method used to obtain the name.

Table 6-14 Relationship between the monitoring host name and the method to obtain the name

Method for acquiring a monitoring host name Monitoring host name
uname Physical host name (displayed by using the uname -n command)
hostname Physical host name (displayed by using the hostname command)
alias Alias name

If the method used to obtain the monitoring host name is set to alias, you do not need to perform the steps described here. This is because the monitoring host name of the Performance Management system is the alias name, even if you change the physical host name (the value displayed by either the uname -n or hostname command) of the machine.

If one of the following conditions applies, you must perform the steps described above in (1) Changing the monitoring host name of the PFM - Manager host and (2) Changing the monitoring host name of the PFM - Agent or PFM - RM host.

If you execute the jpcconf host hostname command, all existing information, such as the 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.

Note
Do not execute any other commands while executing the jpcconf host command. If you execute another command, both the jpcconf host command and the executed command might fail.
Organization of this subsection
(1) Changing the PFM - Manager host name
(2) Changing the PFM - Agent or PFM - RM host name
(3) Changing the monitored host name of PFM - RM
(4) Changing the PFM - Web Console host name
(5) Optional Agent-specific steps for host name changes

(1) Changing the PFM - Manager host name

You must perform operations on the following hosts when changing the PFM - Manager host name:

The following figure shows the process flow.

Figure 6-7 Process flow for changing the PFM - Manager host name

[Figure]

To set the display conditions (each step corresponds to the step number in the above figure):

  1. Clear the setting for the health check agent.
    If you have been using the health check function, use the PFM - Web Console browser to delete the definition for the health check agent. (To delete an agent definition, delete the agent definition from a management folder in the Agents tree, and then delete the linkage with an alarm table.) For details on the procedure for changing the agent definition, see the chapter that describes monitoring agents or the operation monitoring with alarms in the Job Management Partner 1/Performance Management User's Guide.

  2. Stop the 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 the services, use the jpcwstop command.

  3. Stop the 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 the services, use the jpcspm stop command.

  4. Stop the services on the PFM - Manager host.
    Stop all Performance Management programs and services on the PFM - Manager host for which you intend to change the host name. To stop the services, use the jpcspm stop command.

  5. Change the monitoring host name of the PFM - Manager host.
    Execute the jpcconf host hostname command to change the monitoring host name.
    To change a physical host name to hostB:
     
jpcconf host hostname -newhost hostB -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 for the -d option in the jpcconf host hostmode command must have empty disk space that is equal to or greater than the total size of the PFM - Agent and PFM - RM Store databases on the specified host.
    For example, if the health check agent, PFM - Agent for Platform, and PFM - Agent for Oracle are on the specified host, empty disk space equal to or greater than the total size of the Store databases of those agents is required. However, you do not need to include the size of Store database for the PMF - Manager Master Store service in the total size.

  6. Change the physical host name of the PFM - Manager host.
    Change the physical host name of the PFM - Manager host. Change the settings of the jpchosts file, hosts file, and DNS, if necessary. When the machine requires restarting, change the settings so that the Performance Management programs and services will not automatically start after the machine is restarted. After the PFM - Manager host operation has finished, return the settings so that the Performance Management programs and services start automatically.

  7. Perform the PFM - Agent-specific procedure, 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 6-15 PFM - Necessity of the Agent-specific procedure

    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 the installation and setup in the PFM - Agent manuals.
    The version of PFM - Agent installed on the PFM - Manager host is earlier than 09-00. When the following PFM-Agent has been installed:
    • PFM - Agent for Enterprise Applications
    • PFM - Agent for Microsoft SQL Server
    		 The PFM - Agent-specific procedure is necessary. For details on the Agent-specific procedure, see (5) Optional Agent-specific steps for host name changes.
    For all other cases (including the case that PFM - RM is installed on the PFM - Manager host) The PFM - Agent-specific procedure is not necessary.
    If the PFM - Agent-specific procedure is necessary, perform the procedure indicated in the table above, and then proceed to the following steps.

  8. Start the services on the PFM - Manager host.
    Start the Performance Management programs and services on the PFM - Manager host. To start the services, use the jpcspm start command.

  9. Delete the 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 delete all information on the PFM - Manager host (hostA), execute the following command on hostA:

    jpctool service delete -id "P*" -host hostA
jpctool service delete -id "0*" -host hostA
    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 the services on the PFM - Manager host.
    To refresh information, restart the Performance Management programs and services on the PFM - Manager host. To start the services, use the jpcspm start command.

  11. 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 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 hostB, specify and execute the command as follows:
     
jpcconf mgrhost define -host hostB
    For details on the jpcconf mgrhost define command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.

  12. Start the 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 host name. To start the services, use the jpcspm start command.

  13. Change the settings of 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 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 6.4.6(1)(b) Setting PFM - Manager for the connection destination.

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

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

  16. 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 the chapter that describes the operation monitoring with alarms in the Job Management Partner 1/Performance Management User's Guide.

  17. Update the JP1 system event settings.
    If one of the following conditions is met, you need to update the JP1 system event settings by using the PFM - Web Console browser:
    • The previous host name has been specified as the name of the event server to which JP1/Base connects.
    • The previous host name has been specified as the host name of the monitoring console for JP1 system events.

  18. Check whether the JP1 system event settings have been properly updated.
    Check the following items after changed the settings:
    • Collection of performance data
      Make sure that 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.
    • Check of the report definition and alarm definition
      Make sure that there is no problem with the report definition and alarm definition created in the browser.
    • Check of the actions
      Make sure that there is no problem in executing the created alarm actions.

  19. Log on to NNM again, if now linking with Network Node Manager (NNM) for operation monitoring.

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

You must perform operations on the following hosts when changing the PFM - Agent or PFM - RM host name:

The following figure shows the process flow.

Figure 6-8 Process flow for changing the monitoring host name of the PFM - Agent or PFM - RM host

[Figure]

To set the display conditions (Each step corresponds to the step number in the figure above):

  1. Delete the settings for PFM - Agent or PFM - RM.
    Use your PFM - Web Console browser to delete the agent definitions from the PFM - Agent or PFM - RM host whose host name is to be changed (by deleting the definitions from the management folder in the Agents tree and disassociating any alarm tables from them).
    For details on the procedure for changing the agent definition, see the chapter that describes monitoring agents or the operation monitoring with alarms in the Job Management Partner 1/Performance Management User's Guide.

  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 host name. To stop services, use the jpcspm stop command.

  3. Change the monitoring host name of the PFM - Agent or PFM - RM host.
    Execute the jpcconf host hostname command to change the monitoring host name.
    To change a physical host name to hostB:
     
jpcconf host hostname -newhost hostB -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 for the -d option in the jpcconf host hostmode command must have empty disk space that is equal to or greater than the total size of the PFM - Agent and PFM - RM Store databases on the specified host.
    For example, if the health check agent, PFM - Agent for Platform, and PFM - Agent for Oracle are on the specified host, empty disk space equal to or greater than the total size of the Store databases of those agents is required. However, you do not need to include the size of Store database for the PMF - Manager Master Store service in the total size.

  4. Change the physical host name of the PFM - Agent or PFM - RM host.
    Change the physical host name of the PFM - Manager host. Change the settings of the jpchosts file, hosts file, and DNS, if necessary. When the machine requires restarting, change the settings so that the Performance Management programs and services will not automatically start after the machine is restarted. After the PFM - Manager host operation has finished, return the settings so that the Performance Management programs and services start automatically.

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

    Table 6-16 PFM - Necessity of the Agent-specific procedure

    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 the installation and setup in the PFM - Agent manuals.
    The version of PFM - Agent installed on the PFM - Manager host is earlier than 09-00. When the following PFM-Agent has been installed:
    • PFM - Agent for Enterprise Applications
    • PFM - Agent for Microsoft SQL Server
    		 The PFM - Agent-specific procedure is necessary. For details on the Agent-specific procedure, see (5) Optional Agent-specific steps for host name changes.
    For all other cases (including the case that PFM - RM is installed on the PFM - Manager host) The PFM - Agent-specific procedure is not necessary.
    If the PFM - Agent-specific procedure is necessary, perform the procedure indicated in the table above, and then proceed to the following steps.

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

  7. 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. You need to delete the old PFM - Agent or PFM - RM service information on the PFM - Manager host. For example, to delete the information on the Agent Store service of PFM - Agent for Oracle on the PFM - Agent or PFM - RM host (hostB), execute the following command on the PFM - Manager host:
     
jpctool service delete -id "OS*" -host hostB

  8. Restart the services on the PFM - Manager host.
    Start the Performance Management programs and services on the PFM - Manager host. To start the services, use the jpcspm start command.

  9. Restart the services on the PFM - Web Console host.
    Start the Performance Management programs and services on the PFM - Web Console host connected to PFM - Manager. To start the services, use the jpcwstart command.

  10. 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 - 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.
    • JP1 events are issued by actions.
      Set the JP1 event settings in the action again.
    For details on how to edit alarms, see the chapter that describes the operation monitoring with alarms in the Job Management Partner 1/Performance Management User's Guide.

  11. Update the JP1 system event settings.
    If one of the following conditions is met, you need to update the JP1 system event settings by using the PFM - Web Console browser:
    • The previous host name has been specified as the name of the event server to which JP1/Base connects.
    • The previous host name has been specified as the host name of the monitoring console for JP1 system events.

  12. Check whether the JP1 system event settings have been properly updated.
    Check the following items the settings are changed:
    • Collection of performance data
      Make sure that 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.
    • Check of the report definition and alarm definition
      Make sure that there is no problem with the report definition and alarm definition created in the browser.
    • Check of the actions
      Make sure that there is no problem in executing the created alarm actions.

(3) Changing the monitored host name of PFM - RM

This subsection describes the procedure for changing the monitored host name of PFM - RM.

(a) If you do not change the monitored host name

You must change the monitored host name of the remote agent that corresponds to the monitoring target. Assuming that you change the monitored host name of the remote agent (instance name = inst1) from hostA to hostB, the commands are executed as follows:

To change the monitored host name of the remote agent that corresponds to the monitoring target:

  1. Execute the jpcconf target setup -key RMPlatform -inst inst1 -target hostA command.

  2. Enter Target Host:hostB.
    Follow the instructions to enter the setting items for the monitored host. When you are finished, press the Enter key to confirm the setting.

The following figure shows an example of changing the monitored host name of PFM - RM.

Figure 6-9 Example of changing the monitored host name for PFM - RM (if you do not change the monitored host name)

[Figure]

(b) If you change the monitored host name

You must re-create the remote agent that corresponds to the monitoring target.

To re-create the remote agent:

  1. Execute the jpcconf target unsetup command to delete the remote agent that corresponds to the monitoring target.

  2. Execute the jpcconf target setup command to add the remote agent with a new monitored host name.

Note that the performance data for the monitored host cannot be inherited.

The following figure shows an example of changing the monitored host name of PFM - RM.

Figure 6-10 Example of changing the monitored host name for PFM - RM (if you change the monitored host name)

[Figure]

For details on the jpcconf target setup and jpcconf target unsetup commands, see the chapter explaining the commands in the manual Job Management Partner 1/Performance Management Reference.

(4) Changing the PFM - Web Console host name

To change the PFM - Web Console host name:

  1. Stop the 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 the services, use the jpcwstop command.

  2. If you have changed the host name for communications, change the host name of the PFM - Web Console.
    You need to perform this step if the IP address used by the PFM - Web Console host cannot communicate with the PFM - Manager host, and if the host name of PFM - Web Console has been specified in the initialization file (config.xml).
    For details on how to change host names, see the sections that describe settings of host names used for communications between PFM - Manager and PFM - Web Console in the appendix of the manual Job Management Partner 1/Performance Management Reference.

  3. If the integrated management product (JP1/IM) is linked for operation monitoring, change the host name.
    Depending on the configured event, change the applicable host name to the new host name.
    • If a JP1 user event is used
      Change the host name in the definition files for the tool launcher and for opening monitor windows.
    • If a JP1 system event is used
      Change the Monitoring Console Host property setting of JP1 Event Send Host to the new host name.
    For details on an integrated management product (JP1/IM), see the chapter that describes the linkage with the integrated management product JP1/IM for operation monitoring in the Job Management Partner 1/Performance Management User's Guide.

  4. If the network management product (NNM) is linked for operation monitoring, change the host name.
    Change the host name of the PFM - Web Console in jpcnnm.ini file to the new host name.
    For details on a network management product (NNM), see the chapter that describes the linkage with Network Node Manager (NNM) for operation monitoring in the Job Management Partner 1/Performance Management User's Guide.

  5. Change the PFM - Web Console physical host name.
    Change the PFM - Web Console physical host name. When the machine requires restarting, change the settings so that the Performance Management programs and services will not automatically start after the machine is restarted. After the PFM - Web Console host operation has finished, return the settings so that the Performance Management programs and services start automatically.

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

  7. Restart the integrated management product (JP1/IM), if linking with JP1/IM.

(5) 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 the situation which needs this procedure, see (1) Changing the PFM - Manager host name or (2) Changing the PFM - Agent or PFM - RM host name.

(a) In PFM - Agent for Enterprise Applications

Execute the jpcconf inst setup command for all the 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

The interactive jpcconf inst setup command returns a prompt that requests you to enter a value. In this case, enter a new host name in ASHOST, leave other items blank, and press the Enter key. If you do not enter a value and press the Enter key, the setting prior to executing the command is used.

(b) In PFM - Agent for Microsoft SQL Server

Execute the jpcconf inst setup command for all the 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

The interactive jpcconf inst setup command returns a prompt that requests you to enter a value. In this case, enter a new host name in SQL_HOST, leave other items blank, and press the Enter key. If you do not enter a value and press the Enter key, the setting prior to executing the command is used.

[Contents][Back][Next]

[Trademarks]

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