3.1.2 Before installation and setup

(a) Setting up IP addresses

You must set up the environment for a PFM - Agent for Service Response host in such a manner that IP addresses can be determined from the host names.

PFM - Agent for Service Response cannot start in an environment in which IP addresses cannot be resolved.

Actual host names or alias names can be used for a monitoring host name (the name used as the host name of a Performance Management system).

• When using an actual host name as a monitoring host name

  Execute the hostname command on a Windows system or uname -n command on a UNIX system to check the host name, and set up the environment so that it can resolve IP addresses. Note that on a UNIX system, the host name obtained by the hostname command can also be used.

• When using an alias name as a monitoring host name

Set up the environment so that it can resolve the IP addresses for the set alias name.

For details about the configuration of a monitoring host name, see the chapter on installation and setup in the JP1/Performance Management Planning and Configuration Guide.

Use one of the following methods to set the host name and IP address:

• Performance Management's host information file (jpchosts file)

• hosts file

• DNS

Notes:

• Although Performance Management can operate in a DNS environment, do not specify host names in FQDN format. When you specify a monitoring host name, remove the domain name portions.

• 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 JP1/Performance Management Planning and Configuration Guide. Note that the IP addresses set in the jpchosts file are not used for resolving the IP addresses of monitored hosts.

• Performance Management cannot be run on a host on which DHCP is used to assign dynamic IP addresses. Set fixed IP addresses on all hosts on which Performance Management is installed.

Because Performance Management supports network configurations for IPv4 environments and IPv6 environments, you can use Performance Management in a network configuration that contains both IPv4 and IPv6 environments. PFM - Agent for Service Response can communicate with PFM - Manager by using IPv6. Note, however, that this applies only when Windows or Linux runs on a host with PFM - Manager installed.

For details about the scope of communication in IPv4 and IPv6 environments, see K. About Communication in IPv4 Environments and IPv6 Environments.

To use IPv6 for communication, IPv6 must be enabled on both the PFM - Manager host and the PFM - Agent host by using the jpcconf ipv6 enable command.

In addition, before installing PFM - Agent for Service Response, you need to enable the use of IPv6 on the PFM - Agent for Service Response host. You have to execute the jpcconf ipv6 enable command to enable this setting. If this setting is already enabled, however, you do not need to execute the command. If you want to check whether the use of IPv6 is enabled, execute the jpcconf ipv6 display command.

For details about the jpcconf ipv6 enable command and the jpcconf ipv6 display command, see the chapter that describes commands in the manual JP1/Performance Management Reference. For details about the conditions or occasions for executing the jpcconf ipv6 enable command, see the chapter that describes network configuration examples in an environment that includes IPv6 in the JP1/Performance Management Planning and Configuration Guide.

(b) Setting up 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 JP1/Performance Management Planning and Configuration Guide.

Table 3‒1: Default port numbers for Performance Management program services

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.
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.
JP1/SLM linkage facility	JP1/ITSLM	--	20905	The port number set by JP1/SLM.

You should set up your network in such a manner that communication can be established with the port numbers used by these PFM - Agent for Service Response programs.

(a) Precautions regarding the registry

PFM - Agent for Service Response can only be run on environments set up using the standard method provided by the OS. Despite the information provided by Microsoft technical support, if the OS environment is customized such as by using a registry editor to directly edit registry information, performance data might no longer be collected properly.

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

(c) Notes on 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 that 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 that order.

• If you install PFM - Agent for Service Response 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 already been installed on the target host.

• If PFM - Agent for Service Response already exists on the host where PFM - Manager is being installed, the local host is reset as the connection-target PFM - Manager for that PFM - Agent for Service Response. 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 for Service Response is to be installed, close all Web browser windows before starting installation.

• When you perform a new installation of a Performance Management program, the status management facility will be enabled by default. To change the setting of the status management facility, see the chapter on error detection for Performance Management in the JP1/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.

(d) Notes on version upgrade

For details about notes on upgrading the versions of Performance Management programs, see the section describing the notes on version upgrading in the chapter that explains installation and setup in the JP1/Performance Management Planning and Configuration Guide.

Observe the following precautions when upgrading the version of PFM - Agent for Service Response:

• You cannot upgrade PFM - Agent for Service Response when the IE Recorder or IE Probe Daemon is running. Before upgrade installation, stop the IE Recorder and IE Probe Daemon.

(e) Other notes

• If you are installing PFM - Agent for Service Response in an environment in which no Performance Management program has been installed, make sure that there are no files or folders in the installation-target folder.

• If you attempt to install PFM - Agent for Service Response 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 may be displayed. If this occurs, restart the system according to the message and then complete the installation.

• If you attempt to install PFM - Agent for Service Response 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 may fail if there is not enough disk space, or if you do not have folder permission. In such a case, terminate all such programs and then re-install PFM - Agent for Service Response. If there is not enough disk space or if you do not have directory permission, resolve the problem and then re-install PFM - Agent for Service Response.

• When installing the 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

    We recommend that any virus detection programs be stopped before the Performance Management program is installed.

    If a virus detection program is running during installation of the Performance Management program, the installation speed might suffer, and installation might not be executed, 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.

• You cannot upgrade PFM - Agent for Service Response when the IE Recorder or IE Probe Daemon is running. Before upgrade installation, stop the IE Recorder and IE Probe Daemon.