Job Management Partner 1/Performance Management Planning and Configuration Guide

5.3.3 Changing the host name in a Performance Management system

This subsection describes how to change the host name in a Performance Management system. A host name that is applied to the Performance Management system is called a monitoring host name.

Reference note

The monitoring host name forms part of the service ID (that is, device name). For example, if you installed PFM - Agent for Platform (Windows) on a host whose monitoring host name is HostA, the service ID of Agent Collector is TA1HostA. If you use the product name display function, the service ID is HostA<Windows>.

By default, the real host name is used as the monitoring host name (obtained from OS with the hostname command).

For a Performance Management system existing within a physical host environment, you can set an alias name (any given host name) as the monitoring host name. This function is called the function for setting monitoring-host names.

For example, in a monitoring environment with multiple hosts sharing the same real host name, this allows you to distinguish the hosts by the alias name.

To identify the monitoring host name currently used by the Performance Management system, you must 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 : hostname

hostname : hostA

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

Table 5-10 Relationship between the monitoring host name and the method used to obtain the name

Method for acquiring a monitoring host name Monitoring host name

hostname Physical host name (displayed by using the hostname command)

alias Alias name

To set an alias name for the monitoring host name, you must execute the jpcconf host hostmode command to set alias as the method used to obtain the monitoring host name.

If you execute the jpcconf host hostmode command, all existing information, such as definition and performance information, is inherited. For details on the jpcconf host hostmode 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 monitoring host name of the PFM - Manager host

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

(3) Notes

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

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

(1) Changing the monitoring host name of the PFM - Manager host

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

PFM - Manager host

PFM - Web Console host

PFM - Agent or PFM - RM host

Monitoring console

The following figure shows the process flow.

Figure 5-5 Process flow for changing the monitoring host name of the PFM - Manager host

To change the monitoring host name of the PFM - Manager host (each step corresponds to the step number in the above figure):
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.

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

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

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 services, use the jpcspm stop command.
Change the monitoring host name of the PFM - Manager host.
Execute the jpcconf host hostmode command to change the method of acquiring a monitoring host name. To use an alias name (aliasA) to acquire a monitoring host name:
 
jpcconf host hostmode -mode alias -aliasname aliasA -d d:\backup -dbconvert convert
 
For details on the jpcconf host hostmode command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.

Reference note

The folder specified for the -d option in the jpcconf host hostmode command must have 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.
Change the settings of the jpchosts file, hosts file, and DNS, if necessary.

Perform the 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 5-11 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. The following PFM-Agent:

PFM - Agent for Enterprise Applications

PFM - Agent for Microsoft SQL Server

The Agent-specific procedure is necessary. For details on the PFM - Agent-specific procedure, see (4) Optional Agent-specific steps for host name changes.

For all other cases (including the case that PFM - RM is installed on the PFM - Manager) The 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.

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.
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 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.
Restart the services on the PFM - Manager host.
To refresh information, start the Performance Management programs and services on the PFM - Manager host. To start the services, use the jpcspm start command.
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.
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 services, use the jpcspm start command.

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 5.4.6(1)(b) Setting PFM - Manager for the connection destination.

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 services, use the jpcwstart command.

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

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.

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.

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.

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.	The following PFM-Agent: PFM - Agent for Enterprise Applications PFM - Agent for Microsoft SQL Server	The Agent-specific procedure is necessary. For details on the PFM - Agent-specific procedure, see (4) Optional Agent-specific steps for host name changes.
For all other cases (including the case that PFM - RM is installed on the PFM - Manager)	The Agent-specific procedure is not necessary.

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

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

PFM - Manager host

PFM - Web Console host

PFM - Agent or PFM - RM host

Monitoring console

The following figure shows the process flow.

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

To change the monitoring host name of the PFM - Agent or PFM - RM (each step corresponds to the step number in the above figure):
Delete the settings for PFM - Agent or PFM - RM.
Use the PFM - Web Console browser to delete the agent definition for the PFM - Agent or PFM - RM host whose name is to be changed. (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.

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 the services, use the jpcspm stop command.
Change the monitoring host name of the PFM - Agent or PFM - RM host.
Execute the jpcconf host hostmode command to change the method of acquiring a monitoring host name. The following shows an example of using an alias name (aliasA) to acquire a monitoring host name:
 
jpcconf host hostmode -mode alias -aliasname aliasA -d d:\backup -dbconvert convert
 
For details on the jpcconf host hostmode command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.

Reference note

The folder 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 Store database of each instance of PFM - Agent and PFM - RM on the specified host.

For example, if 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.
Change the settings of the jpchosts file, hosts file, and DNS, if necessary.

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

Table 5-12 PFM - Necessity of the Agent-specific procedure

Configuration Necessity and reference

The version of PFM - Agent on which the monitoring host name is changed 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 on which the monitoring host name is changed is 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 on the PFM - Agent-specific procedure, see (4) Optional Agent-specific steps for host name changes.

For all other cases (including the case that the monitoring host name of the PFM - RM host is changed.) The 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.

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

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.

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.

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.

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.

Configuration	Necessity and reference
The version of PFM - Agent on which the monitoring host name is changed 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 on which the monitoring host name is changed is 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 on the PFM - Agent-specific procedure, see (4) Optional Agent-specific steps for host name changes.
For all other cases (including the case that the monitoring host name of the PFM - RM host is changed.)	The Agent-specific procedure is not necessary.

(3) Notes

Note the following when using the function for setting monitoring-host names:

If you use an alias name, the IP address of the host must be resolved through the alias name. If you only want to resolve the IP address for the Performance Management system, use the jpchosts file to define the IP address resolution. For details on how to edit the jpchosts file, see 5.3.1 Changing the network configuration. To link the Performance Management system with other systems, you must configure the IP address to be resolved by either the hosts file or DNS definition.

If you use the function for setting monitoring-host names, depending on the type of PFM - Agent or PFM - RM, the host name output to the common message log might be different from the actual operating host name.

Even if you use the function for setting monitoring-host names immediately after installation, 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.

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

Changing the monitoring host name of the PFM - Manager host

Changing the monitoring host name of the PFM - Agent or PFM - RM host

For details on when this procedure is required, see (1) Changing the monitoring host name of the PFM - Manager host or (2) Changing the monitoring host name of the PFM - Agent or PFM - RM host.

(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 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 at the other prompts. If the Enter key is pressed 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 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 jpcconf inst setup command is an interactive command that returns a command prompt when executed. At the SQL_HOST prompt, enter a new host name, and press the Enter key at the other prompts. If the Enter key is pressed at a prompt without entering a value, the existing value is assumed.

[Contents][Back][Next]

[Trademarks]