5.1.1 Before installation and setup

(a) IP address settings

Set up an environment in which host names of all the hosts in a Performance Management system can be resolved to IP addresses (IP addresses do not need to be resolved to host names). Performance Management cannot be installed if the environment does not provide the ability to resolve IP addresses.

You can use the real host name or the alias name as the monitoring host name (the host name for the Performance Management system). However, we recommend that you use aliases to minimize the influence caused by changing host names in the real environment.

• When using the alias name as the monitoring host name

  Configure the environment so that the IP address can be resolved with the specified alias name.

• When using the real host name as the monitoring host name

  Configure the environment so that the IP address can be resolved with the host name that has been obtained by executing either the hostname command (Windows system) or uname -n command (UNIX system).

  For a UNIX system, you can also use the host name obtained with the hostname command. For details, see 6.3.3 Specifying and changing the monitoring host name in a Performance Management system.

For details about how to set a monitoring host name, see 5.3.3 Specifying and changing the monitoring host name in a Performance Management system.

Use one of the following methods to specify host names and IP addresses:

• hosts file

• DNS

• Host information configuration file for Performance Management

  • jpchosts file (for PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base)

Notes:

• Performance Management can be used in a DNS environment but does not support FQDN. Therefore, you must exclude the domain name when you specify the monitoring host name.

• Use the jpchosts file to set IP addresses if you run the system in multiple LAN environments. For details, see 5.3.1 Specifying and changing the network configuration.

• Performance Management cannot be used in a DHCP environment on hosts which IP addresses are dynamically allocated. You must allocate fixed IP addresses to all hosts where Performance Management is installed.

• A loopback address cannot be specified as the IP address of a host name that is to be resolved.

• A loopback address must be specified for localhost in the hosts file.

• If two or more host names are assigned to the PFM - Manager host, you must specify the name of the connection-target PFM - Manager host that is to be used, as described below, in the jpcconf mgrhost define command on the PFM - Agent or PFM - RM host in the system.

  When the real host name is used as PFM - Manager's monitoring host name:

  Host name obtained by executing the hostname command in a Windows system or the uname -n command in a UNIX system

  When an alias is used as PFM - Manager's monitoring host name:

  Alias name that has been specified

• If IP address translation (NAT) is performed between the PFM - Manager host and the PFM - Web Console host and JP1/ITSLM host, or multiple IP addresses are used between the PFM - Manager host and the PFM - Web Console host and JP1/ITSLM host, the host name to be used for communication must be specified.

  For details, see the section that describes the specification of host names used for communication between PFM - Manager and PFM - Web Console and between PFM - Manager and JP1/ITSLM in the appendix of the manual Job Management Partner 1/Performance Management Reference.

• In a Performance Management system, the host names of servers and the aliases used as monitoring host names must be unique.

  The method of checking the host names of servers differs depending on how monitoring host names were determined.

  When the hostname command was used to obtain a real host name used as a monitoring host name: Use the hostname command to check.

  When the uname command was used to obtain a real host name used as a monitoring host name: Use the uname -n command to check.

• In a Performance Management system, the IP addresses of hosts must be unique.

(b) Port number settings

The port numbers listed in the following table are assigned to the Performance Management program services by default. For other services or programs, a port number not in use by the system at that time, is automatically assigned each time a service is started up. Use fixed port numbers if you use Performance Management in a firewall environment. For details about the procedure to fix port numbers, see 5.3.1(1)(c) Setting port numbers.

Table 5‒2: Default port numbers and Performance Management program services (in Windows)

Service	Service name	Parameter	Port number	Note
Service configuration information management function	Name Server	jp1pcnsvr	22285	The port number used by the PFM - Manager Name Server service. This port number is set for all hosts for Performance Management.
NNM linkage function	NNM Object Manager	jp1pcovsvr	22292	The port number used for communications between a map manager and object manager in the NNM linkage facility of PFM - Manager and PFM - Base. This port number is set on a host where PFM - Manager or PFM - Base is installed.
Service status management function	Status Server	jp1pcstatsvr	22350	The port number used by the Status Server service in the PFM - Manager and PFM - Base. This port number is set on a host where PFM - Manager or PFM - Base is installed.
Monitoring console communication function	View Server	jp1pcvsvr	22286	The port number used by View Server service in PFM - Manager. This port number is set on PFM - Manager hosts.
Web Service function	Web Service	--	20358	The port number used by the service of Web Service in PFM - Web Console. This is used for communication between the monitoring console's Web browser and the PFM - Web Console host.
Web Container function	Web Console	--	20359 20360	The port number used by Web Console service in PFM - Web Console.

Set the network settings so that Performance Management can communicate through these port numbers.

(a) Programs required for the monitoring manager

PFM - Manager is required for the monitoring manager. Also, JP1/Base is required on the same host running PFM - Manager to enable integrated authentication for JP1 users. For details, see the chapter that describes management of user accounts and business groups in the appropriate JP1/Base manual and the Job Management Partner 1/Performance Management User's Guide.

(b) Programs required for the monitoring console server

PFM - Web Console is required for the monitoring console server.

(c) Programs required for the monitoring agent

PFM - Agent or PFM - RM and PFM - Base are required for the monitoring agent. Since the PFM - Base program is required for PFM - Agent or PFM - RM, install PFM - Base first and then install PFM - Agent or PFM - RM.

However, PFM - Base is not required if you install PFM - Manager and either PFM - Agent or PFM - RM on the same host. In such cases, since PFM - Manager is the required program for PFM - Agent or PFM - RM, install PFM - Manager first and then install PFM - Agent or PFM - RM.

The programs to be monitored differ per the PFM - Agent or PFM - RM. For details about the programs monitored by PFM - Agent or PFM - RM, see the appropriate PFM - Agent or PFM - RM manual.

(d) Programs required for the monitoring console

A Web browser is required for the monitoring console in order to check the operation monitoring data collected by Performance Management or to change Performance Management settings.

Either of the following Web browsers is required for Performance Management:

• Internet Explorer

• Firefox

The settings for PFM - Web Console differ depending on the kind of Web browsers. For details, see the Release Notes.

(a) Specifying settings in Windows Server 2003

Memory dump output settings

1. From Control Panel, double-click System.

2. On the Advanced page, click the Settings button in Startup and Recovery.

3. In Write debugging information, select Kernel memory dump, and then specify the output file.

Note:

The size of a memory dump depends on the size of the real memory. If the installed physical memory is large, a memory dump will also be large. Allocate enough disk space for the memory dump. For details, see the OS documentation.

Crash dump output settings

1. From the Start menu, select Run.

2. In the text box, enter drwtsn32, and then click the OK button.

   The Dr. Watson dialog box is displayed.

3. Select the Create Crash Dump File check box, and then specify the output file in the Crash Dump text box.

4. Click the OK button.

Note:

The information that is output to a crash dump includes not only the JP1 error information but also error information from other application programs. A crash dump uses a large amount of disk space. If you set crash dumps to be output, provide sufficient disk space.

(b) Specifying settings in Windows Server 2008 or Windows Server 2012

• User mode process dump output settings

  If you specify the registry shown below, you can obtain user mode process dumps as data to aid in an investigation after application programs terminate abnormally:

  \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

  Specify the following registry values in this registry key:

  • DumpFolder : REG_EXPAND_SZ dump-output-folder-name

    (Write permission is required for the output folder)

  • DumpCount : REG_DWORD number-of-dumps-to-be-retained

  • DumpType : REG_DWORD 2

Note:

• Once you set this registry, user mode process dumps will be output not only for JP1 programs but also for other application programs. Keep this is mind when you set user mode process dumps to be output.

• A user mode process dump uses a large amount of disk space. If you set user mode process dumps to be output, specify a dump output folder that has sufficient disk space.

(a) Notes on environment variables

Do not manually set JPC_HOSTNAME as an environment variable, because it is used for Performance Management as an environment variable. If this setting is made, Performance Management will not run correctly.

(b) Notes on installation and setup of multiple Performance Management programs on a single host

You can also install the following Performance Management programs on the same host:

• PFM - Manager

• PFM - Web Console

• PFM - Agent or PFM - RM

Supplemental information:

To improve system performance and reliability, we recommend that you run PFM - Manager, PFM - Web Console, PFM - Agent, and PFM - RM on separate hosts.

• PFM - Base is not required if you install PFM - Manager and either PFM - Agent or PFM - RM on the same host. In such cases, because PFM - Manager is required for PFM - Agent or PFM - RM, install PFM - Manager first and then install PFM - Agent or PFM - RM.

• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on a host that has PFM - Base and either PFM - Agent or PFM - RM installed, uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager and either PFM - Agent or PFM - RM, in that order. To install PFM - Base on a host on which PFM - Manager and either PFM - Agent or PFM - RM is installed, first, uninstall all Performance Management programs except PFM - Web Console and then install PFM - Base and either PFM - Agent or PFM - RM, in that order.

• If you install PFM - Agent or PFM - RM on a host that has PFM - Manager installed, PFM - Manager for the connection destination of PFM - Agent or PFM - RM is set to PFM - Manager on the local host. In such cases, you cannot change PFM - Manager for the connection destination of PFM - Agent or PFM - RM to PFM - Manager on the remote host. If you want to connect to PFM - Manager on the remote host, make sure that PFM - Manager is not installed on a host on which PFM - Agent or PFM - RM is to be installed.

• When you install Performance Management programs on a host that has PFM - Web Console installed, close all the Web browser windows first, and then install the programs.

• If you use the function for setting monitoring-host names, you cannot install PFM - Agent 07-00 or earlier on the same host. If you want to install PFM - Agent 07-00 or earlier, you must reset the setting so that the function for setting monitoring-host names is not used. If you do not reset the setting, the installation of PFM - Agent 07-00 or earlier might fail. For details about how to set a monitoring host name, see 5.3.3 Specifying and changing the monitoring host name in a Performance Management system.

(c) Notes on version upgrade

The following gives cautionary notes on upgrading older versions of Performance Management programs:

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

• When you install a Performance Management program (except for PFM - Web Console), stop all of the Performance Management programs and services on the local host. When you install PFM - Web Console, stop existing PFM - Web Console on the local host. All services on the physical host and logical host must be stopped. For details about how to stop services, see the chapter that describes starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.

• Except in the case of PFM - Web Console, the installation path is the same as the first program when you install another Performance Management program on a host that already has a Performance Management program installed. To change the installation path, you must delete all installed Performance Management programs and then re-install the same programs.

• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on a host that has PFM - Base and either PFM - Agent or PFM - RM installed, uninstall all Performance Management programs except PFM - Web Console and then install PFM - Manager and either PFM - Agent or PFM - RM, in that order. To install PFM - Base on a host on which PFM - Manager and either PFM - Agent or PFM - RM is installed, first, uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base and either PFM - Agent or PFM - RM, in that order.

• Note that the location of the executable files for the Store service (jpcsto.exe and stpqlpr.exe) has been changed in versions 08-00 and later of the Performance Management programs. When you upgrade PFM - Manager and PFM - Agent to version 08-00 or later, the executable files for the Store service will be deleted from their former location.

• If you want to upgrade the operating system to Windows Server 2008 or Windows Server 2012, you must uninstall temporarily the Performance Management programs for Windows Server 2003. This is because these programs might not function correctly on Windows Server 2008 or Windows Server 2012. First, uninstall all Performance Management programs, and then perform the upgrade. Finally, install the Performance Management programs for Windows Server 2008 or Windows Server 2012.

• For the upgrade installation, the destination disk temporarily requires twice as much free space as the Store database. Securing this free space enables the existing Store database to be automatically upgraded. Confirm that there is sufficient free disk space in the destination disk before performing the upgrade installation.

  Determine the required amount of free disk space based on the total size of the current Store database. For example, if the total size of the current Store database is 100 GB, the free disk space required for upgrading will be at least 200 GB. If you have changed the disk used for storing the Store database, determine the required free disk space based on the capacity of the new disk after the change.

(d) Notes on PFM - Web Console installation

The following gives cautionary notes on installing PFM - Web Console:

• The Windows initialization file (config.xml) stored in installation-folder\conf\ is not updated if you overwrite PFM - Web Console when installing. However, the config.xml file stored in the installation-folder\sample\conf\ is updated.

• You must restart the system to enable the PFM - Web Console settings when installing a new PFM - Web Console.

(e) Notes on linking with other systems

• When you install the program in an environment that is linked with Network Node Manager, stop the NNM linkage facility and ovw, and then install the program. For details about the NNM linkage facility, see the chapter that describes the linkage with Network Node Manager (NNM) for operation monitoring in the Job Management Partner 1/Performance Management User's Guide. For the Network Node Manager environment variables and commands, see the HP NNM documentation.

(f) Other related notes

• If you install a new Performance Management program into an environment that does not have a Performance Management program installed, make sure there are no files or folders in the installation folder.

• A message that prompts you to restart the system might be displayed if you install a Performance Management program while other Performance Management programs or services are running or programs that reference Performance Management files (such as Windows Event Viewer) are running. In such instances, restart the system according to the displayed message to complete the installation.

• Expanding files or folders might fail if you install Performance Management programs while other programs or services are running, programs that reference Performance Management files (such as Windows Event Viewer) are running, the disk capacity is insufficient, or you do not have permission for the installation directory. If other Performance Management programs or services are running or programs that reference Performance Management files (such as Windows Event Viewer) are running, exit all programs and then perform the installation again. If the problem is caused by insufficient disk space or insufficient directory permission, resolve the problem, and then perform the installation again.

• When you install the Performance Management programs, make sure that the following security-related programs have not been installed. If they have been installed, follow the instructions below:

  • Security-monitoring program

    Terminate the security-monitoring program, or change the settings so that the program does not interfere with the installation of the Performance Management programs.

  • Virus detection program

    Stop virus detection programs before installing the Performance Management programs.

    If a virus detection program is running, the installation might be slower, the installation might be aborted, or the programs might not be installed correctly.

  • Process-monitoring program

    Stop process-monitoring programs, or change the settings so that the programs do not monitor the services and processes of Performance Management or shared components.

    If these services or processes are started or terminated by a process-monitoring program while installing the Performance Management programs, the installation might fail.

• If you will be installing Performance Management programs, check for the Windows standard service Application Experience Lookup Service or Application Experience. If you find such a service, first start it, and then install the products.

• When you install version 08-00 or later of a Performance Management program, the setting for the status management function is as follows:

  • After a new installation of version 08-00 or later of PFM - Manager or PFM - Base on a host that does not already have a Performance Management program installed

    Status management function setting: Enabled

  • Other cases^#

    Status management function setting: Remains the same

  #: The following fall under the other cases category:

  • Upgrading version 06-70 to 07-10 of PFM - Manager to version 08-00 or later

  • Performing a new installation of version 08-00 or later of PFM - Manager or PFM - Base in an environment where version 06-70 to 07-00 of PFM - Agent is installed

  Because 06-70 to 07-10 versions of Performance Management do not have the status management function, the setting status in this case becomes disabled.

  For details about changing the settings of the status management functions, see the chapter that describes detecting problems in Performance Management in the Job Management Partner 1/Performance Management User's Guide.

• You can use the health check function with PFM - Manager version 08-11 or later. Depending on the PFM - Manager version and your installation environment, the settings of the health check function are as follows.

  • After a new installation of version 09-00 or later of PFM - Manager on an environment that does not already have a Performance Management program installed

    Health check function setting: Enabled

  • Other cases^#

    Health check function setting: Remains the same

  #: The following are under the other cases category:

  • Upgrading version 06-70 to 08-00 of PFM - Manager to version 08-11 or later

  • Newly installing PFM - Manager version 08-11 or later in an environment in which PFM - Agent version 06-70 to 07-00 has been installed

  Because PFM - Manager versions 06-70 to 08-00 do not support the health check function, the health check function is set to Disabled.

  For details about the health check function settings, see the chapter that describes detecting problems in Performance Management in the Job Management Partner 1/Performance Management User's Guide.

• If the installation folder is displayed by Explorer during installation, close Explorer.

• If the installation folder is displayed in the Command Prompt window during installation, close the window.

• You can install PFM - Manager and specify it as the connection destination of the PFM - Web Console services while those services are running. However, you must then restart PFM - Web Console. If you do not, the functions of PFM - Manager might become unavailable.