3.4.2 Setup cancellation procedure
This section describes the procedure for canceling setup of the logical host environment. There are separate procedures for the executing node and the standby node. Cancellation of setup must be performed first on the executing node and then on the standby node.
indicates a task to be performed on the executing node.
indicates a task to be performed on the standby node.
indicates a setup item that is required depending on the environment or an optional setup item used when the default is to
be changed.
The following subsections describe how to cancel setup of PFM - Agent for Microsoft SQL Server.
- Organization of this subsection
-
-
(4) Cancel setup of the logical host environments for PFM - Agent for Microsoft SQL Server
-
(5) Cancel setup of the logical host environments for other Performance Management programs
-
(7) Copy the logical-host environment definition file to the standby node
-
(10) Unregister PFM - Agent for Microsoft SQL Server in the cluster software
(1) Stop services from the cluster software
![[Figure]](GRAPHICS/ZU12003.GIF)
Stop all the Performance Management programs and services running on the executing and standby nodes by using instructions from the cluster system. For details about how to stop the programs and services, see the documentation for your cluster software.
(2) Bring the shared disk online ![[Figure]](GRAPHICS/ZU12002.GIF)
Make sure that the shared disk is online. If the shared disk is not online, use the cluster software or the volume manager to bring it online.
(3) Clear the port number settings
![[Figure]](GRAPHICS/ZU12001.GIF)
Perform this step only if you are running a firewall environment, and you used the jpcconf port command to set port numbers during setup.
For details about how to clear the port number settings, see the chapter on uninstallation and unsetup in the JP1/Performance Management Planning and Configuration Guide and see the chapters on setup and operation in a cluster system in the JP1/Performance Management User's Guide.
(4) Cancel setup of the logical host environments for PFM - Agent for Microsoft SQL Server ![[Figure]](GRAPHICS/ZU12002.GIF)
The following procedure shows how to cancel setup of the logical host environment for the executing node.
- Note:
-
If a logical host environment is deleted while the shared disk is offline, the logical host settings are deleted from the physical host, but the folders and files are not deleted from the shared disk. In such cases, you must bring the shared disk online and then manually delete the jp1pc folder under the environment folder.
-
Execute the jpcconf ha list command to check the logical host settings.
Execute the command as follows:
jpcconf ha list -key all -lhost jp1-halSQL
Before canceling setup of the logical host environment, check the current settings, including the logical host name and the path to the shared disk.
-
Execute the jpcconf inst unsetup command to delete the instance environment.
Execute the command as follows:
jpcconf inst unsetup -key SQL -lhost jp1-halSQL -inst SQL1
Although an example of interactive command execution is shown here, the jpcconf inst unsetup command can be also executed non-interactively. For details about the jpcconf inst unsetup command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
When you execute the jpcconf inst unsetup command, the settings that allow the instance to start on the logical host are deleted. The files on the shared disk that relate to the logical host are also deleted.
-
Execute the jpcconf ha unsetup command to delete the logical host environment for PFM - Agent for Microsoft SQL Server.
Execute the command as follows:
jpcconf ha unsetup -key SQL -lhost jp1-halSQL
When you execute the jpcconf ha unsetup command, the settings that allow the instance to start on the logical host are deleted. Files on the shared disk that relate to the logical host are also deleted.
-
Use the jpcconf ha list command to check the logical host settings.
Execute the command as follows:
jpcconf ha list -key all
Confirm that PFM - Agent for Microsoft SQL Server has been deleted from the logical host environment.
(5) Cancel setup of the logical host environments for other Performance Management programs
![[Figure]](GRAPHICS/ZU12001.GIF)
If there are Performance Management programs for which you want to cancel setup in addition to PFM - Agent for Microsoft SQL Server on the same logical host, cancel setup of these at this point.
For details about how to cancel setup, see the chapters on setup and operation in a cluster system in the JP1/Performance Management User's Guide, or the chapters on operation in a cluster system in the applicable PFM - Agent manual.
(6) Export the logical-host environment definition file ![[Figure]](GRAPHICS/ZU12002.GIF)
After you have deleted PFM - Agent for Microsoft SQL Server from the logical host, export the environment definition as a file.
Performance Management allows you to synchronize the environments on the executing node and standby node by exporting the environment definition from one node and importing it into the other.
When you import the environment definition (without the Performance Management component) from the executing node into the standby node, the imported environment definition is compared with the existing environment definition (containing the Performance Management component) and the difference between the two is verified. The Performance Management environment definition is then cleared from the standby node so that both nodes have the same environment.
To export the logical-host environment definition file:
-
Execute the jpcconf ha export command to export the logical host environment definition.
The definition information for the logical host environment of Performance Management is output to an export file. You can give this file any name you wish.
For example, execute the command as follows to output the logical host environment definition to the file lhostexp.txt:
jpcconf ha export -f lhostexp.txt
Although an example of interactive command execution is shown here, the jpcconf ha export command can be also executed non-interactively. For details about the jpcconf ha export command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
(7) Copy the logical-host environment definition file to the standby node
![[Figure]](GRAPHICS/ZU12003.GIF)
Copy the file you exported in (6) Export the logical-host environment definition file from the executing node to the standby node.
(8) Take the shared disk offline
![[Figure]](GRAPHICS/ZU12001.GIF)
Use the cluster software or the volume manager to take the shared disk offline. Note that if you intend to continue using the shared disk, you do not need to take it offline at this point.
(9) Import the logical-host environment definition file ![[Figure]](GRAPHICS/ZU12003.GIF)
On the standby node, import the exported file you copied from the executing node in order to synchronize the environment definitions of both nodes. You do not need to take the shared disk offline on the standby node before importing the file. Note that the shared disk does not need to be offline when you execute this command.
To import the logical-host environment definition file:
-
Execute the jpcconf ha import command to import the environment definition of the logical host.
Execute the command as follows:
jpcconf ha import -f lhostexp.txt
Although an example of interactive command execution is shown here, the jpcconf ha import command can be also executed non-interactively. For details about the jpcconf ha import command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
When you execute the command, the environment on the standby node is changed to reflect the environment described in the export file. This clears the settings that allow PFM - Agent for Microsoft SQL Server to start on the logical host. These settings are also cleared for any other Performance Management programs for which you cancel setup on the logical host.
If you used the jpcconf port command during setup to assign fixed port numbers, the port numbers will no longer be assigned.
-
Execute the jpcconf ha list command to check the logical host settings.
Execute the command as follows:
jpcconf ha list -key all
Confirm whether the same output is displayed as when you executed the jpcconf ha list command on the executing node.
(10) Unregister PFM - Agent for Microsoft SQL Server in the cluster software
![[Figure]](GRAPHICS/ZU12003.GIF)
Delete the settings related to PFM - Agent for Microsoft SQL Server on the logical host from the cluster software.
For details about deleting these settings, see the documentation for your cluster software.
(11) Delete settings from PFM - Manager
![[Figure]](GRAPHICS/ZU12003.GIF)
Log in to PFM - Manager from PFM - Web Console, and delete the definition relating to the PFM - Agent for Microsoft SQL Server for which you want to cancel setup.
To delete the definition:
-
Start the PFM - Manager service.
-
If you have stopped the PFM - Manager services from the cluster software as described in (1) Stop services from the cluster software, use the cluster software to start the PFM - Manager services. For details about how to start the services, see the cluster software documentation.
-
From PFM - Web Console, delete the agent.
-
Delete the agent information in PFM - Manager.
For example, if PFM - Manager is running on the logical host jp1-hal, and PFM - Agent for Microsoft SQL Server is running on the logical host jp1-halora, execute the following command to delete the agent:
jpctool service delete -id service-ID -host jp1-halSQL -lhost jp1-hal
In service-ID, specify the service ID of the agent you want to delete.
-
Restart the PFM - Manager service.
For details about how to start services, see the chapter on starting and stopping Performance Management in the JP1/Performance Management User's Guide.
-
Apply the service information of the PFM - Manager host.
In order to update the PFM - Web Console host to reflect the deletion of service information, synchronize the agent information of the PFM - Manager host and that of the PFM - Web Console host. Use the jpctool service sync command to synchronize the agent information.