3.1.6 Notes about installation and setup in Windows
- Organization of this subsection
(1) Notes about environment variables
Performance Management uses the JPC_HOSTNAME environment variable. Do not set a user-specific JPC_HOSTNAME environment variable. If such an environment variable is set, Performance Management will not function correctly.
(2) Installing and setting up multiple Performance Management programs on the same host
Performance Management enables you to install PFM - Manager, PFM - Web Console, and PFM - Agent on the same host. This subsection provides notes about such an installation.
-
If you install PFM - Manager and PFM - Agent on the same host, there is no need to install PFM - Base. In this case, PFM - Agent requires PFM - Manager; therefore, install PFM - Manager first, and then install PFM - Agent.
-
PFM - Base and PFM - Manager cannot be installed on the same host. To install PFM - Manager on a host where PFM - Base and PFM - Agent are already installed, uninstall all Performance Management programs (other than PFM - Web Console), and then install PFM - Manager and PFM - Agent in this order. Similarly, to install PFM - Base on a host where PFM - Manager and PFM - Agent are already installed, uninstall all Performance Management programs (other than PFM - Web Console), and then install PFM - Base and PFM - Agent in this order.
-
If you install PFM - Agent on a host where PFM - Manager is already installed, the PFM - Manager on the local host becomes the connection-target PFM - Manager. In such a case, you can no longer change the connection-target PFM - Manager to a PFM - Manager on a remote host. Therefore, if you want to connect to a PFM - Manager on a remote host, make sure that PFM - Manager has not been installed already on the target host.
-
If a PFM - Agent already exists on the host where PFM - Manager is being installed, the local host is redesignated as the connection-target PFM - Manager for that PFM - Agent. The resulting settings are output to the common message log file; check the results.
-
If PFM - Web Console already exists on a host where PFM - Agent is to be installed, close all browser windows before starting installation.
-
When a new Performance Management program is installed, the default is that the status management function is enabled. However, if you upgrade from version 07-00 to 08-00 or later, the settings for the status management function disabled. To change the status management function settings, see the chapter that describes Performance Management failure detection in the JP1/Performance Management User's Guide.
- Tip
-
To improve system performance and reliability, we recommend that you run PFM - Manager, PFM - Web Console, and PFM - Agent on separate hosts.
(3) Upgrading
For notes about upgrading the Performance Management programs, see the notes on version upgrades in the chapter on installation and setup in the JP1/Performance Management Planning and Configuration Guide.
This subsection provides notes about upgrading a PFM - Agent.
For details about upgrading, see Appendix H. Migration Steps and Notes on Migration and the JP1/Performance Management Planning and Configuration Guide.
-
If the Store database's data model version changes during an upgrade, the existing Store database is automatically upgraded. If the upgrading fails, the Store database might be corrupted. Therefore, before you upgrade PFM - Agent, back up the Store database.
-
If a Performance Management program already exists on the host where a PFM - Agent is to be installed, the PFM - Agent's installation path becomes the same as for the existing Performance Management programs (other than PFM - Web Console). To change the installation path, you must uninstall all the Performance Management programs that have been installed (other than PFM - Web Console) and then re-install them.
-
If you are upgrading your OS to Windows Server 2008 or Windows Server 2012, you must first uninstall the Performance Management products for Windows Server 2003, because operations for Performance Management products are not guaranteed on Windows Server 2008 and Windows Server 2012. Before you start the upgrade procedure, uninstall all Performance Management products, upgrade the OS, and then install Performance Management products that support Windows Server 2008 or Windows 2012.
-
If you are using a file monitoring product to monitor the files containing system log information and CCMS Alert Information, stop the file monitoring function before upgrading.
-
The settings in the existing environment parameter file for system log information and CCMS Alert Information are inherited during upgrading, including those for existing instances.
-
If PFM - Agent is upgraded from version 09-00 or earlier, the storage files will have the same output format as before upgrading (WRAP1).
(4) Notes about an SAP system employing an ASCS instance configuration
-
To monitor the SAP system, you need to set up an instance environment for each host that contains a central instance with dialog service (primary application server instance) or a dialog instance (additional application server instance).
-
If the SAP system employs an ASCS instance configuration, no performance data will be collected from the ENQUEUE_SERVER_QUEUE_LENGTH field of the PI_ENQ record because this field does not exist in the connection-target dialog instance. As a result, a warning message (KAVF14173-W) is output to the common message log and Windows event log. This warning message is output regardless of the settings for Log (whether or not the collected performance data is to be recorded in the Store database) in each record.
(5) Other notes
-
If you attempt to install PFM - Agent for Enterprise Applications while Performance Management programs and services are running or while other programs that reference Performance Management files (such as Windows Event Viewer) are running, a message prompting for a system restart might be displayed. If this occurs, restart the system according to the message and complete the installation.
-
If you attempt to install PFM - Agent for Enterprise Applications while Performance Management programs and services are running or while other programs that reference Performance Management files (such as Windows Event Viewer) are running, file expansion might fail if there is not enough disk space or if you do not have directory permission. In such a case, terminate all such programs and then re-install PFM - Agent for Enterprise Applications. If there is not enough disk space or you do not have directory permission, resolve the problem and then re-install PFM - Agent for Enterprise Applications.
-
Before you install Performance Management programs, check to see if any security-related programs, such as those described below, are installed. If such a program is installed, take appropriate action according to the information provided below.
-
Security monitoring program
Terminate the security monitoring program or change its settings so that installation of the Performance Management programs will not be affected.
-
Virus detection program
We recommend that you terminate any virus detection program before you install the Performance Management programs.
If a virus detection program is running during installation of a Performance Management program, it might slow down the installation process, the installation might fail, or the program might not install correctly.
-
Process monitoring program
Terminate the process monitoring program or change its settings so that it does not monitor the services and processes of Performance Management or the services and processes of common components.
Installation of a Performance Management program might fail if any of these services or processes is started or stopped by the process monitoring program during the installation process.
-