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

2.1.1 Before installing and setting up PFM - Agent for Platform

Before installing and setting up PFM - Agent for Platform, make sure that the requirements described below are satisfied.

Organization of this subsection

(1) Required OS

(2) Network environment setup

(3) OS user permission necessary for installation

(4) Prerequisite programs

(5) Environment configuration required for collecting performance data

(6) Notes

(1) Required OS

PFM - Agent for Platform can run on the following OSs:

• Windows Server 2003
• Windows Server 2008

(2) Network environment setup

The following explains the network environment that is necessary for Performance Management to operate.

(a) IP address setup

For the PFM - Agent host, you must set up an environment in which the IP address can be resolved using a host name. PFM - Agent cannot start in an environment in which the IP address 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 monitoring host name settings, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

Host names and IP addresses can be set using any of the following:

• The host information settings file for Performance Management (jpchosts file)
• hosts file
• DNS (Domain Name System)
  

  Note

  • Performance Management can be run on a DNS environment, but does not support host names in the FQDN (Fully Qualified Domain Name) format. Accordingly, leave out the domain name when setting monitoring host names.
  • If PFM - Agent for Platform is to be used in multiple LAN environments, set up the IP address in the jpchosts file. For details, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.
  • 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.

(b) Port number setup

The default port numbers shown in the table below are assigned to Performance Management program services. For any other services or programs, port numbers currently not in use in the system are automatically assigned when the service or program is started. When you are using Performance Management in an environment with a firewall, assign fixed port numbers. For details about how to fix port numbers, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

Table 2-1 Default port numbers and Performance Management program services (for Windows)

Service explanation	Service name	Parameter	Port number	Remarks
Service configuration information management function	Name Server	jp1pcnsvr	22285	Port number used by the Name Server service of PFM - Manager. This port number is set for all hosts in Performance Management.
OpenView linkage facility	NNM Object Manager	jp1pcovsvr	22292	Port number used by the OpenView linkage facility of PFM - Manager and PFM - Base for communicating between a map manager and an object manager. This port number is set for hosts in which 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 for hosts in which PFM - Manager and PFM - Base are installed.

Set up the network to enable these PFM - Agents to communicate using the assigned port numbers.

(3) OS user permission necessary for installation

When installing PFM - Agent for Platform, you must execute the installation procedure from an account that has the Administrators permission.

(4) Prerequisite programs

This subsection explains the prerequisite programs that are necessary for installing PFM - Agent for Platform. The figure below shows the program configuration.

Figure 2-1 Program configuration

(a) Monitoring target programs

PFM - Agent for Platform monitors the following programs:

• Windows Server 2003
• Windows Server 2008

These monitoring target programs and PFM - Agent for Platform must be installed on the same host.

(b) Performance Management programs

Install PFM - Agent and PFM - Base on the monitoring agent. PFM - Base is a prerequisite program for PFM - Agent. Even when installing multiple copies of PFM - Agent on the same host, you need only a single copy of PFM - Base.

However, if you are installing PFM - Manager and PFM - Agent on the same host, you do not need PFM - Base.

To use PFM - Agent for Platform to monitor the operation of Windows Server, you need PFM - Manager and PFM - Web Console.

The following table lists the versions of PFM - Manager and PFM - Base supported by PFM - Agent for Platform 09-00.

Table 2-2 Supported version of PFM - Manager of PFM - Base

OS	Supported version of PFM - Manager or PFM - Base
Windows Server 2003	08-00 or later
Windows Server 2008	09-00 or later

(5) Environment configuration required for collecting performance data

To collect performance data on the network environment required for running PFM - Agent for Platform, all network services, protocols, servers, and products must be installed before the Agent Collector service is started. Note that if the environment for the installed products is not configured, or if additionally installed services are not running, performance data will be collected, but data might not be obtained field values might be displayed as 0.

To collect performance data for specific records in PFM - Agent for Platform, the prerequisites shown in the following table need to be satisfied before the Agent Collector service is started. Note that the following table does not include services required for OS operation, such as Event Logs (service name: Eventlog).

The following table describes the prerequisites for collecting performance data.

Table 2-3 Prerequisites for collecting performance data

Category	Record name (record ID)	Field name (PFM - View name)	Prerequisites
OS	Logical Disk Overview (PI_LOGD)	Page File Size Mbytes (PAGE_FILE_SIZE_BYTES)	Windows Management Instrumentation (service name: WinMgmt) has started. Note: This is only required for Windows Server 2003 and Windows Server 2008.
	System Overview (PI)	System Type (SYSTEM_TYPE)
Network services	Browser Overview (PI_BRSR)	All	Computer Browser (service name: Browser) has started.
	WINS Server Overview (PI_WINS)	All	Windows Internet Name Service (WINS) has been installed, and subsequently added services have been started.
	Server Work Queues Overview (PI_SVRQ)	All	Server (service name: LanmanServer) has started.
	System Overview (PI)	Blocking Reqs Rejected (BLOCKING_REQUESTS_REJECTED)
		Bytes Rcvd/sec (BYTES_RECEIVED_PER_SEC)
		Bytes Total/sec (BYTES_TOTAL_PER_SEC)
		Bytes Xmitd/sec (BYTES_TRANSMITTED_PER_SEC)
		Context Blocks Queued/sec (CONTEXT_BLOCKS_QUEUED_PER_SEC)
		Errors Access Permissions (ERRORS_ACCESS_PERMISSIONS)
		Errors Granted Access (ERRORS_GRANTED_ACCESS)
		Errors Logon (ERRORS_LOGON)
		Errors System (ERRORS_SYSTEM)
		File Directory Searches (FILE_DIRECTORY_SEARCHES)
		Files Open (FILES_OPEN)
		Files Opened Total (FILES_OPENED_TOTAL)
		Logon Total (LOGON_TOTAL)
		Logon/sec (LOGON_PER_SEC)
		Pool Nonpaged Failures (POOL_NONPAGED_FAILURES)
		Pool Nonpaged Peak (POOL_NONPAGED_PEAK)
		Pool Paged Failures (POOL_PAGED_FAILURES)
		Pool Paged Peak (POOL_PAGED_PEAK)
		Server Pool Nonpaged Bytes (SERVER_POOL_NONPAGED_BYTES)
		Server Pool Paged Bytes (SERVER_POOL_PAGED_BYTES)
		Server Sessions (SERVER_SESSIONS)
		Sessions Errored Out (SESSIONS_ERRORED_OUT)
		Sessions Forced Off (SESSIONS_FORCED_OFF)
		Sessions Logged Off (SESSIONS_LOGGED_OFF)
		Sessions Timed Out (SESSIONS_TIMED_OUT)
		Work Item Shortages (WORK_ITEM_SHORTAGES)
Active Directory	Active Directory Overview (PI_AD)	Cache % Hit	Active Directory is enabled, and the Active Directory database performance counter has been installed. Note: On Windows Server 2003 (x64) and the 64-bit version of Windows Server 2008, the wmiadap /f command needs to be executed from the DOS prompt, and the OS needs to be restarted.
		Cache Page Fault Stalls/sec
		Cache Page Faults/sec
		Cache Size
		Log Record Stalls/sec
		Log Threads Waiting
		Log Writes/sec
		Table Open Cache % Hit
		Table Open Cache Hits/sec
		Table Open Cache Misses/sec
		Table Opens/sec
		Anything other than the above	Active Directory is enabled.

(6) Notes

Note the following points when installing and setting up Performance Management.

(a) Precautions regarding the registry

PFM - Agent for Platform 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

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

• If you are installing PFM - Manager and PFM - Agent on the same host, you do not need PFM - Base. In this case, because the prerequisite program for PFM - Agent is PFM - Manager, install PFM - Manager first, and then install PFM - Agent.
• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on the host on which PFM - Base and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. To install PFM - Base on the host on which PFM - Manager and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - Agent.
• When you install PFM - Agent on a host on which PFM - Manager is installed, PFM - Manager of the local host becomes PFM - Manager for the connection destination. In this case, you cannot change PFM - Manager for the connection destination to PFM - Manager of a remote host. To connect to PFM - Manager of a remote host, make sure that PFM - Manager is not installed on the host on which you want to install PFM - Agent.
• When you install PFM - Manager on a host on which PFM - Agent is installed, PFM - Manager for the connection destination of PFM - Agent is reset to the local host name. Check the setting results that are output to the common message log.
• To install PFM - Agent on a host on which PFM - Web Console is installed, close all browser windows before installing PFM - Agent.
• When a Performance Management program is newly installed, the status management function is enabled as the default. However, if you upgrade from version 07-00 to 08-00 or newer, the settings for the status management function remain the same as they were in the older version. For details about how to change the settings for the status management function, see the chapter explaining error detection in Performance Management in the manual Job Management Partner 1/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

Note the following points when upgrading PFM - Agent from an older version to a newer one:

For details about upgrading, see the appendix in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

• Before installing a Performance Management program, stop all Performance Management programs and services of the local host. For details about how to stop services, see the chapter explaining how to start and stop Performance Management in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.
• When installing PFM - Agent on a host on which Performance Management programs are already installed, the installation path for PFM - Agent is the same as the installation path for the Performance Management programs, other than PFM - Web Console, that are already installed. To change the installation path, you need to delete all Performance Management programs, other than PFM - Web Console, that are already installed, and then reinstall them.
• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on the host on which PFM - Base and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. To install PFM - Base on the host on which PFM - Manager and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - Agent.
• In Performance Management programs of version 08-00 or later, the locations of the Store execution programs (jpcsto.exe and stpqlpr.exe) have been changed. When PFM - Agent is upgraded to version 08-00 or later, the Store execution modules in the previous locations are deleted.
• During upgrade installation, because the existing Store database is automatically upgraded, twice as much disk capacity as that needed for the Store database is temporarily required. Before performing an upgrade installation, make sure that the disk on which the Store database is stored has sufficient free space.

(e) Other notes

• If you install PFM - Agent for Platform while another Performance Management program or service is running, or while another program (such as Windows Event Viewer) that might reference Performance Management files is running, a message prompting a system restart might be displayed. In this case, follow the message and restart the system to complete the installation.
• If you install PFM - Agent for Platform while another Performance Management program or service is running, while another program (such as Windows Event Viewer) that might reference Performance Management files is running, while there is insufficient disk space, or while a folder permission is not valid, file expansion might fail. If any Performance Management programs or services are running, or if any other programs that reference Performance Management files are running, stop all these programs first, and then re-install PFM - Agent for Platform. If disk space shortage or invalid folder permission is a problem, resolve these issues first, and then reinstall.
• 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.
    

[Contents][Back][Next]

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