5.1.4 PFM - Manager setup procedure

(1) Setting the LANG environment variable

Set the LANG environment variable.

Before setting the LANG environment variable, verify that the language environment to set is properly installed and configured. If the language is not installed and configured properly, text might be garbled and definition data might be overwritten erroneously. For more information about operating in a mixed environment in which multiple languages are used, see 3.10.4 Notes on environments in which multiple languages coexist.

Note1:

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

Note 2:

If the LC_ALL environment variable has been specified and its value differs from the value of the LANG environment variable, release the LC_ALL environment variable or change its value to the value of the LANG environment variable when you start the services of Performance Management and when you execute commands.

Changing the environment variable is required only on the shell that is used to perform the corresponding operations. There is no need to change the environment variable throughout the entire system. You use the following command to release the LC_ALL environment variable:

unset LC_ALL

The table below lists the values that can be set to the LANG environment variable in Performance Management. 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.

To Page Top

(2) Registering PFM - Agent or PFM - RM

You must register PFM - Agent or PFM - RM in PFM - Manager 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 - Manager, 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 all of the following conditions apply, manually register PFM - Agent or PFM - RM in PFM - Manager:

• The PFM - Agent or PFM - RM to be installed is of a product version that is not specified in the Release Notes for PFM - Manager.

• PFM - Agent or PFM - RM is installed on a host other than PFM - Manager.

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.

Note

The information on the automatically registered PFM - Agent or PFM - RM is displayed in PFM - Web Console at the following timing:

If the version of PFM - Web Console is 09-00 or later:

The information is displayed when you log into PFM - Web Console again after starting the registered PFM - Agent or PFM - RM.

If the version of PFM - Web Console is 08-11 or earlier:

The information is displayed when you restart PFM - Web Console after starting the registered PFM - Agent or PFM - RM.

If you want to register PFM - Agent or PFM - RM before starting the console, execute the jpcconf agent setup command with the -register option specified. For details about the jpcconf agent setup command, see the chapters that describe commands in the manual JP1/Performance Management Reference.

Note

• Register PFM - Agent or PFM - RM before setting the instance environment of PFM - Agent or PFM - RM.

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

• If you install a different version of PFM - Agent or PFM - RM with the same product ID on a different host, first set up the older version of PFM - Agent or PFM - RM, and then set up the newer version of PFM - Agent or PFM - RM.

• If you install PFM - Agent or PFM - RM on the same host that has PFM - Manager installed, the jpcconf agent setup command is executed automatically. In PFM - Agent or PFM - RM, the execution results are logged as KAVE05908-I New agent setup (pfm-agent-service-key) ended successfully. (version=version) to the common message log. Check the results. If the command has not been executed correctly, execute the command again. For details about how to execute the commands, see the chapters that describe commands in the JP1/Performance Management Reference.

Supplemental information:

Note the information that follows about performing manual registration (jpcconf agent setup -key agtX (with the -register option omitted)) on the PFM - Manager host.

Executing jpcconf agent setup -key agtX (with the -register option omitted) when PFM - Manager is a physical environment:

The registered PFM - Agent or PFM - RM information is displayed on PFM - Web Console at the following time:

• PFM - Web Console version 09-00 or later

  The next time the user log on to PFM - Web Console

• PFM - Web Console version 08-11 or earlier

  When PFM - Web Console is restarted

Executing jpcconf agent setup -key agtX (with the -register option omitted) on the executing host and the standby host when PFM - Manager is a logical host:

The registered PFM - Agent or PFM - RM information is displayed on PFM - Web Console at the following time:

• PFM - Web Console version 09-00 or later

  After the registered PFM - Agent or PFM - RM has started or the next time the user executes jpcconf agent setup -key agtX -register on the executing host and the standby host to which the shared disk is connected and logs on to PFM - Web Console

• PFM - Web Console version 08-11 or earlier

  After the registered PFM - Agent or PFM - RM has started or the next time the user executes jpcconf agent setup -key agtX -register on the executing host and the standby host to which the shared disk is connected and restarts PFM - Web Console

jpcconf agent setup -key xxxx

jpcconf agent setup -key Oracle

To Page Top

(3) Specifying settings for the network

Settings described in this subsection are required if you change settings according to the network configuration on which Performance Management is used.

You can set the following four items for network settings:

• Setting IPv6 communication

  This setting is required if you use IPv6 communication in Performance Management. To use IPv6 communication, execute the jpcconf ipv6 enable command on the PFM - Agent, PFM - RM, and PFM - Manager that will be using IPv6 communication.

  In a cluster system, this setting must be specified in both the executing system and the standby system.

  Note that only IPv4 communication is supported between PFM - Manager and PFM - Web Console.

  For details, see 5.3.1(1)(a) Setting IPv6 communication.

• Setting IP addresses

  Set this item when Performance Management is used in a network with multiple LANs connected. To set multiple IP addresses, define the host name and IP address in the jpchosts file. Confirm that the settings in jpchosts files are the same throughout the entire Performance Management system.

  For details, see 5.3.1(1)(b) Setting IP addresses.

• Setting port numbers

  You can set the port numbers used by Performance Management. Use the same port numbers and service names for the entire Performance Management system to avoid confusion during operation.

  For procedures on setting port numbers, see 5.3.1(1)(c) Setting port numbers.

  Note

  By setting fixed ports for the PFM - Manager's Master Manager service and Correlator service, you can start up Performance Management more quickly in large environments.

• Setting the host name or IP address used for communication with PFM - Web Console and JP1/SLM

  Define the host name or IP address of PFM - Manager in the jpcvsvr.ini file on the PFM - Manager host in the following cases:

  • IP address translation (NAT) is performed between the PFM - Manager host and the PFM - Web Console host.

  • Multiple IP addresses are used between the PFM - Manager host and the PFM - Web Console host.

  • JP1/SLM is linked and IP address translation (NAT) is performed between the PFM - Manager host and the JP1/SLM host.

  • JP1/SLM is linked and multiple IP addresses are used between the PFM - Manager host and the JP1/SLM host.

  For details, see 5.3.1(1)(d) Setting the host name or IP address used for communication with PFM - Web Console and JP1/SLM.

To Page Top

(4) Changing the log file size

The operating status of Performance Management is output to a Performance Management-specific log file. This log file is called the common message log. This setting is required when you wish to change this file size.

For details, see 5.4.1 Setting the size of the log file for the common message log.

To Page Top

(5) Specifying settings for the authentication mode

These settings are required when you wish to change the authentication mode of Performance Management from PFM authentication mode to JP1 authentication mode.

For details, see the chapter that describes management of user accounts and business groups in the JP1/Performance Management User's Guide.

To Page Top

(6) Setting the access control function based on business groups

These settings are required if you want to use business groups to manage the users of Performance Management. Specify in the start information file (jpccomm.ini) whether the access control function based on business groups is to be used.

For details, see the chapter that describes user accounts and business groups in the JP1/Performance Management User's Guide.

To Page Top

(7) Changing the storage locations of event data

The settings below are required when you wish to change the storage destination, backup destination, or export destination of the event data managed by PFM - Manager.

By default, event data is stored in the following locations:

• Data storage directory: /opt/jp1pc/mgr/store/

• Backup directory: /opt/jp1pc/mgr/store/backup/

• Export directory: /opt/jp1pc/mgr/store/dump/

Note:

For the default directories when running Performance Management on a logical host, read /opt/jp1pc/ as environment-directory\jp1pc\.

For details about how to change the storage location, see 5.4.2 Changing the storage location of event data.

To Page Top

(8) Specifying settings for action log output

These settings are required when you wish to output action log data when an alarm is issued. Action log data is output in cooperation with the alarm function, when an aspect of the system such as the system load exceeds a threshold. For details, see Appendix H. Outputting Action Log Data.

To Page Top

(9) Configuring the health check function

These settings are required when you wish to check the operation status of monitoring agents and their hosts. For details about how to specify this setting, see the chapter that describes detecting problems in the JP1/Performance Management User's Guide.

To Page Top

(10) Configuring the PFM service automatic restart function

This setting is required if you want PFM services to automatically restart if they terminate abnormally. For details about how to specify this setting, see the chapter that describes detecting problems in Performance Management in the JP1/Performance Management User's Guide.

To Page Top

(11) Configuring the product name display function

These settings are required if you want to enable the product name display function when you upgrade from version 08-11 or earlier, or when you perform a new installation. For details about the product name display function, see 3.1.2 Displaying and specifying services (the product name display function). For details about how to specify these settings, see 5.4.9 Configuring the product name display function.

To Page Top

(12) Configuring the auto alarm bind function

The setting described here is necessary when you want to change the default setting (enabled or disabled) of the auto alarm bind function. When you install or upgrade to Performance Management version 11-50 or later, the auto alarm bind function is enabled by default. For details about the auto alarm bind function, see the section describing auto alarm bind in the JP1/Performance Management User's Guide.

You can edit the default setting as follows:

Note

If you are using a multiple monitor configuration, edit this setting on both the primary and secondary hosts.

1. Stop Performance Management programs and services.

   If there are any Performance Management programs and services running, stop all of them by using the jpcspm stop command. If you are using a cluster configuration, first stop the cluster software.

2. Use a text editor or a similar tool to edit the jpccomm.ini file that defines the operating environment for the PFM - Manager hosts (physical and logical hosts).

   Under the [Common Section] section of the jpccomm.ini file, edit and then save the setting as follows:

   To enable the auto alarm bind function:

   Auto Alarm Bind Mode=1

   To disable the auto alarm bind function:

   Auto Alarm Bind Mode=0

   After editing the above setting, save and then close the jpccomm.ini file.

3. Start Performance Management programs and services.

   Start Performance Management programs and services by using the jpcspm start command. If you are using a cluster configuration, first start the cluster software.

To Page Top