4.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 5.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 4.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 4.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 static 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/SLM host, or multiple IP addresses are used between the PFM - Manager host and the PFM - Web Console host and JP1/SLM 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/SLM in the appendix of the manual JP1/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 4.3.1(1)(c) Setting port numbers.

Table 4‒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.
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# 20368# 20369#	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 JP1/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

• Google Chrome

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

(a) Notes on environment variables

Notes on environment variables are provided below.

• Do not manually set any environment variables used with Performance Management as an environment variable. If this setting is made, Performance Management will not run correctly. For details, see the chapter describing the environment variables used with Performance Management in the manual JP1/Performance Management Reference.

• When you install the Performance Management program version 11-50 or later, the path to the location to which to store commands is added to the system environment variable PATH. When the total length of the strings set for the system environment variable PATH (that is, the value already set for this variable plus the path to the location to which to store commands) exceeds 2,047 characters, however, a message dialog box appears.

  In this case, the installation of the Performance Management program ends successfully, but the path to the location to which to store commands is not added to the system environment variable PATH.

(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 4.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 Appendix 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 JP1/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.

• For the upgrade installation of PFM - Manager, PFM - RM or PFM - Agent, if the data model version is updated, 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.

• When an upgrade installation of PFM - Manager, PFM - RM or PFM - Agent is performed, if the data model version is updated, the existing Store database is automatically updated. Depending on the size of the Store database, the installation process might be taken of tens of minutes.

• When an upgrade installation of PFM - Manager or PFM - Agent that uses version 1.0 of the Store database is performed, if the data model version is updated, the size of each Store database file (*.DB or *.IDX) increases to a maximum of 1.8 GB after the data model is updated. If the ulimit command has been used to limit the file size or file system, the maximum file size will be either 90% of the limit or 1.8 GB, whichever is smaller.

  If the size of a file after an upgrade is performed exceeds the maximum file size, the data that exceeds the maximum size is deleted, and the message KAVE05834-W is output to the common message log. The following rules are used to select the data to be deleted:

  • For a PD/PL/PA database:

    The data is sequentially deleted starting with the oldest collection time.

  • For a PI database:

    Data is sequentially deleted based on the summarization category, in the following order: minute, hour, day, week, month, year. Within each summarization category, the data is sequentially deleted starting with the oldest collection time.

• When an upgrade installation of PFM - Manager, PFM - RM or PFM - Agent is performed, if the data model version is updated, the upgrade installation will fail if the size of Store database files (*.DB or *.IDX) exceed 2.0 GB.

  To successfully perform an upgrade installation, initialization must be performed. Initialize the Store database as described below, and then perform the upgrade installation.

  1. Stop the PFM service.

     Stop the PFM services whose database file exceeds the file size limit.

     Example:

     cd /d installation-folder\tools

     jpcspm stop -key all

  2. Check the PFM status.

     Confirm that the PFM services have stopped.

     Example:

     installation-folder\tools\jpctool service list -id "*"

  3. Initialize the Store database.

     Delete the PFM service Store database files.

     If the Store database installation directory is specified in jpcsto.ini, delete the files under the specified directory.

     Example: For the Master Store service

     cd /d installation-folder\mgr\store

     del *.DB

     del *.IDX

• When the data model of PFM - Manager, PFM - RM or PFM - Agent is updated, the disk space requirement for the Store database changes. Based on the new data model, reconfirm the collection items, collection frequency, and data retention conditions of the Store database.

• When you upgrade from version 09-50 or earlier of PFM - Manager or PFM - Base, the message text of the following message changes. If you use log trapping or other features that depend on the contents of the common message log or command output, change the settings for these features accordingly.

  • When you upgrade from versions of PFM - Manager or PFM - Base between 09-00 and 09-50, the following message changes:

    - KAVE05015-E

    <Before>

    A service necessary for this operation is not running.

    <After>

    It was not possible to communicate with the service necessary for this operation.

  • When you upgrade from version 08-50 or earlier of PFM - Manager or PFM - Base, the following message changes:

    - KAVE00181-W

    <Before>

    Correlator was not able to acquire alarm status information from Agent Collector. (service=service-ID)

    <After>

    Correlator was not able to acquire alarm status information from Collector. (service=service-ID)

    - KAVE05015-E

    <Before>

    A service necessary for this operation is not running.

    <After>

    It was not possible to communicate with the service necessary for this operation.

    - KAVE05019-E

    <Before>

    The specified sub-command is valid for the Master Store and Agent Store services only.

    <After>

    The specified sub-command is valid for the Store services only.

    - KAVE05237-E

    <Before>

    The service did not return the response to the request of the command-name command in time. (service=service-name, lhost=logical-host-name, inst=instance-name, rc=maintenance-code)

    <After>

    The service did not return the response to the request of the command in time (service=service-name, lhost=logical-host-name, inst=instance-name, rc=maintenanc-code)

• When data models are upgraded as part of an upgrade installation of PFM - Manager, PFM - RM or Agent, data that has already been imported is not subjected to data model conversion. Either execute the jpctool db import command with the -clear option specified to delete the imported data, or use the jpctool db dmconvert command after upgrading PFM - Manager, PFM - RM or PFM - Agent to convert the data in the import directory. If the data in the import directory is unconverted, the message KAVE00229-E is output at startup of the RM Store service or the Agent Store service, and the service fails to start.

  Note:

  Free space equivalent to twice the size of the data being converted must be temporarily available in the directory you specify in the jpctool db dmconvert -d command. Calculate the free space with reference to the size of the database specified in the -d option. For example, if the database is 100 MB in size, make sure that at least 200 MB of disk space is available before executing the command.

• When you perform an overwrite installation of PFM - Manager, the following three messages might be output to the common message log in succession during the installation process. This does not affect the operation of the system and can be safely ignored.

  KAVE05952-I The rebuilding of agent registration information for the Manager will now start.
  KAVE05051-E The file does not exist.
  KAVE05953-I The rebuilding of agent registration information for the Manager has ended.

• Because the Windows Event Viewer sometimes references files associated with Performance Management, make sure that the Event Viewer is stopped before you start installing PFM - Manager. If the Performance Management administrator console is running, close it before installation. If the command prompt is open and the current directory points to the Performance Management installation folder or one of its subfolders, navigate to a location outside the installation folder hierarchy. Also, close any open files associated with Performance Management.

(d) Notes on installation of PFM - Manager and PFM - Base

The following gives cautionary notes on installing PFM - Manager and PFM - Base:

• When you install PFM - Manager and PFM - Base, first stop all of Performance Management programs and services. Execute the jpcspm stop command to stop Performance Management services. If you want to set up a logical host, stop all Performance Management services on the logical host.

• When you install PFM - Manager and PFM - Base, make sure that the destination path name does not include any of the following characters:

  & ( ) = ^ ; , " | * < > / ? $ % ' ! + { } @ [ ]

  If any of these single-byte symbols is used, the installation of other Performance Management products might fail. However, PFM - Manager and PFM - Base can be installed in the default installation directory:

  system-drive:\Program Files(x86)\Hitachi\

• Do not install PFM - Manager and PFM - Base in the root directory of a drive.

• Do not specify the following folder as the installation directory:

  system-drive:\Program Files\Hitachi\

  system-drive:\Windows\System32\

• If you want to upgrade Microsoft(R) Windows Server(R) 2008 R2 or earlier to Windows Server 2012 or later, you must uninstall all of the Performance Management products before performing the upgrade.

• Because Windows Event Viewer might reference Performance Management files, exit Event Viewer before installing Performance Management programs.

• You cannot install PFM - Manager in a native IPv6 environment.

• If you use the Hitachi Integrated Installer CD-ROM, see the manual of the Hitachi Integrated Installer CD-ROM for how to use the integrated installer.

(e) Notes on PFM - Web Console installation

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

• When installing PFM - Web Console, first stop the programs and services for PFM - Web Console. Use the jpcwstop command to stop the services for PFM - Web Console.

• You can specify an installation folder name that has 33 or fewer characters in the installation destination for PFM - Web Console. You can use the following characters for the installation path:

  • Single-byte alphanumeric characters

  • Single-byte spaces and single-byte symbols - . _ ~

  If you attempt to install PFM - Web Console in a folder whose name contains characters other than the above, installation will fail except when the following default installation folder is used on a Windows OS:

  system-drive:\Program Files (x86)\Hitachi\

• If installation fails due to insufficient disk space or other reason, check the system status, and perform installation again. If the reason for failure is unknown, collect the installation logs (%TEMP%\pfmwebconinst.log), and contact the system administrator.

• When PFM - Web Console is already installed, overwrite installation cannot be performed for older versions of PFM - Web Console. When an older version of PFM - Web Console is installed, overwrite installation is cancelled, but when PFM - Manager is subsequently uninstalled, information about PFM - Web Console may still be displayed in the Add/Remove Programs dialog box.

  In this case, reinstall the installed version of PFM - Web Console, and then perform uninstallation.

• 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.

• If the port number set to install PFM - Web Console is already in use by another program, the installation ends without PFM - Web Console being setup. In this case, modify the port number setting to be used by PFM - Web Console and then execute the jpcwsvsetup command to finish setting up the port number. For details about how to set the port number for PFM - Web Console, see 4.1.1(4)(b) Port number settings. For details about the jpcwsvsetup command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

• If you want to upgrade Microsoft(R) Windows Server(R) 2008 R2 or earlier to Windows Server 2012 or later, you must uninstall all of the Performance Management products before performing the upgrade.

• When you upgrade PFM - Web Console to a newer revision or version, the PFM-WebService startup is set to Auto. Set the startup type to Disabled or Manual after upgrading, as necessary.

• If you install by overwriting or uninstall PFM - Web Console, the system log message below might be output. Ignore it. Even if this message is output, the overwrite installation or uninstallation succeeds and there is no problem with operation.

  KFCT73435-E <omitted>: CPRFD has not started. ID=PFMWebCon.

• When you make changes (such as adding new-type agents) to the Performance Management system configuration, always restart the PFM - Web Console service after executing the jpcagtsetup and jpcwagtsetup commands. If you omit the setup, the following problems might occur:

  • If an alarm, report, or added agent is accessed, a KAVJS4007-E error occurs. The following message is an example of the maintenance information that appears:

    The specified product not found, <Product-ID><Datamodel-Version>.

  • No product-specific icons are displayed.

  • No data model description is displayed.

• Do not install PFM - Web Console in any volume that was formatted by using the Resilient File System (ReFS).

• In PFM - Web Console, it is assumed that the DLL of PFM - Web Console and the OS standard DLL are used for operation. In an environment where any other product injects DLL (DLL injection) in a PFM - Web Console process, it might affect the operation of PFM - Web Console. The behavior might become unstable or it might be impossible to start the system.

  To confirm that the cause is not another product, we might ask the customer to reproduce the situation in an environment where no other product is installed as a part of the survey of the problem in such an environment. If it cannot be confirmed that the cause is not another product, we might not be able to provide normal support service.

(f) Notes on disk replication installation

• PFM - Manager does not support the disk replication installation.

• PFM - Web Console does not support disk replication installation of JP1/ServerConductor/Deployment Manager or image-file-based replication function provided by virtualization platforms. Uninstall PFM - Web Console before performing a disk replication installation, and then re-install PFM - Web Console after disk replication installation is complete.

  For details about operations related to disk replication installation, see the applicable manual of JP1/ServerConductor/Deployment Manager. For details about the replication function of a virtualization platform, see the documentation for the virtualization software

• PFM - Base is a Hitachi Program Product supporting the disk replication installation provided by JP1/ServerConductor/Deployment Manager, and the replication function through the image filing function provided by the virtual platform. Note, however, that replication installation cannot replicate the following information and definitions because the installation is the same as constructing an environment on different hosts.

  • Information on associating a monitoring agent with an alarm table

  • Configuring the instance environment of PFM - Agent and PFM - RM, and setting the monitoring target

  • Performance data

  In PFM - Agent for SR, the following environments, information, and definitions cannot be replicated:

  • Environment of JP1/PFM - Agent for SR earlier than 10-00

  • IE scenario files

  • Web transaction files

  • User defined commands

  • Definitions of all tasks in the measurement condition registration file (esptask.xml)

  • Command registration files (espcommand.xml)

  • Certificates

  • Passwords registered by using the esppasswd command (password file)

  To replicate a disk:

  Execute steps 1 and 2 from PFM - Web Console.

• Perform steps 3 and later on the PFM - Base, PFM - Agent, and PFM - RM machines to be replicated.

  1. Delete the association between the monitoring agent and the alarm table.

     For details on how to delete the association between the monitoring agent and the alarm table, see the chapters that describe changing the association between an alarm table and a monitoring agent in the manual JP1/Performance Management User's Guide.

  2. Delete an agent from the management folder in the Agents tree.

     For details on how to delete the Agents tree from the management folder, see the chapters that describe editing the Agents tree in the manual JP1/Performance Management User's Guide.

  3. Stop the services of all Performance Management programs.

     jpcspm stop -key all

     Stop the services of Performance Management programs except PFM - Web Console. For details on how to stop Performance Management services, see the chapters that describe jpcspm stop command in the manual JP1/Performance Management Reference.

     Make sure that there is no service process of Performance Management (processes whose name begins with jpc) from the task manager for Windows, or when using the ps command for UNIX or Linux.

     If service processes of Performance Management remain, stop them forcibly. Note, however, that it is not necessary to stop the following processes:

     - jpcadmin(.exe)

     - jpcwadmin(.exe)

     - jpcwebcon(.exe)

  4. Stop the WEB recorder, IE recorder, and IE probe (if started from an icon).

     Perform this operation only if you replicate PFM - Agent for SR.

  5. Delete the monitoring target settings and the instance environment.

     For details on how to set the monitoring target and delete the instance environment, see the applicable manuals for PFM - Agent or PFM - RM.

     Execute this operation only if you replicate multi-instance agents.

  6. Specify settings so that the alias name to be set as the monitored host name of Performance Management can be resolved.

     Configure the environment so that the alias name of the replication origination host and the replication destination host to be set as the monitoring host names of Performance Management can be resolved.

  7. Set the alias name for the monitoring host name of Performance Management.

     - For Windows:

     jpcconf host hostmode -mode alias -aliasname replication-origination-machine-alias-name (such as aliasA) -d temporary-directory (such as C:\tmp\aa) -dbconvert delete

     - For UNIX:

     jpcconf host hostmode -mode alias -aliasname replication-origination-machine-alias-name (such as aliasA) -d temporary-directory (such as /tmp/aa) -dbconvert delete

     Before replication, set the alias name of the monitoring host of Performance Management. For details on how to set alias names, for Windows see 4.3.3 Specifying and changing the monitoring host name in a Performance Management system, and for UNIX see 5.3.3 Specifying and changing the monitoring host name in a Performance Management system.

     When setting an alias name, specify the -dbconvert delete option for the jpcconf host hostmode command.

     Note that the machine for which the alias name is set here can be used for multiple replication installations.

  8. Delete all task definitions in the measurement condition registration file (esptask.xml). (If necessary, back up the files in advance.)

     Perform this operation only if you replicate PFM - Agent for SR.

  9. Delete the following files. (If necessary, back up the files in advance.)

     - IE scenario files

     (XML files under installation-destination-folder\agtv\probe\iescena\)

     - Web transaction files

     (XML files under installation-destination-folder\agtv\probe\webtrans\)

     - User defined commands

     (files under installation-destination-folder\agtv\probe\user\)

     - Command registration files

     (installation-destination-folder\agtv\probe\conf\espcommand.xml)

     - Certificates

     (files under installation-destination-folder\agtv\probe\cert\)

     - Password file

     (files under installation-destination-folder\agtv\probe\passwd\)

     Perform this operation only if you replicate PFM - Agent for SR.

  10. Perform replication installation.

      For details on how to specify settings for replication installation, and notes, see the sections below in the applicable manuals for JP1/ServerConductor/Deployment Manager. For details on the replication function of the virtualization platform, see the manuals on virtualization software.

  11. Resetting monitoring host names of replication destination machines.

      - For Windows:

      jpcconf host hostmode -newhost replication-destination-machine-alias-name (such as aliasA) -d temporary-directory (such as C:\tmp\aa)

      - For UNIX:

      jpcconf host hostmode -newhost replication-destination-machine-alias-name (such as aliasA) -d temporary-directory (such as /tmp/aa)

      After replication, specify settings again by using an alias name, such as jpcconf host hostname -newhost, for the monitoring host corresponding to the replication destinations.

      For how to reset monitoring host names, for Windows see 4.3.3 Specifying and changing the monitoring host name in a Performance Management system, and for UNIX see 5.3.3 Specifying and changing the monitoring host name in a Performance Management system.

  12. Delete the monitoring target settings and the instance environment of replication destination machines as necessary.

      For details on how to set the monitoring target and delete the instance environment, see the applicable manuals for PFM - Agent or PFM - RM.

      Execute this operation only if you replicate multi-instance agents.

(g) 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 JP1/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 JP1/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.

• When you first connect PFM - Agent or PFM - RM to PFM - Manager after installation or after performing an upgrade installation that involves changes to data models, PFM - Manager registers the associated agent information. This places a greater than usual load on PFM - Manager.

  For this reason, do not simultaneously start a large number of PFM - Agent or PFM - RM instances that will be connecting to PFM - Manager for the first time.

  We recommend that no more than 100 instances establish first-time connections to PFM - Manager at any one time.