8.3.4 Log output

This subsection describes application logs to be output by commands.

Organization of this subsection

(1) Log level
(2) Log file
(3) Output format

(1) Log level

The following table lists and describes the log levels for application logs.

Table 8‒3: List of log levels for application log
No.	Log level	ID	Severity	Description	Monitoring
1	`Error`	`E`	Requires the representative user or the system administrator to correspond.	Indicates that the command processing cannot be continued due to a problem with the execution environment such as the network environment or due to a problem with a parameter entered in the command. This problem requires correspondence by the representative user. In some cases, correspondence by the system administrator might be required. Logs output for the cases of exit codes `16` and `8`.	Y
2	`Warn`	`W`	Temporary problem	Indicates that an abnormal event occurred during command processing. The command processing continues. Log output for the case of exit code `4`.	C
3	`Info`	`I`	Normal event	Log that notifies normal processing on going.	N

Legend:

Y: Log level for which monitoring is required

C: Level for which necessity of monitoring is considered depending on the character of the system

N: Log level for which monitoring is not required

To Page Top

(2) Log file

The following table describes the specifications for log files.

Table 8‒4: Log file specifications
No.	Item	Format or value
1	File format	Text
2	Character code	UTF-8
3	Line feed	CR`+`LF

Log files are output to the path shown below. Storage period is 30 days.

installation-folder\log\dwc-yyyyMMddhhmmss-GUID.log

Legend:

installation-folder: Folder to which the JP1/DH - Server commands are installed
yyyyMMddhhmmss: Command execution date (yyyy: four-digit year, MM: two-digit month, dd: two-digit day, hh: two-digit hour (in 24-hour format), mm: minute, and ss: second)
GUID: Random string in GUID format

Important

Each time a command is executed, a new log is output to the predetermined output destination. If there is no log output destination, a log output destination folder is automatically created so that logs are output to it. Note that log files whose storage period has expired are automatically deleted when a command is started.

To Page Top

(3) Output format

The application log output format is as follows:

date delimiter-character time-of-day version-number log-level message-ID message-text

An application log output example is as follows:

2011/04/19T20:38:21.500 02-07    INFO  DWCO1001_I Command start.
2011/04/19T20:38:28.250 02-07    INFO  DWCO1602_I User information acquisition finished.
2011/04/19T20:38:28.250 02-07    INFO  DWCO1002_I Command finished.

The table below describes application log output details. For details about specific messages, see 14. Messages.

Table 8‒5: Log file output details
No.	Item	No. of digits	Output data
1	`date`	10	`yyyy/MM/dd` `yyyy`: Four-digit year `MM`: Two-digit month `dd`: Two-digit day
2	`delimiter-character`	1	`T`
3	`time-of-day`	12	`HH:mm:ss.SSS` `HH`: Two-digit hour (in 24-hour format) `mm`: Minute `ss`: Second `SSS`: Millisecond Note that the output time of day is the time of day at the client side.
4	`version-number`	8	12-00 Aligned left and filled with a blank character on the right.
5	`log-level`	5	Log level. Aligned left. For details, see 8.3.4 (1) Log level.
6	`message-ID`	10	ID for the message. `XXXXYYYY_Z` `XXXX`: Product code `YYYY`: Message number `Z`: Log level ID (`I`: Info. `W`: Warn, `E`: Error)
7	`message-text`	Variable length	Message content. If a stack trace in Java is included, line feed may be included.

To Page Top