10.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 JP1/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 PFM - Agent-specific steps for host name changes

(1) Changing the PFM - Manager logical host name

(a) Overview of changing the PFM - Manager logical host name

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

PFM - Manager host
PFM - Web Console host
PFM - Agent or PFM - RM host
Monitoring console

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

Before performing this task in a system that links with JP1/SLM, refer to 13.4.1 Changing host names after linking with JP1/SLM.

Figure 10‒18: Changing the PFM - Manager logical host name

(b) Procedure for changing the PFM - Manager logical host name

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

Suspend monitoring for the PFM - Manager host whose host name is to be changed.

If you do not want health check events to occur while changing the host name, suspend monitoring for the host whose name is to be changed. You can do so by using the jpctool monitor suspend command of the PFM - Manager host or from the monitoring console.

For details on suspending monitoring, see 8. Suspending and Resuming Monitoring.
Suspend monitoring with the new host name specified.

If you suspend monitoring in step 1, you also need to suspend monitoring with the new host name specified.

In this case, use the -force option of the jpctool monitor suspend command of the PFM - Manager host.
Delete 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 (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.
Delete the settings for PFM - Agent or PFM - RM.

You can use the PFM - Web Console to delete the agent definitions for the logical PFM - Agent host or logical PFM - RM host installed on the same host as the PFM - Manager whose logical host name is to be changed. This involves deleting the definitions from the management folder in the Agents tree and removing the association between the alarm tables and the definitions. For details about how to change agent definitions, see 3. Monitoring Agents and 6. Monitoring Operations with Alarms.
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.
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.
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.
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.
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 JP1/Performance Management Reference.

Note

As a general rule, the directory specified in the -d option of the jpcconf host hostname command requires disk space equivalent to the total size of the PFM - Agent and PFM - RM Store databases and the import directory on the specified host. If you have made changes to the storage directory or import directory of the Store database, calculate the disk space requirements with reference to the size of the database in the new location.

For example, if PFM - Agent for HiRDB and PFM - Agent for Oracle are located in the environment directory, the directory must have free disk space equivalent to the size of the Store databases in the environment directory plus the size of the database in the import directory. You do not need to include the size of the Store database for the PFM - Manager Master Store service in the total size.
Change the PFM - Manager logical host name.

Change the PFM - Manager logical host name.
Edit the settings in the hosts and jpchosts files so that the new host name can be resolved to an IP address in the Performance Management system, if necessary.
Export the environment definition file of the logical host.

Supplemental information:

Apply the setting information of the active node to the passive node. First, export the environment definitions of the logical host of the active node to a file.

Execute the jpcconf ha export command to export the environment definitions of the logical host to a file of your choice.

For example, to export the environment definition of the logical host to the file lhostexp.conf, execute the following command.
```
jpcconf ha export -f lhostexp.conf
```
Note that, if the health check functionality is enabled in PFM - Manager of the logical host environment to be exported, information about the health check agent will be exported because the health check agent is already set up on the logical host.

In this example, the jpcconf ha export command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf ha export command, see the chapter on commands in the manual JP1/Performance Management Reference.
Copy the environment definition file of the logical host to the standby node.

To apply the contents of the file exported in step 12 to the standby node, copy the file from the active node to the standby node.
Import the environment definition file of the logical host.

Supplemental information:

Import the export file copied from the active to the standby node.

Execute the jpcconf ha import command to import the environment definitions of the logical host to the standby node.

For example, if the name of the export file is lhostexp.conf, execute the following command:
```
jpcconf ha import -f lhostexp.conf
```
Executing the command jpcconf ha import will change the environment definitions of the standby node to match those of the active node. Doing this will change the settings so that PFM - Manager can be started via operations on the logical host.

Note that, if the health check functionality is enabled in PFM - Manager of the logical host environment to be imported, information about the health check agent will be imported because the health check agent is already set up on the logical host.

In this example, the jpcconf ha import command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf ha import command, see the chapter on commands in the manual JP1/Performance Management Reference.
Check the settings of the logical host environment.

In the same way as on the active node, check the settings of the logical host by executing the command jpcconf ha list.

The procedure is as follows:
```
jpcconf ha list -key all
```
For details on the jpcconf ha list command, see the chapter on commands in the manual JP1/Performance Management Reference.
Reconfigure the cluster software.

For details, see 10.2.2(4) Cluster software setting procedure.

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 10‒5: 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 earlier than 09-00.	The following PFM - Agents: PFM - Agent for Cosminexus PFM - Agent for Domino PFM - Agent for Enterprise Applications PFM - Agent for Microsoft SQL Server	The PFM - Agent-specific procedure is necessary. For details about the procedure, see 10.3.3(4) Optional PFM - Agent-specific steps for host name changes.
	Other than the above	The PFM - 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.

Start services on the PFM - Manager host.

Use the cluster software to start all PFM - Manager services.
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. Therefore, you need to delete unnecessary information.

The types of service information that you need to delete and the method of checking the service information are described as follows:

Service information on the host with the old host name

All the items that are displayed by executing the following command must be deleted:
```
jpctool service list -id * -host old-host-name -lhost new-host-name
```
Service information whose service ID contains the old host name

Items whose Service ID column contains the old host name of the items that are displayed by executing the following command must be deleted:
```
jpctool service list -id * -lhost new-host-name
```
Service information can be deleted by using the jpctool service delete command.

Delete service information on the host with the old host name by using the following command:
```
jpctool service delete -id * -host old-host-name -lhost new-host-name
```
Additionally, delete service information whose service ID contains the old host name by using the following command:
```
jpctool service delete -id ???old-host-name -host new-host-name -lhost new-host-name
```
If the message KAVE05233-W is issued during command execution because of a service information deletion error, re-execute the command as follows:
```
jpctool service delete -id * -host old-host-name -lhost new-host-name -force
jpctool service delete -id ???old-host-name -host new-host-name -lhost new-host-name -force
```
Note

Even though you execute the jpctool service list command, old service information that contains the old host name might not be displayed. Because such service information also needs to be deleted from the database, you must execute the jpctool service delete command shown above.

For details on the commands, see the chapter that describes the commands in the manual JP1/Performance Management Reference.
Apply the service information to PFM - Manager.

Synchronize the service information between PFM - Manager and PFM - Web Console so that the deletion takes effect in PFM - Web Console. To synchronize the service information, use the jpctool service sync command.

The time when the service information synchronized by the jpctool service sync command takes effect depends on the version of PFM - Web Console. For details about the jpctool service sync command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
Change the business group configuration if needed.

If the PFM - Manager host whose logical host name you changed is assigned to a business group, you need to change the configuration of the business group. For details on how to do this, see 2. Managing User Accounts and Business Groups.
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.

(Specify the same settings on the physical host of both the executing and standby nodes of the PFM - Manager environment.)

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
```
In this example, the jpcconf mgrhost define command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf mgrhost define command, see the chapters that describe commands in the manual JP1/Performance Management Reference.
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.
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 JP1/Performance Management Planning and Configuration Guide.
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.
Reconfigure the definition for the health check agent.

If you have been using the health check function, reconfigure the definition (that was deleted in step 3) of the health check agent after changing the host name.
Reconfigure the definition of PFM - Agent or PFM - RM.

Reconfigure the definition (that was deleted in step 4) of the logical PFM - Agent or logical PFM - RM installed on the same host as PFM - Manager for which the logical host name was changed.
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.
Update the JP1 system event settings.

If either of the following conditions is met, use your PFM - Web Console 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.
For details on the JP1 system events, see 12.2 JP1 events issued from Performance Management to JP1/IM.
Resume monitoring with the old host name specified.

If you suspend monitoring in step 1, you need to resume monitoring with the old host name specified to delete the settings information of monitoring suspension for the old host name.

In this case, use the -force option of the jpctool monitor resume command of the PFM - Manager host.
Resume monitoring for the PFM - Manager host whose host name was changed.

If you suspend monitoring in step 2, use the jpctool monitor resume command of the PFM - Manager host or use the monitoring console to resume monitoring on the PFM - Manager host.
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 jpcrpt 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 Web browser.
- The actions
  
  Make sure that there is no problem in executing the created actions.

To Page Top

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

(a) Overview of 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:

PFM - Manager host
PFM - Agent or PFM - RM host
Monitoring console

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

Before performing this task in a system that links with JP1/SLM, refer to 13.4.1 Changing host names after linking with JP1/SLM.

Figure 10‒19: Changing the logical host name of PFM - Agent or PFM - RM

(b) Procedure for changing the PFM - Agent or PFM - RM logical host name

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

Suspend monitoring for the PFM - Agent or PFM - RM host whose host name is to be changed.

If you do not want health check events to occur while changing the host name, suspend monitoring for the host whose name is to be changed. You can do so by using the jpctool monitor suspend command of the PFM - Manager host or from the monitoring console.

In a multiple-monitoring configuration, perform this step on the primary manager.

For details on suspending monitoring, see 8. Suspending and Resuming Monitoring.
Suspend monitoring with the new host name specified.

If you suspend monitoring in step 1, you also need to suspend monitoring with the new host name specified.

In this case, use the -force option of the jpctool monitor suspend command of the PFM - Manager host.

In a multiple-monitoring configuration, perform this step on the primary manager.
Delete the PFM - Agent or PFM - RM information.

Use the PFM - Web Console 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).

In a multiple-monitoring configuration, perform this step on the primary manager.

For details on how to change agent definitions, see 3. Monitoring Agents or 6. Monitoring Operations with Alarms.
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.
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.
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
```
Note:

After executing the above command, do not execute any other Performance Management commands until you change the host name in the next step.

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

Note

As a general rule, the directory specified in the -d option of the jpcconf host hostname command requires disk space equivalent to the total size of the PFM - Agent and PFM - RM Store databases and the import directory on the specified host. If you have made changes to the storage directory or import directory of the Store database, calculate the disk space requirements with reference to the size of the database in the new location.

For example, if PFM - Agent for HiRDB and PFM - Agent for Oracle are located in the environment directory, the directory must have free disk space equivalent to the size of the Store databases in the environment directory plus the size of the database in the import directory. You do not need to include the size of the Store database for the PFM - Manager Master Store service in the total size.
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 so that the new host name can be resolved to an IP address in the Performance Management system, if necessary.
Export the environment definition file of the logical host.

Supplemental information:

Apply the setting information of the active node to the passive node. First, export the environment definitions of the logical host of the active node to a file.

Execute the jpcconf ha export command to export the environment definitions of the logical host to a file of your choice.

For example, to export the environment definition of the logical host to the file lhostexp.conf, execute the following command.
```
jpcconf ha export -f lhostexp.conf
```
In this example, the jpcconf ha export command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf ha export command, see the chapter on commands in the manual JP1/Performance Management Reference.
Copy the environment definition file of the logical host to the standby node.

To apply the contents of the file exported in step 9 to the standby node, copy the file from the active node to the standby node.
Import the environment definition file of the logical host.

Supplemental information:

Import the export file copied from the active to the standby node.

Execute the jpcconf ha import command to import the environment definitions of the logical host to the standby node.

For example, if the name of the export file is lhostexp.conf, execute the following command:
```
jpcconf ha import -f lhostexp.conf
```
Executing the command jpcconf ha import will change the environment definitions of the standby node to match those of the active node. In this example, the jpcconf ha import command is executed in interactive mode. However, the command can also be executed in non-interactive mode.

For details on the jpcconf ha import command, see the chapter on commands in the manual JP1/Performance Management Reference.
Check the settings for the logical host environment.

Execute the jpcconf ha list command in the same manner as for the executing node to check the settings of the logical host.

Execute the command as follows.
```
jpcconf ha list -key all
```
For details on the jpcconf ha list command, see the chapter on commands in the manual JP1/Performance Management Reference.
Configure the cluster software.

For details, see 10.2.2(4) Cluster software setting procedure.

Perform any PFM - Agent-specific steps, if necessary.

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

Table 10‒6: 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 - Agents: PFM - Agent for Cosminexus PFM - Agent for Domino PFM - Agent for Enterprise Applications PFM - Agent for Microsoft SQL Server	The PFM - Agent-specific procedure is necessary. For details about the procedure, see 10.3.3(4) Optional PFM - Agent-specific steps for host name changes.
	Other than the above	The PFM - 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.

Delete service information on the PFM - Manager host.

Even though the PFM - Agent or PFM - RM host name is changed, the service information of the Performance Management programs with the old host name remains the same. Therefore, you need to delete unnecessary information from the PFM - Manager host. In a multiple-monitoring configuration, perform this step on both the primary and secondary managers.

The types of service information that you need to delete and the method of checking the service information are described as follows:

Service information on the host with the old host name

All the items that are displayed by executing the following command must be deleted:
```
jpctool service list -id * -host old-host-name
```
Service information whose service ID contains the old host name

Items whose Service ID column contains the old host name of the items that are displayed by executing the following command must be deleted:
```
jpctool service list -id *
```
Service information can be deleted by using the jpctool service delete command.

Delete service information on the host with the old host name by using the following command:
```
jpctool service delete -id * -host old-host-name
```
Additionally, delete service information whose service ID contains the old host name by using the following command:
```
jpctool service delete -id ???old-host-name -host new-host-name
```
If the message KAVE05233-W is issued during command execution because of a service information deletion error, re-execute the command as follows:
```
jpctool service delete -id * -host old-host-name -force
jpctool service delete -id ???old-host-name -host new-host-name -force
```
Note

Even though you execute the jpctool service list command, old service information that contains the old host name might not be displayed. Because such service information also needs to be deleted from the database, you must execute the jpctool service delete command shown above.

For details on the commands, see the chapter that describes the commands in the manual JP1/Performance Management Reference.
Apply the service information to PFM - Manager.

Synchronize the service information between PFM - Manager and PFM - Web Console so that the deletion takes effect in PFM - Web Console. To synchronize the service information, use the jpctool service sync command.

In a multiple-monitoring configuration, perform this step on both the primary and secondary managers.

The time when the service information synchronized by the jpctool service sync command takes effect depends on the version of PFM - Web Console. For details about the jpctool service sync command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
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.
Change the business group configuration if needed.

If the PFM - Agent host or PFM - RM host whose logical host name you changed is assigned to a business group, you need to change the configuration of the business group.

In a multiple-monitoring configuration, perform this step on the primary manager.

For details on how to do so, see 2. Managing User Accounts and Business Groups.
Register the new logical host name in the management folder in the Agents tree as needed.

Register the PFM - Agent or PFM - RM host whose logical host name you changed in the management folder in the Agents tree of PFM - Web Console. For details on how to register a host in the management folder, see 3. Monitoring Agents.
Reconfigure the definition of step 3 as needed.

Reconfigure the definitions (that were deleted in step 3) of the PFM - Agent or PFM - RM for which the logical host name was changed.

In a multiple-monitoring configuration, perform this step on the primary manager.
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.

In a multiple-monitoring configuration, perform this step on the primary manager.
- 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.
For details on how to edit alarms, see 6. Monitoring Operations with Alarms.
Update the JP1 system event settings.

If either of the following conditions is met, use your PFM - Web Console to update the JP1 system event settings:

In a multiple-monitoring configuration, perform this step on the primary manager.
- 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.
For details on the JP1 system events, see 12.2 JP1 events issued from Performance Management to JP1/IM.
Resume monitoring with the old host name specified.

If you suspend monitoring in step 1, you need to resume monitoring with the old host name specified to delete the settings information of monitoring suspension for the old host name.

In this case, use the -force option of the jpctool monitor resume command of the PFM - Manager host.

In a multiple-monitoring configuration, perform this step on the primary manager.
Resume monitoring for the PFM - Agent or PFM - RM host whose host name was changed.

If you suspend monitoring in step 2, use the jpctool monitor resume command of the PFM - Manager host or use the monitoring console to resume monitoring for the PFM - Agent or PFM - RM host.

In a multiple-monitoring configuration, perform this step on the primary manager.
Match the definitions on the primary manager and the secondary manager (in a multiple-monitoring configuration).

Export the definitions for the multiple-monitoring configuration from the primary manager and import them to the secondary manager so that the primary manager and the secondary manager have the same definitions.

For details about how to match the definition information, see 11.5 Duplicating definition information.
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 jpcrpt 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 Web browser.
- The actions
  
  Make sure that there is no problem in executing the created actions.

To Page Top

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

To change the PFM - Web Console logical host name:

Before performing this task in a system that links with JP1/SLM, refer to 13.4.1 Changing host names after linking with JP1/SLM.

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.
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.
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 10.2.3(3)(c) Setting up PFM - Web Console (logical host) and 10.2.3(3)(h) Copying the settings file to the executing node.
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.
- If a JP1 user event is used:
  
  Change the host name in the definition files for the tool launcher and for opening monitor windows. For details, see 12.3.2(4) Editing and copying the definition files for linkage.
- If a JP1 system event is used:
  
  Change the host name in the Monitoring Console Host property value for each service. For details, see 12.3.2(1) Configuring so that JP1 events are issued.
- If the setting is specified to display Performance Management reports from events in the Central Console:
  
  Change the PFM - Web Console host name specified in the performance report definition file (performance.conf).
For details on an integrated management product (JP1/IM), see 12. Linking with the Integrated Management Product JP1/IM for Operation Monitoring.
If the job management product (JP1/AJS3) is linked for operation monitoring, change the host name.

Change the PFM - Web Console host name specified in the JP1/AJS3 - Web Console environment-settings file (ajs3web.conf).
Change the PFM - Web Console logical host name.
If encrypted communication between a web browser and the monitoring console server is enabled, re-obtain certificates.

You must re-obtain certificates under the new host name.

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.
Reconfigure the cluster software.

For details on the setting procedure, see 10.2.3(4) Cluster software setting procedure.
Start services on the PFM - Web Console host.

Use operations from the cluster software to starts the PFM - Web Console services.
If the integrated management product (JP1/IM) is linked, restart the product (JP1/IM).

You can also apply the settings by executing the JP1/IM jco_spmd_reload command. For details about this command, see the manual JP1/Integrated Management 2 - Manager Command and Definition File Reference.
If the job management product (JP1/AJS3) is linked for operation monitoring, restart the services of JP1/AJS3.

To Page Top

(4) Optional PFM - 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 PFM - Manager logical host name
Changing the PFM - Agent or PFM - RM logical host name

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

(a) PFM - Agent for Cosminexus

Edit the definition files in all of the existing instance environments.

Definition file

environment-directory\agtc\agent\instance-name\jpcagt.ini
What to edit

Specify a new host name as the value of the COSMI_HOST entry in the [Agent] section.

(b) PFM - Agent for Domino

Note:: Perform the following procedure only if you use the health check function provided by PFM - Agent for Domino.

Edit the definition files in all of the existing instance environments.

Definition file

environment-directory\agtl\agent\instance-name\jpcagt.ini
What to edit

Specify a new host name as the value of the following entries in the [Health Check Options] section:
- Host entry in the [[HTTP Port Check]] subsection
- Host entry in the [[SMTP Port Check]] subsection
- Host entry in the [[POP3 Port Check]] subsection
- Host entry in the [[LDAP Port Check]] subsection
- Host entry in the [[NNTP Port Check]] subsection

(c) In PFM - Agent for Enterprise Applications

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

jpcconf inst setup -key agtm -inst o246bciSD500 -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.

(d) 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

In this example, the jpcconf inst setup command is executed in interactive mode. However, the command can also be executed in non-interactive mode.

When you execute the jpcconf inst setup command, specify the new host name at the SQL_HOST prompt. The other items are optional. Items for which you do not specify a value retain the existing setting.

To Page Top