A.1 List of files and directories (in Windows)
In the following tables, the Base_Path indicates the installation-folder in this manual. The default location of Base_Path is as follows:
system-drive\Program Files (x86)\Hitachi\jp1base
SystemDrive in the table is the same as system-drive used in the body of this manual.
Contents |
File name/folder name |
---|---|
Command storage folder |
Base_Path\bin\ Base_Path\bin\ext |
Environment settings folder#1 |
Base_Path\conf\ shared-folder\jp1base\conf\ |
Language type settings file |
Base_Path\conf\jp1bs_param.conf shared-folder\jp1base\conf\jp1bs_param.conf |
Configuration definition file |
Base_Path\conf\route\jbs_route.conf shared-folder\jp1base\conf\route\jbs_route.conf |
Startup process definition file |
Base_Path\cconf\jp1bs_spmd.conf Base_Path\cconf\conf\jp1bs_spmd.conf.model (No authentication server startup (2038-non compliant)) Base_Path\conf\conf\jp1bs_spmd.conf.session.model (Authentication server startup (2038-non compliant)) Base_Path\cconf\conf\jp1bs_spmd.conf.2038_model (No authentication server startup (2038 compliant)) Base_Path\cconf\conf\jp1bs_spmd.conf.session.2038_model (Authentication server startup (2038 compliant)) |
JP1/IM function header file |
Base_Path\include\JevApi.h |
Log folder#2 |
Base_Path\log\ shared-folder\jp1base\log\ |
Folder for plug-in |
Base_Path\plugin\ |
Operating information storage folder |
Base_Path\sys\OPI\ shared-folder\jp1base\sys\OPI\ |
Readme file |
Base_Path\readme.txt |
Product number and version information |
Base_Path\Version.txt |
License type information |
Base_Path\ProductInfo.txt |
Event database storage folder#3 |
Base_Path\sys\event\servers\#4 shared-folder\jp1base\event\#4 |
jp1hosts2 information |
Base_Path\sys\jp1hosts2\hostdb{0|1}.bin shared-folder\jp1base\sys\jp1hosts2\hostdb{0|1}.bin |
Log and temporary folder#2 |
Base_Path\sys\tmp\event\servers\#4 |
|
|
|
|
Tool folder |
Base_Path\tools\ |
|
|
|
|
|
|
|
|
Integrated trace log folder |
[32bit] system-drive\Program Files (x86)\Hitachi\HNTRLib2\spool\ [64bit] system-drive\Program Files\Hitachi\HNTRLib2\spool\ |
IT Report Utility (system information collection tool) folder |
|
Forwarding suppression status management folder |
Base_Path\conf\event\servers\default\suppress#4 |
Forwarding suppression information folder for each agent |
Base_Path\conf\event\servers\default\suppress\agent-host-name#4 |
Auto-scaling linkage script folder#1 |
Base_Path\tools\cloud\ |
|
|
|
|
|
|
|
|
Common definition information backup file output folder |
Windows-installation-folder\Temp\JP1_COMDEF\ |
|
|
|
|
|
#1: For details on definition files, see A.1(1) List of definition files (in Windows).
#2: For details on log files, see A.1(2) List of log files (in Windows).
#3: For details on event database file names, see 2.3.2 Event database.
#4: This file or folder is stored in a different folder if you specify another path in the event server index file (index).
#5: For a server OS that is Windows Server 2012 or later.
- Organization of this subsection
(1) List of definition files (in Windows)
Function |
File name/folder name |
---|---|
Startup control |
|
|
|
Event service |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Event conversion |
|
|
|
|
|
|
|
Event service definition information collection and distribution |
|
|
|
|
|
User management |
|
|
|
|
|
|
|
|
|
|
|
Health check function |
|
|
|
|
|
Plugin service |
|
Operation log output function |
|
Process management |
|
|
|
Communication settings |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Local action function |
|
|
|
|
|
Collection of JP1/Base setup information in a single operation |
|
Configuration management functionality |
|
Auto-scaling linkage scripts |
|
|
|
Destination communications port specification function |
|
|
#1: This file or folder is stored in a different folder if you specify another path in the event server index file (index).
#2: This file does not exist unless definition information distribution is used.
(2) List of log files (in Windows)
The table below lists the log files that JP1/Base outputs by default.
- Important
-
JP1/Base also outputs some internal log files required for program maintenance. There is no need for users to reference or modify these internal log files. You might need to keep these files temporarily for data collection purposes if a system error occurs.
Log type indicates the type of log to which JP1/Base outputs data.
File name/folder name indicates the full path of the log file name when JP1/Base is installed using the default settings, and the log file name when JP1/Base is used in a cluster system.
Max. disk space indicates the maximum space the log file uses on a disk. If there are multiple log files, this column indicates the total.
File changing timing indicates when JP1/Base switches the output log files. Output destinations are changed when the indicated file size is reached or when the indicated event occurs. If there is only one log file, file changing causes that log file to be overwritten. If there are multiple log files and the maximum disk space has been reached, the file with the oldest update date is overwritten.
Log type |
File name/folder name |
Max. disk space |
File changing timing |
---|---|---|---|
Process management log |
|
384 KB |
128 KB |
|
384 KB |
128 KB |
|
|
384 KB |
128 KB |
|
Authentication server log |
|
5 MB |
640 KB |
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
Log of the authentication server setting command |
|
5 MB |
640 KB |
|
128 KB |
64 KB |
|
Log of the environment settings program |
|
128 KB |
64 KB |
Log of the logical host setting program |
|
2,000 KB |
1,000 KB |
|
128 KB |
64 KB |
|
|
1.2 GB#3 |
None |
|
|
2 MB#3 |
None |
|
|
1 KB |
When the command is executed |
|
|
1.2 GB#3 |
None |
|
|
2 MB#3 |
None |
|
|
1 KB |
When the command is executed |
|
Common definition information log |
|
128 KB |
64 KB |
Log of jp1hosts information command |
|
128 KB |
64 KB |
User mapping command log |
|
128 KB |
64 KB |
Remote command log#2 |
|
20 MB |
2.5 MB |
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
Plug-in service log |
|
5 MB |
640 KB |
|
50 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
2,048 KB |
256 KB |
|
|
5 MB |
640 KB |
|
|
2,048 KB |
256 KB |
|
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
Configuration management log#2 |
|
20 MB |
4 MB |
Start sequence control log |
|
128 KB |
64 KB |
Event log trap trace log |
|
1,024 KB |
512 KB |
Trap log for event log traps |
|
4,096 KB |
1,024 KB |
Log of the health check function (local host monitoring) |
|
50 MB |
6.25 MB |
Log of the health check function (remote host monitoring) |
|
50 MB |
6.25 MB |
Health check command log |
|
50 MB |
6.25 MB |
Log of the health check API |
|
50 MB |
6.25 MB |
Application error log |
|
5 MB |
5 MB |
Operation log |
|
68 MB#5 |
1,024 KB#5#6 |
Trace log for the event setting, centralized management, and acquisition command |
|
192 KB |
When the command is executed |
Trace log for event setting, centralized management, and distribution command |
|
192 KB |
When the command is executed |
Trace log of the event service |
|
12.5 MB#8 |
When the event service starts |
|
5 MB#8 |
When the event service starts |
|
Transfer error log of the event service |
|
5 MB#8 |
When the event service starts |
Error log of the event service |
|
2,500 KB#8 |
When the event service starts |
Log of the event service API. |
|
5 MB#9 |
1 MB#9 |
Log of the event service |
|
5 MB |
1 MB |
Event service message settings change log |
|
10 KB |
5 KB |
Error log of the log file trap |
|
A few hundred bytes#12 |
When the log file trap starts |
Log of the log file trap |
|
5 MB#13 |
1 MB#13 |
Log-file trap startup execution results log |
|
3 MB |
1 MB |
Remote monitoring log (log-file trap) |
|
5 MB |
1 MB |
Remote monitoring log (event log trap) |
|
5 MB |
1 MB |
Installation log |
|
1 MB |
200 KB |
|
1 MB |
200 KB |
|
|
50 KB |
10 KB |
|
|
50 KB |
10 KB |
|
The output destination in the remote desktop service (formerly known as the terminal service) of the server OS changes as follows:
|
25 KB |
At installation |
|
|
256 KB |
256 KB |
|
|
1,024 KB |
256 KB |
|
|
1,024 KB |
256 KB |
|
Trace log for inter-process communication |
|
10 MB |
2.5 MB |
|
10 MB |
2.5 MB |
|
|
10 MB |
2.5 MB |
|
|
10 MB |
2.5 MB |
|
|
10 MB |
2.5 MB |
|
Error log of the command for collecting operating information |
|
5 MB |
1 MB |
Log for the operating information API |
|
5 MB |
1 MB |
Service management control log |
|
10 MB |
2.5 MB |
Trace log of the service management control |
|
10 MB |
2.5 MB |
Log of the service management control API |
|
10 MB |
2.5 MB |
Local action execution log |
|
1,024 KB#14 |
256 KB#14 |
Local action log |
|
2,048 KB |
256 KB |
|
2,048 KB |
256 KB |
|
|
2,048 KB |
256 KB |
|
Product information log |
|
5 MB |
1 MB |
JP1/Base communications base log |
|
5 MB |
1 MB |
Individual log for the setup information collection command |
|
2 MB |
1 MB |
Log for recording starting and stopping of forwarding suppression |
|
128 KB |
64 KB |
Trace log for the event-forwarding suppression command |
|
5 MB |
1 MB |
Log of the command for the destination communications port settings |
|
6MB |
1MB |
#1: The value set in the environment variable %ALLUSERSPROFILE% at installation is used.
#2: Log file for JP1/IM - Manager
#3: You can use the jcocmddef command of JP1/IM - Manager with the -record option specified to change this to a value within the range below.
-
If the number of the records is 1 (-record 1)
DRF file: 7 KB, K01 file: 4 KB
-
If the number of records is 20,000 (the default setting)
DRF file: 125 MB, K01 file: 200 KB
-
If the number of the records is 196,600 (-record 196600)
DRF file: 1.2 GB, K01 file: 2 MB
#4: Indicates a jbsplugincom process identification number.
#5: You can use the operation log definition file (jp1bs_baselog_setup.conf) to change the number of files and the maximum disk space. For details on the range of specifiable values, see I.5 Settings for outputting operation logs.
#6: You can specify whether to automatically switch files at JP1/Base startup in the operation log definition file (jp1bs_baselog_setup.conf).
#7: This file or folder is stored in a different folder if you specify another path in the event server index file (index).
#8: You can change the number of files and the maximum disk space using the event server settings file (conf). For details on the range of specifiable values, see Event server settings file in 16. Definition Files.
#9: You can use the API settings (api) file to change the number of files and the maximum disk space. For details on the range of specifiable values, see API settings file in 16. Definition Files.
#10: The value set in the environment variable %ALLUSERSPROFILE% at execution is used.
#11: One line equals approximately 100 bytes.
#12: A file is created when the log file trap starts, and is deleted when the log file trap terminates normally. If an error occurs, the file remains when the log file trap terminates. If the log file trap generates frequent errors, there will be a large number of error files. Therefore, you need to delete unnecessary error files.
#13: You can change the number of files and the maximum disk space they occupy in the log information definition file (jevlogd.conf). For details on the range of specifiable values, see Log information definition file in 16. Definition Files.
#14: You can use the common definition settings file (local action function) to change the number of files and the maximum disk space. For details on the range of specifiable values, see Common definition settings file (local action function) in 16. Definition Files.
#15: Logs are output in HNTRLib2 format (multi-process trace).
#16: When deleting this log data, also delete the mmap folder at the output destination.