4.2.7 Points to note before installing PFM - Agent for Platform
(1) Notes on environment variables
Because Performance Management uses JPC_HOSTNAME as an environment variable, do not set it as a user-specific environment variable, as this will prevent Performance Management from operating properly.
(2) Notes on installing and setting up multiple Performance Management programs on the same host
With Performance Management, you can install PFM - Manager, PFM - Web Console, and PFM - Agent on the same host. When doing so, note the following points:
- If you are installing PFM - Manager and PFM - Agent on the same host, you do not need PFM - Base. In this case, because the prerequisite program for PFM - Agent is PFM - Manager, install PFM - Manager first and then install PFM - Agent.
- You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on the host on which PFM - Base and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. To install PFM - Base on the host on which PFM - Manager and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - Agent.
- When you install PFM - Agent on a host on which PFM - Manager is installed, PFM - Manager of the local host becomes PFM - Manager for the connection destination. In this case, you cannot change PFM - Manager for the connection destination to PFM - Manager of a remote host. To connect to PFM - Manager of a remote host, make sure that PFM - Manager is not installed on the host on which you want to install PFM - Agent.
- When you install PFM - Manager on a host on which PFM - Agent is installed, PFM - Manager for the connection destination of PFM - Agent is reset to the local host name. Check the setting results that are output to the common message log.
- Before installing PFM - Agent on a host on which PFM - Web Console is installed, close all browser windows.
- When a Performance Management program is newly installed, the status management function is enabled as the default. However, if you upgrade from version 07-00 to 08-00 or newer, the settings for the status management function remain the same as they were in the older version. For details about how to change the settings for the status management function, see the chapter explaining error detection in Performance Management in the Job Management Partner 1/Performance Management User's Guide.
- Hint
- To improve system performance and reliability, we recommend running PFM - Manager, PFM - Web Console, and PFM - Agent on separate hosts.
(3) Notes on version upgrade
Note the following points when upgrading PFM - Agent from an older version to a newer one:
For details about upgrading, see the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Before installing a Performance Management program, stop all Performance Management programs and services of the local host. For details about how to stop services, see the chapter explaining how to start and stop Performance Management in the Job Management Partner 1/Performance Management User's Guide.
- You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on the host on which PFM - Base and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. To install PFM - Base on the host on which PFM - Manager and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - Agent.
- In Performance Management programs of version 08-00 or later, the locations of the Store execution programs (jpcsto and stpqlpr) have been changed. When PFM - Agent is upgraded to version 08-00 or later, the Store execution modules in the previous locations are deleted.
- Because the data model version of the existing Store database is upgraded automatically during an upgrade installation, twice as much disk space as will be needed for the Store database is required temporarily. Before performing an upgrade installation, make sure that the disk on which the Store database is stored has sufficient free space. The space requirement needs to be evaluated relative to the total size of the current Store database. For example, if the total size of the current Store database is 100 gigabytes, the disk space required for an upgrade installation will be more than 200 gigabytes. If you are changing the disk containing the Store database, be sure to consider the space that will be required on the new disk.
(4) Other notes
- When installing a Performance Management program, check whether any of the following security-related programs are installed. If they are installed, perform the measures explained.
- Security monitoring programs
Stop or change the settings for security monitoring programs so that installation of the Performance Management program is not prevented.
- Virus detection programs
Stop any virus detection programs before you install the Performance Management program
If a virus detection program is running during installation of the Performance Management program, the installation speed may suffer, and installation might not be executed, or might not be performed correctly.
- Process monitoring programs
Stop or change the settings for any process monitoring programs, so that monitoring is not performed for Performance Management services or processes, and Common Component services or processes.
If a process monitoring program starts or stops these services or processes during installation of the Performance Management program, installation might fail.
- If you install a new Performance Management program in an environment in which no Performance Management program is installed, make sure that there is no file or directory in the installation directory.
- If Installation failed appears in the status bar during installation and installation fails, obtain the installation log and store it in a file. You need to back up the log file as needed because this log file is overwritten the next time you install a program. For details about the default file name for the installation log, see 11.4.3 Operation information to be collected.
- When you install Performance Management programs by setting a link to the installation directory, some files and directories might remain in the linked directory even if you uninstall all of the Performance Management programs. Also, you must be careful when you install Performance Management programs in the linked directory, as files or directories having the same name in the linked directory are overwritten.
- When the PFM - Agent for Platform setup file exists in the /opt/jp1pc/setup directory, additional setup of a new PFM - Agent for Platform is executed. When additional setup of the new PFM - Agent for Platform is successful, the execution result message KAVE05908-I New agent setup ended successfully. is output to the common message log. Check the log.