Hitachi

JP1 Version 12 JP1/Performance Management Planning and Configuration Guide


5.1.5 PFM - Web Console setup procedure

[Figure] indicates setup items required according to each environment and optional setup items used to change default settings.

Tip

The initialization file (config.xml) is used to set up the operating environment for PFM - Web Console.

Organization of this subsection

(1) Setting the LANG environment variable

Set the LANG environment variable.

Before assigning a value to the LANG environment variable, make sure that the language environment you specify is installed and configured correctly. If the language is not installed and configured correctly, you might encounter issues such as characters appearing garbled or definition data being overwritten erroneously.

Note:

The value of the LANG environment variable set at the time of service startup or command execution determines the language of the operation status log. Therefore, the log might contain a mixture of text with different language codes.

The table below lists values that can be set to the LANG environment variable in PFM - Web Console. If a language not listed in the table (German, French, Spanish, Korean, and Russian) is set, C is used for the value of the LANG environment variable during operation.

Table 5‒8: LANG environment variables values that are available in Performance Management (In AIX)

Language

Encoding

LANG environment variable value

Japanese

EUC

  • ja_JP

  • ja_JP.IBM-eucJP

Shift_JIS (SJIS)

  • Ja_JP

  • Ja_JP.IBM-932

UTF-8

  • JA_JP

  • JA_JP.UTF-8

English

ASCII

  • C

Chinese (Simplified Chinese)

GB18030

  • Zh_CN

  • Zh_CN.GB18030

UTF-8

  • ZH_CN

  • ZH_CN.UTF-8

Table 5‒9: LANG environment variable values that are available in Performance Management (In Linux)

Language

Encoding

LANG environment variable value

Japanese

Shift_JIS (SJIS)

  • ja_JP.SJIS#

  • ja_JP.sjis#

UTF-8

  • ja_JP.UTF-8

  • ja_JP.utf8

English

ASCII

  • C

Chinese (Simplified Chinese)

GB18030

  • zh_CN.gb18030

UTF-8

  • zh_CN.UTF-8

  • zh_CN.utf8

#: Available only for SUSE Linux

If the language setting of the system locale of the server differs from that of the usrconf.cfg file, PFM - Web Console might not operate properly. Before setting up PFM - Web Console, check the system locale and the usrconf.cfg file, and if the language setting differs from each other, change the setting in the usrconf.cfg file.

If you change the system locale after installing PFM - Web Console, be sure to review the settings for the usrconf.cfg file.

For details about the option definition file (usrconf.cfg), see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(2) Registering PFM - Agent or PFM - RM[Figure]

You must register PFM - Agent or PFM - RM in PFM - Web Console in order to perform integrated management of PFM - Agent or PFM - RM by using PFM - Manager and PFM - Web Console.

If PFM - Agent or PFM - RM is already registered in PFM - Web Console, you do not have to follow the procedure described below. If PFM - Agent or PFM - RM is not registered yet, manually register PFM - Agent or PFM - RM according to the procedure.

You can determine whether manual registration of PFM - Agent or PFM - RM is necessary by referring to the conditions described below.

When the following condition applies, manually register PFM - Agent or PFM - RM in PFM - Web Console:

If, however, the Release Notes for PFM - Agent or PFM - RM state that it is necessary to execute the setup command, execute the setup command.

Figure 5‒4: Process flow for registering PFM - Agent or PFM - RM

[Figure]

Notes:
  • You do not need to register PFM - Agent or PFM - RM when you add the same version of PFM - Agent or PFM - RM with the same product ID to a Performance Management system in which the PFM - Agent or PFM - RM information has been already registered.

  • Set up the latest version of PFM - Agent or PFM - RM if you install a different version of PFM - Agent or PFM - RM with the same product ID on a different host.

(a) Copying the PFM - Agent or PFM - RM setup file

Copy the setup file on a host that has PFM - Agent or PFM - RM onto a host that has PFM - Web Console installed.

To copy the PFM - Agent setup file:

  1. Stop PFM - Web Console if it is running.

  2. Copy the setup file of PFM - Agent or PFM - RM in binary mode.

    The following table gives the locations where the files are stored, and the location where the files are to be copied.

    Table 5‒10: Setup files to be copied

    Copy from

    Copy to

    Host

    File

    Host

    File

    PFM - Agent, PFM - RM

    • In UNIX:

      /opt/jp1pc/setup/jpcxxxxu.Z

    PFM - Web Console

    /opt/jp1pcwebcon/setup/

    Legend:

    xxxx indicates the service key of each PFM - Agent or PFM - RM. For details about service keys, see the appropriate PFM - Agent or PFM - RM documentation.

(b) Executing the setup command on the PFM - Web Console host

Execute the following command on PFM - Web Console to set up PFM - Agent or PFM - RM.

jpcwagtsetup

You can delete the PFM - Agent or PFM - RM setup file on the PFM - Web Console host after this procedure has finished.

Note:

Even though PFM - Web Console is installed on the same host as PFM - Agent or PFM - RM, you must execute the jpcwagtsetup command.

(3) Specifying settings for the network [Figure]

The settings described in this subsection are required when adjusting the network configuration of PFM - Agent to match that used by Performance Management.

You can set the following item for network settings:

(4) Specifying settings in the initialization file (config.xml) [Figure]

The settings required for operating PFM - Web Console are defined in the initialization file (config.xml). The settings described in this subsection are required when you want to change the initial settings in the file.

The config.xml file contains settings related to the log files for PFM - Web Console and the amount of data that can be displayed in the console window. For details, see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(5) Setting the connection-target PFM - Manager for PFM - Web Console[Figure]

To set the connection-target PFM - Manager, edit the initialization file (config.xml).

For details, see the section that describes the initialization file (config.xml) in the appendix of the manual JP1/Performance Management Reference.

(6) Creating an authentication key file for PFM - Web Console[Figure]

If you want to execute the PFM - Web Console commands, you must first execute the jpcmkkey command. For details about the jpcmkkey command, see the chapter that describes definition files in the manual JP1/Performance Management Reference.

(7) Setting the starting user and group for PFM - Web Console[Figure]

By default, the PFM - Web Console services are started with nobody/root permissions. If you fail to start PFM - Web Console with this user and group, the message KAVJT0003-E is output.

In this case, change the User and Group settings in the /opt/jp1pcwebcon/CPSB/httpsd/conf/httpsd.conf file to a system user (other than root) and the group to which that user belongs, respectively. In the following example, the words in italics indicate the points to be changed:

User nobody
Group root

(8) Setting up encrypted communication between a web browser and the monitoring console server [Figure]

To use encrypted communication between a web browser and the monitoring console server, you must set it up for PFM - Web Console and for the web browser. For details, see 4.3.15 Changing the settings for encrypted communication between a web browser and the monitoring console server.