2.1.2 Before installation and setup
(1) Requisite OS
PFM - Agent for Service Response can run on the following operating system (OS):
- Windows Server 2003
- Windows Server 2008
(2) Network environment setup
This subsection describes the network environment needed for Performance Management operation.
(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 Job Management Partner 1/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 Job Management Partner 1/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 Server 2008 R2 runs on a host with PFM - Agent for Service Response installed and Windows Server 2008 R2 or Linux runs on a host with PFM - Manager installed.
For details about the scope of communication in IPv4 and IPv6 environments, see L. 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. The following describes when you need to execute this command.
- Cases when the jpcconf ipv6 enable command needs to be executed:
- When switching from an IPv4 environment to an IPv6 environment on each host
- When switching the PFM - Manager environment from IPv4 to IPv6 in an environment in which both IPv4 and IPv6 are used
- Cases when the jpcconf ipv6 enable command does not need to be executed:
- When each host already operates in an IPv6 environment
- When PFM - Manager operates in an IPv6 environment in an environment in which both IPv4 and IPv6 are used
The following shows an example of executing the jpcconf ipv6 enable command:
jpcconf ipv6 enable
For details about the jpcconf ipv6 enable command, see the chapter that describes commands in the manual Job Management Partner 1/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 Job Management Partner 1/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 Job Management Partner 1/Performance Management Planning and Configuration Guide.
Table 2-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. |
OpenView linkage facility | NNM Object Manager | jp1pcovsvr | 22292 | Port number used for communication between map manager and object manager when the OpenView linkage facility is used with PFM - Manager and PFM - Base. This port number is set at the host where 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 at the host where PFM - Manager and PFM - Base are installed. |
JP1/ITSLM linkage facility | JP1/ITSLM | -- | 20905 | The port number set by JP1/ITSLM. |
- Legend:
- --: None
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.
(3) OS user permission necessary for installation
Make sure that you are using an account that has Administrator permissions when you install PFM - Agent for Service Response.
(4) Required programs
This subsection describes the programs that are required to install PFM - Agent for Service Response. The following figure shows the configuration of the programs.
Figure 2-2 Program configuration
![[Figure]](figure/zuv02010.gif)
PFM - Agent, PFM - Base, and Microsoft XML Parser 3.0 must be installed on the monitoring agent. PFM - Base and Microsoft XML Parser 3.0 is a prerequisite program for PFM - Agent. You need only one PFM - Base even when multiple PFM - Agents are installed on the same host.
Note that if you install PFM - Manager and PFM - Agent on the same host, PFM - Base is not required.
To use PFM - Agent for Service Response to measure and monitor Internet services, you need PFM - Manager and PFM - Web Console.
The response information measured by PFM - Agent for Service Response consists of the response times when a target service is accessed from the machine where PFM - Agent for Service Response is installed. If you install PFM - Agent for Service Response at a location close to the service user's terminal, you can obtain data that is closer to the actual response times experienced by the service user.
The following programs are prerequisite for the IE Recorder and IE Probe Daemon. These programs must be installed on the same host:
- Microsoft .NET Framework 2.0
- Windows Internet Explorer 7, Windows Internet Explorer 8, Windows Internet Explorer 9, or Windows Internet Explorer 10
(5) Installing and setting up in a cluster system
The required network environment and program configuration are different for a cluster system than for a normal non-cluster system. In a cluster system, installation and setup are required at both the executing and standby nodes. For details, see 5. Operation in a Cluster System.
(6) Preparation for collecting data in the event of an error
If a problem occurs, memory dumps, crash dumps, user mode process dumps, and other data might be required. To obtain these dumps when a problem has occurred, use one of the following methods to set up output of these dumps in advance.
(a) Setting method for Windows Server 2003
- Settings for outputting memory dumps:
- In Control Panel, double-click System.
- On the Advanced page, click the Settings button for Startup and Recovery.
- In Write debugging information, select Complete Memory Dump and then specify the output destination file.
- Note
- The size of a memory dump differs depending on the size of actual memory. The greater the installed physical memory, the greater the memory dump size. Accordingly, make sure you have enough disk space to collect the memory dumps. For details, see the OS documentation.
- Settings for outputting crash dumps:
- Select Start and then Run.
- Type drwtsn32 in the text box, and click the OK button. The Dr. Watson for Windows dialog box appears.
- Select the Create Crash Dump File check box, and specify the output destination file in the Crash Dump text box.
- Click the OK button.
- Note
- Not only JP1 information, but also the error information for other application programs is output in crash dumps, with potential adverse effects on available disk space. If you specify that crash dumps are to be output, make sure that you have enough disk space for them.
(b) Setting method for Windows Server 2008
- Settings for outputting user mode process dumps:
- You can use the following registry setting to obtain user mode process dumps of data that you can investigate for troubleshooting when an application program terminates:
\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
- Specify the following registry key values:
- DumpFolder: REG_EXPAND_SZ dump-output-folder-name
Permission to write to the output destination folder is needed.
- DumpCount: REG_DWORD Number-of-dumps-to-be-saved
- DumpType: REG_DWORD 2
- Note
- When you set the registry to output user mode process dumps, user mode process dumps are output for not only JP1 programs, but also for other application programs. Make sure you keep this in mind when you specify that user mode process dumps are to be output.
- When user mode process dumps are output, available disk space can be adversely affected. Make sure that you specify a dump output folder that has enough disk space for the dumps.
(7) Notes
This subsection provides notes about installing and setting up Performance Management.
(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 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:
- 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 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 re-install 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.
- 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.
- If the data model version of the Store database is changed during an upgrade, the existing Store database is automatically upgraded. As a result, twice as much disk space 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. Estimate the required free 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 upgrade installation requires at least 200 GB of free space. If you changed the disk on which the Store database is installed, estimate the free space on the disk after the change.
- 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.