Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference
The performance data collected by PFM - Agent for Enterprise Applications is managed in the Store database of the Agent Store service of PFM - Agent for Enterprise Applications. This subsection describes how to change the storage location of performance data.
- Organization of this subsection
- (1) Using the jpcconf db define (jpcdbctrl config) command to change settings
- (2) Editing the jpcsto.ini file to change settings (for Store version 1.0 only)
(1) Using the jpcconf db define (jpcdbctrl config) command to change settings
To change the data storage directories listed below for the performance data that is to be managed in the Store database, use the jpcconf db define (jpcdbctrl config) command. If you wish to save the performance data already in the Store database storage directory prior to the change, use the -move option of the jpcconf db define (jpcdbctrl config) command. For details about the jpcconf db define (jpcdbctrl config) command, see the manual Job Management Partner 1/Performance Management Reference.
- Storage directory
- Backup directory
- Export directory
- Partial backup directory#
- Import directory#
- #: Supported only when Store version 2.0 is used.
The following table lists and describes the information that can be set by the jpcconf db define (jpcdbctrl config) command, such as option names and value ranges.
Table 3-8 Command settings for changing the performance data storage location
Description Option name Permitted value (Store version 1.0) Permitted value (Store version 2.0) Default value Performance data creation directory sd 1 to 127 bytes of full path name 1 to 214 bytes of full path name#1 /opt/jp1pc/agtm/store/instance-name Performance data creation directory (for logical host operation) sd 1 to 127 bytes of full path name 1 to 214 bytes of full path name#1 environment-directory#2/jp1pc/agtm/store/instance-name Performance data backup directory (full backup) bd 1 to 127 bytes of full path name 1 to 211 bytes of full path name#3 /opt/jp1pc/agtm/store/instance-name/backup Performance data backup directory (full backup during logical host operation) bd 1 to 127 bytes of full path name 1 to 211 bytes of full path name#3 environment-directory#2/jp1pc/agtm/store/instance-name/backup Performance data backup directory (partial backup) pbd -- 1 to 214 bytes of full path name#1 /opt/jp1pc/agtm/store/instance-name/partial Performance data backup directory (partial backup during logical host operation) pbd -- 1 to 214 bytes of full path name#1 environment-directory#2/jp1pc/agtm/store/instance-name/partial Maximum generation number when performance data is backed up bs 1 to 9 1 to 9 5 Performance data export directory dd 1 to 127 bytes of full path name 1 to 127 bytes of full path name /opt/jp1pc/agtm/store/instance-name/dump Performance data export directory (for logical host operation) dd 1 to 127 bytes of full path name 1 to 127 bytes of full path name environment-directory#2/jp1pc/agtm/store/instance-name/dump Performance data import directory id -- 1 to 222 bytes of full path name#4 /opt/jp1pc/agtm/store/instance-name/import Performance data import directory (for logical host operation) id -- 1 to 222 bytes of full path name#4 environment-directory#2/jp1pc/agtm/store/instance-name/import
- Legend:
- --: Cannot be set
- #1
- If a relative path is set, the length of the specified directory path (absolute path) must not exceed 214 bytes.
- #2
- The environment directory is located on the shared disk that was specified when the logical host was created.
- #3
- If a relative path is set, the length of the specified directory path (absolute path) must not exceed 211 bytes.
- #4
- If a relative path is set, the length of the specified directory path (absolute path) must not exceed 222 bytes.
(2) Editing the jpcsto.ini file to change settings (for Store version 1.0 only)
If you are using Store version 1.0, you can directly edit jpcsto.ini.
(a) Settings in the jpcsto.ini file
The table below shows the settings in the jpcsto.ini file, such as the label names that can be edited and the permitted value ranges.
Table 3-9 Settings for the performance data storage location ([Data Section] section in jpcsto.ini)
Description Label name Permitted value(Store version 1.0)#1 Default value Performance data creation directory Store Dir#2 1 to 127 bytes of full path name /opt/jp1pc/agtm/store/instance-name Performance data creation directory Store Dir#2 1 to 127 bytes of full path name environment-directory#3/jp1pc/agtm/store/instance-name Performance data backup directory (full backup) Backup Dir#2 1 to 127 bytes of full path name /opt/jp1pc/agtm/store/instance-name/backup Performance data backup directory (full backup during logical host operation) Backup Dir#2 1 to 127 bytes of full path name environment-directory#3/jp1pc/agtm/store/instance-name/backup Maximum generation number when performance data is backed up Backup Save 1 to 9 5 Performance data export directory Dump Dir#2 1 to 127 bytes of full path name /opt/jp1pc/agtm/store/instance-name/dump Performance data export directory (for logical host operation) Dump Dir#2 1 to 127 bytes of full path name environment-directory#3/jp1pc/agtm/store/instance-name/dump
- #1
- Specify all directory names as full path names.
- All alphanumeric characters, symbols, and the space are permitted, except for the following characters:
;, ,, *, ?, ', ", <, >, |
- If a specified value is invalid, the Agent Store service cannot be started.
- #2
- No duplication of directory names can be specified in Store Dir, Backup Dir, and Dump Dir.
- #3
- The environment directory is located on the shared disk that was specified when the logical host was created.
(b) Preparations before editing the jpcsto.ini file
- In order to change the Store database storage directory, you must first create the storage directory that is to be used.
- Once you have changed the Store database storage directory, the performance data that was collected previously is no longer available. If you need the previous performance data, the following procedure can be used to inherit it:
- Use the jpctool db backup (jpcctrl backup) command to make a backup of the performance data that is stored in the existing Store database.
- Change the Store database storage directory according to the procedure described in 3.4.1(2)(c) Editing the jpcsto.ini file.
- Use the jpctool db restore (jpcresto) command to restore the backup data into the new directory.
(c) Editing the jpcsto.ini file
To edit the jpcsto.ini file:
- Stop the PFM - Agent services.
If PFM - Agent programs and services are running at the local host, stop all of them.
- Use a program such as a text editor to open the jpcsto.ini file.
- Make necessary changes (e.g., change the performance data storage directory).
Correct the shaded information shown below, as necessary.
Notes
- Do not enter any space characters at the beginning of a line or before or after an equal sign (=).
- A period (.) in a label value indicates the default storage directory for the Agent Store service's Store database (/opt/jp1pc/agtm/store/instance-name). To change the storage directory, specify a path relative to this directory or the absolute path.
- To change the Store database storage location, you must have already created the directory that you specify here.
- The jpcsto.ini file contains not only the database storage directory but also definition information. Make sure that you do not change any values other than in the [Data Section] section. If a value outside the [Data Section] section is changed, Performance Management might not function normally.
- Save the jpcsto.ini file and then close it.
- Start the Performance Management programs and services.
- Note
- If you have used this procedure to change the Store database storage directory, the previous performance data still remains in the old directory. If you do not need these files, delete only the following files:
- All files whose extension is .DB
- All files whose extension is .IDX
All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.