Job Management Partner 1/Performance Management Planning and Configuration Guide
This subsection describes what you need to confirm before installing and setting up Performance Management. For details on notes on Windows Server 2008, see 4.8.3 Notes on using Windows Server 2008.
- Organization of this subsection
- (1) Supported OSs
- (2) Determining the system configuration
- (3) Network environment settings
- (4) OS user permission required for installation
- (5) Required programs
- (6) Installation and setup in a cluster system
- (7) Notes
The following table lists supported OSs for the Performance Management programs.
Table 5-1 Supported OSs (in Windows)
OS name PFM - Manager PFM - Web Console PFM - Base Windows Server 2003 Y Y Y Windows Server 2008 Y Y Y
- Legend:
- Y: Supported
PFM - Agent and PFM - RM support different OSs. For details, see the appropriate PFM - Agent or PFM - RM manual.
(2) Determining the system configuration
Determine the number of instances of PFM - Agent or PFM - RM that connect to PFM - Manager. For details on how to estimate the number of instances, see A.1 System configuration.
(3) Network environment settings
This subsection describes the network environment required to run Performance Management.
(a) IP address settings
Specify an environment in which the IP addresses can be resolved by host names for all hosts in the Performance Management system. 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).
- 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 Changing the host name in a Performance Management system.
- 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.
For details on how to set a monitoring host name, see 5.3.3 Changing the host name in a Performance Management system.
Use one of the following methods to specify host names and IP addresses:
- hosts file
- Domain Name System (DNS)
- Host information configuration file for Performance Management
- jpchosts file (for PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base)
- config.xml file (for PFM - Web Console)
- Notes:
- Performance Management can be used in a DNS environment but does not support FQDN (Fully Qualified Domain Name). 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 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.
(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 on the procedure to fix port numbers, see 5.3.1(1)(b) 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. OpenView linkage function NNM Object Manager jp1pcovsvr 22292 The port number used for communications between a map manager and object manager in the OpenView 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. Web Container function Web Console -- 20359
20360The port number used by Web Console service in PFM - Web Console.
- Legend:
- --: Not applicable
Set the network settings so that Performance Management can communicate through these port numbers.
(4) OS user permission required for installation
Always use an account that has OS Administrators permissions when you install the Performance Management programs.
(5) Required programs
This subsection describes required programs to install Performance Management. The following figure describes the configuration of the required programs.
Figure 5-1 Program configuration
- Notes:
- An SMTP server is required to send emails when alarm events are reported to the system administrator via emails. For details, see the chapter that describes the operation monitoring with alarms in the Job Management Partner 1/Performance Management User's Guide.
- The required programs might differ if you use linkage functions between Performance Management and other systems. For details on the linkage facility, see the chapter that describes the linkage with the integrated management product JP1/IM for operation monitoring, and the linkage with Network Node Manager (NNM) for operation monitoring in the Job Management Partner 1/Performance Management User's Guide.
(a) Programs required for the monitoring manager
PFM - Manager is required for the monitoring manager. Also, JP1/Base is required for JP1 users to perform integrated authentication. For details, see the chapter that describes user account management 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
Install PFM - Base and either PFM - Agent or PFM - RM 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 on 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 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.
The following browser is required for Performance Management when you are using the monitoring console in a Windows environment:
- Internet Explorer 6.0 or later, Firefox 2.0.x, or Firefox 3
The supported browsers differ depending on the version of PFM - Web Console. For details, see 5.1.6 Procedure for setting up the monitoring console browser.
(6) Installation and setup in a cluster system
For installation and setup in a cluster system, the required network environment and program configuration differ from the setup in usual configurations. Also, you need to perform procedures on the executing and standby nodes. For details, see the chapter that describes the cluster system configuration and operation in the Job Management Partner 1/Performance Management User's Guide.
(7) Notes
This subsection gives cautionary notes on installing and setting up Performance Management.
(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
Note the following about installing multiple programs:
- 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 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 (set 0 for the Get Host Mode label). If you do not reset the setting, the installation of PFM - Agent 07-00 or earlier might fail. For details on how to set a monitoring host name, see 5.3.3 Changing the host name in a Performance Management system.
- Hint
- We recommend that you operate PFM - Manager, PFM - Web Console, PFM - Agent, and PFM - RM on separate hosts in order to improve the system performance and reliability.
The following gives cautionary notes on upgrading older versions of Performance Management programs:
For details on upgrading, see E. Migration Steps and Notes on Migration.
- When you install a new Performance Management program, stop all of the Performance Management programs and services at the local host. All services on the physical host and logical host must be stopped. For details on 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, you must temporarily uninstall the Performance Management programs for Windows Server 2003. This is because the operation of these programs on Windows Server 2008 might not be correct. First uninstall all Performance Management products, and then perform the upgrade. Finally, install the Performance Management programs for Windows Server 2008.
- 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.
(d) Notes on PFM - Web Console installation
The following gives cautionary notes on installing PFM - Web Console:
- The value of the %SystemDrive% environmental variable is referenced as the log output folder during the installation of the program. The log file is not output if the %SystemDrive% environment variable is not defined. In Windows Server 2008, the value of the %SYSTEMROOT% environment variable is referenced.
- The log data recorded during the installation is output to %SystemDrive%\pfmwebconinst.log. Also, the installer end code is output to %SystemDrive%\pfmwebconinst.rtn. The log file output from the installer is copied to the installation-folder\log directory before the installation ends. In Windows Server 2008, the log file is output to %SYSTEMROOT%\TEMP\HCDINST\product-model-name.LOG.
- If the installation fails, back up the log data (%SystemDrive%\pfmwebconinst.log) recorded during the installation, remove the cause of the problem, uninstall PFM - Web Console, and then perform the installation again.
- 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 OpenView linkage facility and ovw, and then install the program. For details on the OpenView 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
Before installing the Performance Management programs, we recommend that first you stop virus detection 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.
- When you install version 08-00 or later of a Performance Management program, the setting for the status management function is as follows:
# The following fall under the other cases category:
- 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
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.
- 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
For the procedure to change 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.
Because 06-70 to 08-00 versions of PFM - Manager do not have the health check function, the setting status in this case becomes disabled. For details on configuring the health check function, see the chapter that describes detecting problems in Performance Management in the Job Management Partner 1/Performance Management User's Guide.
- 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
- After a new installation of version 09-00 or later of PFM - Manager on an environment that already has a Performance Management program installed
Health check function setting: Disabled
- After a new installation of version 08-11 of PFM - Manager
Health check function setting: Disabled
- Upgrading version 06-70 to 08-00 of PFM - Manager to version 08-11 or later
Health check function setting: Disabled
- Upgrading version 08-11 or later of PFM - Manager
Health check function setting: Setting prior to upgrading is used.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.