Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference

3.1.1 Before installation and setup

This section describes the items to be checked before installing and setting up PFM - Agent for Enterprise Applications.

Organization of this subsection

(1) Supported OSs

(2) Network environment setup

(3) OS user permission required for installation

(4) Required programs

(5) Installing and setting up in a cluster system

(6) Notes

(1) Supported OSs

PFM - Agent for Enterprise Applications can run on the following operating systems (OSs):

• HP-UX
• AIX
• Solaris

(2) Network environment setup

This subsection describes the network environment needed for Performance Management operation.

(a) Setting IP addresses

You must set up the environment for a PFM - Agent host in such a manner that IP addresses can be determined from the host name. PFM - Agent can run only in an environment in which IP addresses can be resolved.

For the monitoring host name (name used as the host name of the Performance Management system), you can use the real host name or an alias name.

• When the real host name is used as the monitoring host name:
  In a UNIX system, set the environment in such a manner that the IP address can be resolved by the host name that is obtained by the uname -n command. Note that in a UNIX system, you can also use the hostname command to obtain the host name.
  
• When an alias name is used as the monitoring host name:
  Set the environment in such a manner that the IP address can be resolved by this alias name.
  

For details about the monitoring host name setting, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

To set host names and IP addresses, use one of the following methods:

• Performance Management's host information file (jpchosts file)
• hosts file
• Domain Name System (DNS)

Notes

• Performance Management can be run in a DNS environment, but it does not support fully qualified domain names (FQDNs). When you specify a monitoring host name, do not include the domain name.
• If you use Performance Management in multiple LAN environments, use the jpchosts file to set IP addresses. For details, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
• Performance Management does not run on a host where dynamic IP addresses are assigned by DHCP. Set fixed IP addresses for all hosts on which Performance Management is to be installed.

(b) Setting port numbers

The port numbers listed in the table below are assigned by default to the Performance Management program services. An available port number is assigned automatically to any other service or program each time such a service is started. You must use fixed port numbers when Performance Management is used in a firewall environment. For details about how to fix port numbers, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Table 3-1 Default port numbers used by the Performance Management program services (for UNIX)

Service description	Service name	Parameter	Port number	Remarks
Service configuration information management function	Name Server	jp1pcnsvr	22285	Port number used by PFM - Manager's Name Server service. This port number is set at all hosts of Performance Management.
OpenView linkage facility	NNM Object Manager	jp1pcovsvr	22292	Port number used for communication between map manager and object manager when the OpenView linkage facility is used with PFM - Manager and PFM - Base. This port number is set at the host where PFM - Manager and PFM - Base are installed.
Service status management function	Status Server	jp1pcstatsvr	22350	Port number used by the Status Server service of PFM - Manager and PFM - Base. This port number is set at the host where PFM - Manager and PFM - Base are installed.

You should set up your network in such a manner that communication can be established with the port numbers used by these Performance Management program services.

(3) OS user permission required for installation

Make sure that you are using an account that has the superuser permission when you install PFM - Agent for Enterprise Applications.

(4) Required programs

This subsection describes the programs that are required in order to install PFM - Agent for Enterprise Applications. The following shows the configuration of the programs.

Figure 3-1 Program configuration

(a) Programs that can be monitored

PFM - Agent for Enterprise Applications can monitor the following programs:

• SAP R/3 Enterprise
• SAP Business Information Warehouse
• SAP NetWeaver

For these programs to be monitored, they must be installed on the same host as PFM - Agent for Enterprise Applications.

(b) Performance Management programs

PFM - Agent and PFM - Base must be installed on the monitoring agent. PFM - Base is a prerequisite program for PFM - Agent. You need only one PFM - Base even when multiple PFM - Agents are installed on the same host.

Note that if you install PFM - Manager and PFM - Agent on the same host, PFM - Base is not required.

To monitor SAP system operation using PFM - Agent for Enterprise Applications, you need PFM - Manager and PFM - Web Console.

(5) Installing and setting up in a cluster system

The required network environment and program configuration are different for a cluster system than for a normal non-cluster system. In a cluster system, installation and setup are required at both the executing and the standby nodes. For details, see 4. Operation in a Cluster System.

(6) Notes

This subsection provides notes about installing and setting up Performance Management.

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

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

(c) Upgrading

This subsection provides notes about upgrading a PFM - Agent.

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

• 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 delete 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.
• During an upgrade installation, 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.

(d) Other notes

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

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.