2.1.1 Preparation for installing and setting up PFM - RM for Oracle (Windows)

(a) IP address settings

The PFM - RM for Oracle host must be set up in a network environment where IP addresses can be resolved from host names. PFM - RM for Oracle will not start in an environment where IP addresses cannot be resolved.

PFM - RM for Oracle can run in an IPv6 environment and dual stack environment in addition to an IPv4 environment. To run PFM - RM for Oracle in an IPv6 environment, the monitored Oracle database must support IPv6 environments.

You can use the real host name as a monitoring host name (a host name used in Performance Management system).

In a Windows system, set up the environment so that an IP address can be resolved from the host name returned by the hostname command. In a UNIX system, set up the environment so that an IP address can be resolved from the host name returned by the uname -n command.

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. Note that IP addresses set in the jpchosts file are not used for resolving the IP addresses of monitoring targets.

Use one of the following methods to set the host name and IP address of a host monitored by Performance Management programs:

• Host information settings file for Performance Management (jpchosts file)

• hosts file

• DNS (Domain Name System)

Use a real host name or an alias name for the monitoring host name.

• When using a real host name

  In a Windows system, set up the environment so that an IP address can be resolved from the host name returned by the hostname command.

  Note that although Performance Management can operate in a DNS environment, it does not support host names in FQDN (Fully Qualified Domain Name) format. Therefore, specify a monitoring host name without the domain name.

• When using an alias name

  Set up the environment so that an IP address can be resolved from the specified alias name.

For details about the structure of a monitoring host name, see the chapter that describes how to change the system configuration in the JP1/Performance Management Planning and Configuration Guide.

Notes on setting IP addresses:

• If you intend to use Performance Management within multiple LAN environments, set the IP addresses in the jpchosts file. For details, see the chapter on installation and setup in the JP1/Performance Management Planning and Configuration Guide.

• Performance Management cannot operate on the hosts to which IP addresses are assigned dynamically by DHCP. Make sure that all the hosts on which Performance Management programs are installed are configured with user-specified static IP addresses.

Performance Management supports IPv6 environments as well as IPv4 environments as a network configuration. Therefore, Performance Management can operate even in a network configuration in which both an IPv4 environment and an IPv6 environment are used.

PFM - RM for Oracle can communicate with PFM - Manager via IPv6. Note that this explanation applies only when the OS of a host on which PFM - RM for Oracle and PFM - Manager are installed is Windows or Linux.

For details about the scope of communication in an environment with both IPv4 and IPv6, see M. About Communication in IPv4 Environments and IPv6 Environments.

When you want to use IPv6 for communication between PFM - Manager and PFM - RM for Oracle, the settings for using IPv6 must be enabled for both the PFM - Manager host and the PFM - RM host. In addition, before installing PFM - RM for Oracle, you need to enable the use of IPv6 on the PFM - RM 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 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.

When you use IPv6 for communication between a monitored host and PFM - RM for Oracle, specify the name of a monitored host where name resolution can be performed.

Communication between PFM - RM for Oracle and a monitoring target is performed with an IP address that can be resolved. Also, if an IPv4 environment and an IPv6 environment are both used, and communication between PFM - RM for Oracle and the monitoring target fails with an IP address that can be resolved, the communication is not retried by using another IP address.

For example, if communication fails when IPv4 is used, IPv6 is not used to retry communication. Similarly, if communication fails when IPv6 is used, IPv4 is not used to retry communication. Make sure beforehand that a connection can be established.

(b) Port number settings

The following table shows the default port numbers assigned to the services of Performance Management programs. For other services and programs, available port numbers are automatically assigned each time they are started. If you use Performance Management in a firewall environment, use fixed port numbers. For details about how to set fixed port numbers, see the chapter on installation and setup in the JP1/Performance Management Planning and Configuration Guide.

Table 2‒1: Default port numbers for Performance Management program services (in Windows)

Service description	Service name	Parameter	Port number	Remarks
Service configuration information management facility	Name Server	jp1pcnsvr	22285	The port number used by the Name Server service of PFM - Manager. This port is set up on every Performance Management host.
Service status management facility	Status Server	jp1pcstatsvr	22350	The port number used by the Status Server service of PFM - Manager and PFM - Base. This port is set up on the hosts on which PFM - Manager and PFM - Base are installed.
Monitoring console communication facility	View Server	jp1pcvsvr	22286	The port number used by the View Server service of PFM - Manager. This port is set up on the hosts on which PFM - Manager is installed.
Web service facility	Web Service	--	20358	The port number used by the Web Service service of PFM - Web Console.
Web container facility	Web Console	--	20359 20360	The port number used by the Web Console service of PFM - Web Console.
JP1/SLM linkage facility	JP1/ITSLM	--	20905	The port number set by JP1/SLM.

Legend:

--: None

Ensure that the network is set up to allow communication using these port numbers, which are used by PFM - RM for Oracle.

(a) Monitoring target programs

The monitoring target programs of PFM - RM for Oracle are as follows:

• Oracle Database Standard Edition

• Oracle Database Standard Edition One

• Oracle Database Standard Edition 2

• Oracle Database Enterprise Edition

Note that when a monitoring target program running on a virtualized OS is being monitored, PFM - RM for Oracle monitors what the monitoring target program can perform on the virtualized OS.

(b) Performance Management programs

Install PFM - RM for Oracle and PFM - Base on the PFM - RM host.

PFM - Base is a prerequisite program for PFM - RM for Oracle. Only one instance of PFM - Base is required, even when multiple instances of PFM - RM are installed on one host.

Note that you do not need to install PFM - Base if PFM - Manager and PFM - RM for Oracle are installed on the same host.

To monitor Oracle operation using PFM - RM for Oracle, PFM - Manager and PFM - Web Console are required.

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

(b) Notes on installing and setting up multiple Performance Management programs on same host

With Performance Management, you can install PFM - Manager, PFM - Web Console, and PFM - RM for Oracle on the same host. When doing so, note the following:

• When PFM - Manager and PFM - RM for Oracle are installed on the same host, PFM - Base is not required. In this case, PFM - Manager is a prerequisite program for PFM - RM for Oracle and must be installed before PFM - RM for Oracle is installed.

• You cannot install PFM - Base and PFM - Manager on the same host. If you want to install PFM - Manager on a host on which PFM - Base and PFM - RM for Oracle are already installed, uninstall all Performance Management programs, and then install PFM - Manager and PFM - RM for Oracle in that order. The same applies when you install PFM - Base on a host on which PFM - Manager and PFM - RM for Oracle are already installed: you must uninstall all Performance Management programs, and then install PFM - Base and PFM - RM for Oracle in that order.

• If you install PFM - RM for Oracle on a host on which PFM - Manager is already installed, the connection-target PFM - Manager will be the instance of PFM - Manager on the local host, and cannot change it to that on the remote host. If you want PFM - RM for Oracle to connect to PFM - Manager on a remote host, ensure that PFM - Manager is not installed on the host on which you install PFM - RM for Oracle.

• If you install PFM - Manager on a host on which PFM - RM for Oracle is already installed, the connection-target PFM - Manager is reset to the local host. See the setting results that are output to the common message log.

• If you install PFM - RM for Oracle on a host on which PFM - Web Console in already installed, close all the browser windows before you install the program.

• 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 - RM for Oracle on separate hosts.

(c) Notes on upgrading PFM - RM for Oracle

Before you perform version upgrade installation, you need to perform the procedure described in 2.3.2(1) (c) Deleting the objects registered in the Oracle Database. Complete version upgrade installation and then perform the procedure in 2.1.4(3) (c) Registering objects in the Oracle Database.

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.

For details about notes on upgrading the version of PFM - RM for Oracle, see H. Migration Procedure and Notes on Migration.

For details about upgrading, see the JP1/Performance Management Planning and Configuration Guide.

(d) Other cautionary notes

• To use PFM - RM for Oracle to monitor an Oracle Database, you must install and set up Oracle Client 64-bit to connect to the Oracle Database.

  Note that you can select Administrator or Runtime as the installation type for Oracle Client 64-bit. Instant Client is not supported.

  When you mistook to install Oracle Client by using Instant Client as the installation type, do not install it by using [Administrator] or [Runtime] to the same ORACLE_HOME. In this case, install Oracle Client to the other ORACLE_HOME or install it after deleting Instant Client.

• If the monitoring-target program is Oracle Database 12c Release 1, the program can only be monitored in a non-CDB environment and cannot be monitored in a CDB environment.

• If the monitoring-target program is Oracle Database 12c Release 2 or later, in addition to the program in a traditional non-CDB environment, PDBs and the root container (CDB$ROOT) in a CDB environment can be monitored. Monitoring application containers (an application root and application PDBs) is not supported.

• When you perform a new installation of PFM - RM for Oracle in an environment where no other Performance Management program has been installed, make sure that there are no files or folders in the installation folder.

• You may be prompted to restart the system if you attempt to install PFM - RM for Oracle while another Performance Management program or service is running. Alternatively, you may be prompted to restart the system while Windows Event Viewer or another program that references Performance Management files is running. If this occurs, restart the system as indicated in the message, and complete the installation.

• The installer may be unable to expand the files required for installation if you attempt to install PFM - RM for Oracle in the following cases:

  • While a Performance Management program or service is running or while another program that references Performance Management files (for example, Windows Event Viewer) is running

  • When there is insufficient disk space

  • When you do not have the required folder permission

  Stop any active Performance Management programs or services or other programs that reference Performance Management files, and then perform the installation again. If the problem is caused by insufficient disk space or a lack of the appropriate folder permissions, fix the problem and then perform the installation again.

• When you install Performance Management programs, check whether the following security-related programs are installed. If they have been installed, take appropriate action according to the explanations below.

  • Security monitoring program

    Stop the security monitoring program or change the settings so that the installation of Performance Management programs will not be interrupted.

  • Virus detection program

    Stop the virus detection program before you install Performance Management programs.

    If a virus detection program is running during the installation of Performance Management programs, the installation processing might slow down, installation might not be executable, or the programs might not be able to be installed correctly.

  • Process monitoring program

    Stop the process monitoring program or change the settings. Also, specify settings that prevent the services or processes of Performance Management and common components from being monitored.

    If the process monitoring program starts or stops these services or processes during the installation of Performance Management programs, installation might fail.

• Do not specify the following folder as the installation-folder. If so, the installation process may fail:

  system-folder\Program files

• This software is a Hitachi program product that conforms to the disk copy installation of JP1/ServerConductor/Deployment Manager and Hitachi Compute Systems Manager Deployment Manager Plug-in, or the copy functionality using conversion to image files that is provided by a virtual platform. About the disk copy installation, see notes on installing replicated disks in the manual JP1/Performance Management Planning and Configuration Guide.