3.2.4 Setup procedure for the UNIX edition
This subsection describes how to set up PFM - RM for Platform.
indicates the following setup items:
-
Setup item required depending on the environment in use
-
Setup item for changing a default setting
- Organization of this subsection
-
(1) Setting the LANG environment variable
You must set the LANG environment variable.
The table below shows the LANG environment variable values supported by PFM - RM for Platform. Before you set a LANG environment variable value, check that the applicable language environment has been installed and configured correctly. Invalid installation and configuration of the language environment might result in encoding errors and illegal rewriting of definition data.
No. |
Language |
LANG environment variable value |
|
---|---|---|---|
1 |
Japanese |
UTF-8 code |
|
2 |
English (no Japanese) |
C |
- Note;
-
If you specify a value not listed in this table, PFM - RM for Platform runs in C.
- Notes regarding setting of the LANG environment variable
-
The language for the common message log is determined by the LANG environment variable that is specified during service startup or command execution. Therefore, character strings in multiple language codes, such as both Japanese and English, might be present.
(2) Registering PFM - RM for Platform
To achieve central management of PFM - RM for Platform in the Performance Management system, you must register PFM - RM for Platform into PFM - Manager and PFM - Web Console.
You must register PFM - RM for Platform at the following times:
-
Whenever you add a new PFM - RM for Platform in the Performance Management system.
Note: If a PFM - RM for Platform has already been registered and you are adding a new PFM - RM for Platform of the same version, there is no need to register the new PFM - RM for Platform.
-
When you update the Data model version for the registered PFM - RM for Platform.
The following figure shows the procedure for registering PFM - RM for Platform.
|
- Notes about registering PFM - RM for Platform
-
-
Register PFM - RM for Platform before you set up an instance environment.
-
If you install different versions of PFM - RM for Platform on separate hosts, set up old versions before you set up new versions.
-
If you install PFM - RM for Platform on the same host as where PFM - Manager is installed, the jpcconf agent setup command executes automatically.
-
When PFM - RM for Platform is registered, folders named RM Platform are created on the Reports and Alarms pages of PFM - Web Console. If you have already created a folder or file named RM Platform on the Reports page, you must rename it before starting the registration procedure.
-
The following subsections describe how to register PFM - RM for Platform.
(a) Copying the setup files for PFM - RM for Platform
Copy the setup files from the PFM - RM host to the hosts where PFM - Manager and PFM - Web Console are installed.
To copy the setup files:
-
Stop PFM - Web Console.
If PFM - Web Console is running, stop it.
-
Copy the setup files in binary mode.
Copy the files from the PFM - RM host to the PFM - Manager and PFM - Web Console hosts.
The following table lists the source file storage locations and the copy destination locations.
Table 3‒33: Setup files to be copied (for UNIX)) No.
Source (setup files for PFM - RM for Platform)
Target
Program name
OS
Target folder
1
/opt/jp1pc/setup/jpcagt7w.EXE
PFM - Manager
Windows
PFM-Manager-installation-folder\setup
2
/opt/jp1pc/setup/jpcagt7u.Z
UNIX
/opt/jp1pc/setup/
3
/opt/jp1pc/setup/jpcagt7w.EXE
PFM - Web Console
Windows
PFM-Web-Console-installation-folder\setup
4
/opt/jp1pc/setup/jpcagt7u.Z
UNIX
/opt/jp1pcwebcon/setup/
(b) Executing the setup command at the PFM - Manager host
At the PFM - Manager host, execute the setup command for PFM - RM for Platform.
Execute the following command:
jpcconf agent setup -key RMPlatform
This example shows execution in the interactive mode, but you can also execute the jpcconf agent setup command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
- Notes about executing the command
-
Before you execute the command, stop all Performance Management programs and services at the local host. An error might occur if the jpcconf agent setup command is executed before all Performance Management programs and services have stopped completely. If an error has occurred, make sure that all Performance Management programs and services have stopped completely, and then re-execute the jpcconf agent setup command.
After you have executed the setup command at the PFM - Manager host, you might delete the setup files for PFM - RM for Platform that were copied to the PFM - Manager.
(c) Executing the setup command at the PFM - Web Console host
At the PFM - Web Console host, execute the setup command for PFM - RM for Platform.
Execute the following command:
jpcwagtsetup
After you have executed the setup command at the PFM - Web Console host, you might delete the setup files for PFM - RM for Platform that were copied to the PFM - Web Console.
(3) Setting up an instance environment
Set up an instance environment for PFM - RM for Platform at the PFM - RM host. To set multiple instance environments, repeat this procedure. In PFM - RM for Platform, you can define a maximum of 50 monitoring targets in a single instance environment.
- Notes about setting instance environments
-
Before you set instance environments, make sure that the procedure described in 3.2.1(5) Environment settings required for collecting performance data (for UNIX) has been completed and the correct environment has been set up.
The table below lists and describes the instance environment setting items and values. Check this information before you start operations.
Use the jpcconf inst setup command to set up an instance environment. For details about how to execute the jpcconf inst setup command, see (a) Execution in the interactive mode and (b) Execution in the non-interactive mode.
No. |
Item name#1 |
Description |
Setting |
Default |
---|---|---|---|---|
1 |
Interval |
Specifies a collection interval for the collection process. |
Specify a value in the range from 60 to 3,600 (seconds). |
300 |
2 |
Std_Category#2 |
Specifies whether the collection process is to collect basic information (PI and PI_CPU records). |
Specify one of the following values:
|
Y |
3 |
Disk_Category#2 |
Specifies whether the collection process is to collect disk information (PI_PDSK and PI_LDSK records). |
Specify one of the following values:
|
Y |
4 |
Network_Category#2 |
Specifies whether the collection process is to collect network information (PI_NET record). |
Specify one of the following values:
|
Y |
5 |
Ps_Category#2 |
Specifies whether the collection process is to collect process information (PD_APS, PD_ASVC, PD_APP2, PD_APPC, and PD_APPD records). |
Specify one of the following values:
|
Y |
6 |
Log_Size |
Specifies the maximum size of one agent log file.#3 |
Specify a value in the range from 1 to 32 (megabytes). |
3 |
- #1
-
When the jpcconf inst setup command is executed in the non-interactive mode, this item name is used as a product-specific label in the definition file. For details about commands in the non-interactive mode, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
- #2
-
The settings for Std_Category, Disk_Category, Network_Category, and Ps_Category are given higher priority than the collection settings for the individual records.
For example, if you set Std_Category to N (do not collect), a PI record is handled as follows:
The PI record information is not recorded in the Store database.
If an attempt is made to display a real-time report based on PI records, the KAVJS5001-I error message is displayed.
If an alarm is bound to a PI record, that alarm will not function.
- #3
-
The following formula can be used to estimate the agent log file size:
Agent log (megabytes) = ((a
24
3600)
b
4)
(4
1024)
Legend:
a: Number of days agent logs are stored
b: Interval value of the instance
For agent logs, the maximum number of files collected for each instance is (8 + the number of monitoring targets
4). If there is not enough free space on the hard disk, agent logs result in an output error. For details about agent logs, see 9.3 Log information to be collected for troubleshooting.
(a) Execution in the interactive mode
-
Execute the jpcconf inst setup command.
The command sets an instance environment with an instance name of inst1:
jpcconf inst setup -key RMPlatform -inst inst1
-
Set up an instance environment for PFM - RM for Platform.
Enter each instance environment setting for PFM - RM for Platform according to the command's instructions. For details about each instance environment setting, see Table 3-34 Instance environment settings for PFM - RM for Platform (for UNIX). After you enter each setting, press the Enter key. To use a displayed default value, press the Enter key.
The following example sets all instance environment settings to the default values:
/opt/jp1pc/tools>jpcconf inst setup -key RMPlatform -inst inst1 Interval [300] :<Enter> Std_Category [Y] :<Enter> Disk_Category [Y] :<Enter> Network_Category [Y] :<Enter> Ps_Category [Y] :<Enter> Log_Size (MB) [3] :<Enter> KAVE05080-I The instance environment is now being created. (servicekey#=RMPlatform, inst=inst1) KAVE05081-I The instance environment has been created. (servicekey#=RMPlatform, inst=inst1)
- #
-
If PFM - Manager's product name display function is disabled, agt7 is displayed for servicekey.
(b) Execution in the non-interactive mode
-
Execute the jpcconf inst setup command to create a definition file template.
Execute the command as follows:
jpcconf inst setup -key RMPlatform -noquery -template definition-file-name
Sections and labels that correspond to the instance environment settings are output to a definition file. Note that the value for the label of the Instance Definitions section is left blank.
-
Edit the definition file template created in step 1.
Edit the template setting values according to the instance environment.
For details about the product-specific labels to be specified in the definition file, see Table 3-34 Instance environment settings for PFM - RM for Platform (for UNIX).
Shown below is an example of coding a definition file. Specify values for the labels in the Instance Definitions section according to the instance environment.
[Common Definitions] Definition File Version=0001 [Product Information] Product ID=7 [Instance Definitions] Interval=300 Std_Category=Y Disk_Category=Y Network_Category=Y Ps_Category=Y Log_Size=3
-
Execute the jpcconf inst setup command to set up the instance environment for PFM - RM for Platform.
Shown below is an example of executing a command for setting up an instance environment where inst1 is the instance name. For the -input option, specify the definition file edited in step 2.
jpcconf inst setup -key RMPlatform -inst inst1 -noquery -input definition-file-name
- Note;
-
If the definition file contains confidential information such as passwords, save the definition file in a secure location, and delete it after you have used it. If you want to transfer the definition file between hosts, we recommend that you use a secure file transfer protocol, such as Secure File Transfer Protocol (SFTP), which is FTP over an SSH tunnel.
When all of the settings have been completed, an instance environment can be built. The following table shows the directory structure of an instance environment.
No. |
Storage directory |
File name |
Description |
---|---|---|---|
1 |
/opt#1/jp1pc/agt7/agent/instance-name |
jpcagt.ini |
Service startup initialization file of Remote Monitor Collector |
2 |
jpcagt.ini.lck |
Lock file for the service startup initialization file of Remote Monitor Collector (for each instance) |
|
3 |
jpcagt.ini.model#2 |
Sample of a service startup initialization file of Remote Monitor Collector |
|
4 |
status.dat |
Intermediate file for internal processing |
|
5 |
tstatuses.dat |
Virtual Agent status information#3 |
|
6 |
targetlist.ini |
List of monitoring targets |
|
7 |
grouplist.ini |
List of groups |
|
8 |
GARULES.DAT |
Grouping rule description file |
|
9 |
targets |
Storage folder for remote agent |
|
10 |
groups |
Storage folder for group agent |
|
11 |
log |
Storage folder for log files |
|
12 |
/opt#1/jp1pc/agt7/store/instance-name |
*.DB |
Performance data file |
13 |
*.IDX |
Index files for performance data files |
|
14 |
*.LCK |
Lock files for performance data files |
|
15 |
jpcsto.ini |
Service startup initialization file of Remote Monitor Store |
|
16 |
jpcsto.ini.model#2 |
Model file for the service startup initialization file of Remote Monitor Store |
|
17 |
status.dat |
Intermediate file for internal processing |
|
18 |
*.DAT |
Definition file for a data model |
|
19 |
dump |
Export folder |
|
20 |
backup |
Backup folder |
|
21 |
partial |
Partial backup folder |
|
22 |
import |
Import folder |
|
23 |
log |
Storage folder for log files |
- #1
-
If you run a logical host, replace opt with environment-directory. An environment directory is a directory on the shared disk that is specified when the logical host is created.
- #2
-
Use these sample files when you want to restore the settings to their initial values from when the instance environment was configured.
- #3
-
Created when the health check function is enabled.
To change an instance environment, re-execute the jpcconf inst setup command, and then update each instance environment setting. For details about updating the instance environment settings, see 3.6.2 Updating an instance environment.
You can change some settings by using PFM - Web Console to edit properties. For details about the information that can be changed by editing properties, see E.2 List of properties of the Remote Monitor Collector service.
In an instance environment, the service IDs are as follows:
- Service IDs in an instance environment
-
-
For the Remote Monitor Collector service
7Ainstance-number instance-name[host-name]
-
For the Remote Monitor Store service
7Sinstance-number instance-name[host-name]
-
For the Group Agent service
7Ainstance-number instance-name[All@host-name]
In PFM - RM for Platform, the instance name specified in the jpcconf inst setup command is displayed.
If the host name of the PFM - RM host is host1 and inst1 is specified as the instance name, the service IDs will be as follows:
-
For the Remote Monitor Collector service
7A1inst1[host1]
-
For the Remote Monitor Store service
7S1inst1[host1]
-
For the Group Agent service
7A1inst1[All@host1]
For details about the service IDs, see the naming rules provided in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
You cannot set up an instance environment by using PFM - Web Console's facility for distributing agent-specific properties.
-
(4) Setting the monitored host
Set information about the monitored host for the instance that was set up in (3) Setting up an instance environment. You can set a maximum of 50 monitored hosts for a single instance. To set multiple monitored hosts, repeat this procedure. However, if the number of monitored hosts is large, the desired performance might not be achieved depending on the system's performance and environment. In this case, reduce the number of monitored hosts. Carefully validate the performance before starting operation.
You must specify physical hosts as monitoring targets. PFM - RM for Platform does not support monitoring of logical hosts.
- Using common account information for monitored hosts
-
If Y is set for UseCommonAccount in the setting items for the monitored host, common account information (ssh) that was created beforehand for the monitored host is used.
The following table lists the correspondence between the setting items for the monitored host and those for common account information.
Table 3‒36: Correspondence between the setting items for the monitored host and those for common account information Setting items for the monitored host
Setting items for common account information (ssh)
Description
User
User
User name
Private_Key_File
Private_Key_File
Private key file name
- Note 1:
-
Common account information can only be used in an environment where both the version of PFM - RM for Platform and the version of the prerequisite program (PFM - Manager or PFM - Base) in the same device as PFM - RM for Platform are 10-50 or later.
- Note 2:
-
Common account information must be created on the PFM - RM host beforehand.
Use the jpcconf acc setup command to create common account information. For details about the jpcconf acc setup command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
- Note 3:
-
The settings and precautions required for creating common account information (ssh) are the same as for the corresponding monitoring target setting items. See the corresponding monitoring target setting items in Table 3-37.
- Important note
-
To use common account information, you need to unify the account information settings so that you can connect to multiple monitoring targets by using a single set of account information. For this reason, there is a risk of greater negative impact if common account information is leaked. To avoid such a risk, determine whether to use common account information after considering security measures and information management.
- Notes about setting the monitored host
-
-
Before you set a monitored host, make sure that the procedure described in 3.2.1(5) Environment settings required for collecting performance data (for UNIX) has been completed and the environment has been set up.
-
Even if an invalid value is specified when setting up the monitored host, the monitored host creation command terminates normally. However, if you start record collection with any invalid settings, performance data is not collected. For details about troubleshooting when performance data is not collected, see 9.2.5(3) PFM - RM for Platform was started, but no performance data is being collected.
-
(a) Monitoring target setting items and values
The table below lists and describes the setting items and values for a monitored host. Check this information before you start operations.
Use the jpcconf target setup command to set up a monitored host.
For details about how to execute the jpcconf target setup command, see (c) Execution in the interactive mode and (d) Execution in the non-interactive mode.
For details about the jpcconf target setup command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
No. |
Item name#1 |
Description |
Setting |
Default |
---|---|---|---|---|
1 |
Target Host |
Specifies the name of the monitored host. Specify a host name that can be resolved.#2 The specified monitored host name is used during performance data collection and health checking. If JP1/IM or NNM is linked, this name is also used as the event host name. |
From 1 to 32 bytes of alphanumeric characters and the hyphen (-) are permitted. The name cannot begin with a hyphen (-). The specified value must be unique within the instance.#3 |
No monitored host name is specified.#4 |
2 |
UseCommonAccount |
Specifies whether to use common account information. |
Specify one of the following values:
|
N |
3 |
User#5 |
Specifies the user used to log on to the monitored host. PFM - RM for Platform uses this user to log on to the monitored host and collect performance data. |
From 1 to 256 bytes of characters are permitted. The tab character is not permitted. |
-- |
4 |
Private_Key_File |
Specifies the name of the private key file#6 that is used with the SSH public key method. |
From 1 to 256 bytes of characters are permitted. The tab character is not permitted. |
/opt/jp1pc/agt7/.ssh/agt7 |
5 |
Port |
Specifies the port number of the SSH server on the monitored host. |
Specify a value in the range from 1 to 65,535. |
22 |
- Legend:
-
--: No default is set.
- #1
-
When the jpcconf target setup command is executed in the non-interactive mode, this item name is used as a product-specific label in the definition file. For details about commands in the non-interactive mode, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
- #2
-
To collect performance data and perform health checking, the name must be resolvable at least by the PFM - RM host.
If the JP1/IM linkage facility is used, the name must be resolvable by the JP1/IM host. If the NNM linkage facility is used, the name must be resolvable by the PFM - Manager host and the NNM host.
- #3
-
All cannot be used because it is a reserved word for group agents.
- #4
-
If the specification is omitted, the host name of the PFM - RM host is assumed.
- #5
-
For the login shell for the user to be specified, specify bash, bsh, or ksh.
This also applies when User in common account information (ssh) is used.
- #6
-
If a connection attempt using the specified private key fails, the private key set by the SSH server (IdentityFile) is used for connection.
This also applies when Private_Key_File in common account information (ssh) is used.
(b) Monitored host setting items that are not displayed
Monitored host setting items are usually displayed by executing a command, but some are not displayed depending on the contents of other setting items or for some other reason. The table below describes conditions that prevent monitored host setting items from being displayed. It also shows the input values that are used in such cases.
Item name |
Conditions that prevent monitored host setting items from being displayed, and input values that are used |
---|---|
UseCommonAccount |
This item is not displayed in an environment where common account information cannot be used. |
User |
These items are not displayed when Y is specified for UseCommonAccount in an environment where common account information can be used. Input value: The value in the corresponding common account information is used as the input value. For details about the corresponding common account information, see Table 3-36. |
Private_Key_File |
- Note:
-
Here, an environment where common account information can be used refers to an environment where both the version of PFM - RM for Platform and the version of the prerequisite program (PFM - Manager or PFM - Base) in the same device as PFM - RM for Platform are 10-50 or later.
(c) Execution in the interactive mode
-
Execute the jpcconf target setup command.
In PFM - RM for Platform, we recommend that you specify the host name of the monitored host as the name of the monitoring target.
The following example sets the monitored host targethost1 with instance name inst1 as the monitoring target:
jpcconf target setup -key RMPlatform -inst inst1 -target targethost1
-
Set up the monitoring target for PFM - RM for Platform.
Enter setting items for the monitored host according to the instructions given by the command. For details about the setting items for the monitored host, see Table 3-37. After you input each setting item, press the Enter key to set it. To use a displayed default value, simply press the Enter key.
The following shows an example of setting up a monitoring target:
- Conditions for the PFM - RM host to be set up
-
- SSH client program: :/usr/bin/ss
- Private key: /opt/jp1pc/agt7/.ssh/agt7
- Conditions for the monitored host to be set up
-
- Host name: targethost1
- User: ssh-user
- Port number of SSH: 22
/opt/jp1pc/tools>jpcconf target setup -key RMPlatform -inst inst1 -target targethost1 Target Host [] :targethost1<Enter> UseCommonAccount#1 [N] :<Enter> User#2 :ssh-user<Enter> Private_Key_File#2 [/opt/jp1pc/agt7/.ssh/agt7]:<Enter> Port [22#3] :<Enter> KAVE05361-I The monitoring target is now being added. (servicekey#4=RMPlatform, inst=inst1, target=targethost1) KAVE05362-I The monitoring target has been added. (servicekey#4=RMPlatform, inst=inst1, target=targethost1)
- #1
-
This item is not displayed in an environment where common account information cannot be used.
- #2
-
This item is not displayed when Y is specified for UseCommonAccount.
- #3
-
If the port number used in SSH is not 22, change the value of Port to the port number used in SSH.
- #4
-
If PFM - Manager's product name display function is disabled, agt7 is displayed for servicekey.
(d) Execution in the non-interactive mode
-
Execute the jpcconf target setup command to create a definition file template.
jpcconf target setup -key RMPlatform -noquery -template definition-file-name
Sections and labels that correspond to the monitored host setting items are output to a definition file. Note that the value for the label of the Target Definitions section is left blank.
-
Edit the definition file template created in step 1.
Edit the template setting values as required for the monitored host.
For details about the product-specific labels to be specified in the definition file, see Table 3-37.
Shown below is an example of coding a definition file. Specify values for the labels in the Target Definitions section as required for the monitored host.
[Common Definitions] Definition File Version=0001 [Product Information] Product ID=7 [Target Definitions] Target Host=targethost1 UseCommonAccount#1= User#2=user1 Private_Key_File#2=/opt/jp1pc/agt7/.ssh/agt7 Port=22
- #1
-
This item is not displayed in an environment where common account information cannot be used.
- #2
-
There is no need to specify a value for this item when Y is specified for UseCommonAccount.
-
Execute the jpcconf target setup command to set up the monitoring target for PFM - RM for Platform.
Shown below is an example of executing a command for setting up a monitoring target where inst1 is the instance name and targethost1 is the monitored host. For the -input option, specify the definition file edited in step 2.
jpcconf target setup -key RMPlatform -inst inst1 -target targethost1 -input definition-file-name -noquery
- Note:
-
If the definition file contains confidential information such as passwords, save the definition file in a secure location, and delete it after you have used it. If you want to transfer the definition file between hosts, we recommend that you use a secure file transfer protocol, such as Secure File Transfer Protocol (SFTP), which is FTP over an SSH tunnel.
When all of the settings have been completed, a monitoring target environment can be built. The following table shows the directory structure of the monitoring target environment.
No. |
Storage directory |
File name |
Description |
---|---|---|---|
1 |
/opt#/jp1pc/agt7/agent/instance-name/targets |
monitoring-target-name.ini |
Monitoring target settings file |
2 |
monitoring-target-name.ini.model |
Sample of a monitoring target settings file |
|
3 |
/opt#/jp1pc/agt7/agent/instance-name/targets/monitoring-target-name |
-- |
Work directory for the monitoring target |
- Legend:
-
--: Not applicable
- #
-
If you run a logical host, replace opt with environment-directory.
The following service IDs are added by the monitoring target settings:
- Service IDs to be added
-
-
Remote Agent service
7Ainstance-number instance-name[monitoring-target-name@host-name]
The instance name and monitoring target name will be the values specified in the jpcconf target setup command.
If you specify host1 as the host name of the PFM - RM host, inst1 as the instance name, and targethost1 as the monitoring target name, then the service ID will be as follows:
7A1inst1[targethost1@host1]
For details about the service IDs, see the naming rules provided in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
-
If you want to change information about the monitoring target, re-execute the jpcconf target setup command and update the information. For details about updating a monitoring target, see 3.6.3 Updating a monitoring target.
You can change some settings by using PFM - Web Console to edit properties. For details about the information that can be changed by editing properties, see E.3 List of properties of remote agents and group agents.
(5) Network settings![[Figure]](GRAPHICS/ZUI02001.GIF)
You must specify network settings only if you need to change the network environment settings based on the network configuration specified where Performance Management is used.
There are two types of network environment settings, as described below. Change network settings as necessary.
-
IP address setting
Set this information to use Performance Management in a network that is connected to multiple LANs. You set multiple IP addresses by defining the host names and IP addresses in the jpchosts file. Make sure that the specified jpchosts file is consistent throughout the entire Performance Management system.
For details about the IP address settings, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
-
Port number setting
Set the port numbers used by Performance Management. To avoid confusion during operation, make sure that the specified port numbers and service names are consistent throughout the entire Performance Management system.
For details about the port number settings, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
(6) Changing the log file size![[Figure]](GRAPHICS/ZUI02001.GIF)
The operation status of Performance Management is output to log files unique to Performance Management. This setting is required in order to change the size of these log files.
For the common message log, two files with a size of 2,048 kilobytes each are used by default. For details about changing the common message log, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
(7) Changing performance data storage locations![[Figure]](GRAPHICS/ZUI02001.GIF)
These settings are required in order to change the following settings for the performance data that is managed by PFM - RM for Platform:
-
Database storage location
By default, /opt/jp1pc/agt7/store/instance-name/ is set.
-
Backup location
By default, /opt/jp1pc/agt7/store/instance-name/backup/ is set.
-
Partial backup location
By default, /opt/jp1pc/agt7/store/instance-name/partial/ is set.
-
Export location
By default, /opt/jp1pc/agt7/store/instance-name/dump/ is set.
-
Import location
By default, /opt/jp1pc/agt7/store/instance-name/import/ is set.
- Note
-
If you use a logical host for operation, replace opt with environment-directory.
For details about changing performance data storage locations, see 3.6.1 Changing performance data storage locations.
(8) Setting the connection-target PFM - Manager
You must specify on the PFM - RM host information about the PFM - Manager that manages PFM - RM for Platform. The jpcconf mgrhost define command is used to make this setting.
- Notes about setting the connection-target PFM - Manager
-
-
Only one PFM - Manager can be set as the connection destination even when multiple PFM - RMs are installed on the same host. A different PFM - Manager cannot be specified for each PFM - RM.
-
If PFM - RM for Platform and PFM - Manager are installed on the same host, then the PFM - Manager on the local host is the connection-target PFM - Manager. In this case, you cannot change the connection-target PFM - Manager to any other PFM - Manager. To connect to PFM - Manager on a remote host, install PFM - RM for Platform on a different host than for PFM - Manager.
-
To set the connection-target PFM - Manager:
-
Stop the Performance Management programs and services.
If any Performance Management programs and services are running on the local host, stop all of them before starting the setup procedure. If Performance Management programs and services are running during execution of the jpcconf mgrhost define command, a message is displayed that asks you to terminate them.
For details about how to stop services, see the chapter that describes starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.
-
Execute the jpcconf mgrhost define command with the host name of the connection-target PFM - Manager specified.
The following shows an example of command execution when the connection-target PFM - Manager is located on the host01 host:
jpcconf mgrhost define -host host01
This example shows execution in the interactive mode, but you can also execute the jpcconf mgrhost define command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
(9) Action log output settings![[Figure]](GRAPHICS/ZUI02001.GIF)
These settings are required in order to output action logs at the following times:
-
When a PFM service starts
-
When a PFM service stops
-
When the PFM - Manager connection status is changed
An action log contains log information about exceeded threshold values caused by factors such as system overloads; its output is linked with the alarm function. For details about the action log output settings, see I. Outputting Action Log Data.