3.2.6 Notes about installation and setup in UNIX

(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.

To Page Top

(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 Job Management Partner 1/Performance Management User's Guide.

Tip

System performance and reliability are improved by running PFM - Manager, PFM - Web Console, and PFM - Agent on separate hosts.

To Page Top

(3) Upgrading

This subsection provides notes about upgrading a PFM - Agent.

For details about upgrading, see H. Migration Steps and Notes on Migration.

• 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.

• When you install a Performance Management program, make sure that all Performance Management program services are stopped at the local host. This includes all services on both physical and logical hosts. For details about how to stop services, see the chapter that describes startup and termination of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

• 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.

• PFM - Base and PFM - Manager cannot be installed on the same host. To install PFM - Manager on a host where PFM - Base and a PFM - Agent have been installed already, 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 a PFM - Agent have been installed already, uninstall all Performance Management programs (other than PFM - Web Console), and then install PFM - Base and PFM - Agent in this order.

• For a Performance Management program of version 08-00 or later, the locations of the Store execution programs (jpcsto and stpqlpr) have been changed. The old Store execution modules are deleted when PFM - Agent is upgraded to version 08-00 or later.

• If the Store database's data model version changes during an upgrade, the disk space required for the Store database is temporarily doubled because the existing Store database is upgraded automatically. Before you start the upgrade installation, make sure that there is enough space on the disk where the Store database is located. Determine the required space based on the total size of the current Store database. For example, if the total size of the current Store database is 100 gigabytes, at least 200 gigabytes of disk space is required during the upgrade installation. If you have changed the Store database storage disk, make sure that the new storage disk has sufficient free space.

• 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).

To Page Top

(4) Notes about the 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 syslog. 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.

To Page Top

(5) Other notes

• 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

  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.

• If you are installing PFM - Agent for Enterprise Applications in an environment in which no Performance Management program has been installed, make sure that there are no files or directories in the installation-target directory.

• If installation fails with Install failed displayed on the status bar during the installation process, obtain the installation log. It is wise to make a backup of this log file, because it will be overwritten during the next installation. For details about the default file name for the installation log, see 12.4.2(2) Information about Performance Management.

• If a link is placed in the installation directory to install Performance Management programs, uninstalling all Performance Management programs might not remove all the files and directories from the linked directory. If necessary, manually delete the remaining files and directories. If a Performance Management program is to be installed by linking and the link destination contains a file or directory with the same name, that file or directory will be overwritten when the Performance Management program is installed.

To Page Top