5.2.1 Before uninstallation and unsetup

The following gives cautionary notes on uninstalling and performing unsetup of Performance Management:

Organization of this subsection

(1) Notes on the OS user permission required for uninstallation
(2) Notes on the network
(3) Notes on programs
(4) Notes on services
(5) Notes on PFM - Web Console
(6) Other related notes

(1) Notes on the OS user permission required for uninstallation

Make sure you are the root user when uninstalling Performance Management programs.

(2) Notes on the network

Even though Performance Management programs are uninstalled, the port numbers defined in the services file are not deleted.

To Page Top

(3) Notes on programs

Files or directories might remain if you uninstall Performance Management programs while other programs or services, or programs that reference Performance Management files are running. In such cases, manually delete all of the directories and files under the installation directory.
If a host has PFM - Base and either PFM - Agent or PFM - RM installed, you have to uninstall PFM - Agent or PFM - RM first in order to uninstall PFM - Base. In such cases, uninstall PFM - Agent or PFM - RM, and then uninstall PFM - Base. Additionally, if a host has PFM - Manager and either PFM - Agent or PFM - RM installed, you have to uninstall PFM - Agent or PFM - RM first to uninstall PFM - Manager. In such cases, uninstall PFM - Agent or PFM - RM, and then uninstall PFM - Manager.

To Page Top

(4) Notes on services

Stop all Performance Management programs and services in the entire Performance Management system before you uninstall PFM - Manager.
Uninstalling only PFM - Agent or PFM - RM does not delete the service information that can be displayed by using the jpctool service list command or the jpctool monitor list command. In such cases, use the jpctool service delete command to delete the service information. For details about how to delete the service information, see 5.2.3 Deleting service information.
If you uninstall PFM - Manager and then re-install it on the same machine, two Trap Generator services might be displayed when the jpctool service list command is executed. In such cases, start the PFM - Manager service and use the jpctool service delete command to delete the Trap Generator that is Inactive.

To Page Top

(5) Notes on PFM - Web Console

If uninstallation is performed under the following conditions, some files or directories may remain. If such is the case, delete all the files and directories contained in the installation destination directory. If PFM - Web Console is uded on a logical host environment, delete all the files and directories contained in the environment directory on the shared disk as well.

- The programs or services for PFM - Web Console are running.

- A file or directory within the installation destination directory are referenced.
In the initialization file (config.xml), if you have changed the settings for logDir, bookmarkRepository, and processMonitoringTemplatesRepository to directories other than the default directories, the usual uninstallation procedure will not delete those directories. Before you uninstall PFM - Web Console, check config.xml and manually delete the directories.
The uninstall log is output to /etc/.hitachi/.uninstall.log.
If uninstallation fails, back up the log (/etc/.hitachi/.uninstall.log) output during the uninstallation process, remove the cause of the problem, and then try again. If JP1/PFM - Web Console does not appear in the list of programs you can uninstall, then install it again, and then repeat the uninstallation process.
When you uninstall Performance Management programs from a host that has PFM - Web Console installed, first close all Web browser windows that are logged in to PFM - Web Console and then uninstall the programs.

To Page Top

(6) Other related notes

If an instance environment is set in PFM - Agent or PFM - RM, perform unsetup of the instance environment before uninstalling PFM - Agent or PFM - RM. For details about the unsetup procedure, see the chapters describing installation and setup in the appropriate PFM - Agent or PFM - RM documentation.
If PFM - Manager or PFM - Base is uninstalled while Performance Management is linked with JP1/SLM, the monitoring targets can no longer be checked in JP1/SLM's Troubleshoot window. Therefore, before you uninstall PFM - Manager or PFM - Base, release the linkage between Performance Management and JP1/SLM. For details about how to release the linkage, see the chapter in the JP1/Performance Management User's Guide that describes monitoring with a service-level management product (JP1/SLM) linked.
If you uninstall or unsetup a PFM - Agent or PFM - RM to which alarm tables have been bound, use PFM - Web Console or the jpctool alarm unbind command to unbound all alarm tables before you start the uninstallation or unsetup procedure.
If you have uninstalled or performed the unsetup procedure on PFM - Agent or PFM - RM, delete the agents, if necessary, that are no longer needed from the tree that is displayed when User Agents is selected from the Agents tree in PFM - Web Console. Also, delete any unneeded alarm and report definition information, if necessary. For details about how to delete agents from the Agents tree, see the chapter in the JP1/Performance Management User's Guide that describes monitoring of agents. For details about how to delete alarm definition information, see the chapter in the JP1/Performance Management User's Guide that describes operation monitoring by using alarms. For details about how to delete report definition information, see the chapter in the JP1/Performance Management User's Guide that describes creation of reports for operation analyses.
If the Store database is not located in the default directory, uninstalling the Performance Management programs will not delete the files in the Store database storage directory. In such a case, manually delete all files and subdirectories under the Store database storage directory.

If you execute the systemctl command after uninstalling PFM - Manager, PFM - Base, or PFM - Web Console from Linux 7 or later, not-found might be displayed for jp1_pc.service or jp1_webcon.service.

A jp1_pc.service display example follows:

# systemctl
UNIT                        LOAD      ACTIVE SUB       DESCRIPTION
- Omitted -
jp1_pc.service              not-found active exited    jp1_pc.service
or
jp1_pc.service              not-found failed failed    jp1_pc.service

Although this does not cause any OS operation-related problems, to delete these items, execute the following commands according to the status of the ACTIVE column:

UNIT column	ACTIVE column	Command to be executed
`jp1_pc.service`	active	`systemctl stop jp1_pc`
`jp1_pc.service`	failed	`systemctl reset-failed jp1_pc`
`jp1_webcon.service`	active	`systemctl stop jp1_webcon`
`jp1_webcon.service`	failed	`systemctl reset-failed jp1_webcon`

If you want to perform unsetup of PFM - Agent or PFM - RM for which auto alarm table bind is enabled, and if you have no intention of using auto alarm bind with these products in the future, disable auto alarm table bind set for these products before performing the unsetup procedure. For details about how to specify the auto alarm table bind setting, see the section providing the procedure for auto alarm bind in the JP1/Performance Management User's Guide.
If you want to hide product information on the Alarms page and Reports page of PFM - Web Console, unregister the product information by using the jpcconf agent setup -unregister command. For details, see the section describing the jpcconf agent setup -unregister command in the manual JP1/Performance Management Reference.
In Solaris or HP-UX, to uninstall PFM - Base when the NNM linkage function has been set up, use the same LANG environment variable you used to set up the NNM linkage function.

To Page Top