7.3.1 Output modes and notes for log files and trace files
The failure information includes information that is output to log files and trace files, which are managed in certain modes, such as rotation and switchover. The following table shows the modes that can be used for log and trace data output by the service platform:
Log type |
Rotation method |
Method to switch the output destination file |
|||
---|---|---|---|---|---|
Wraparound mode |
Shift mode |
Switching with file size |
Switching with the file size or at a timing |
||
Message log |
HCSC-Manager log |
A |
N |
A |
N |
Integrated message log |
A |
Y |
A |
Y |
|
Activity log of J2EE server |
A |
Y |
A |
Y |
|
Request trace |
A |
Y |
A |
Y |
|
Performance analysis trace |
- |
- |
- |
- |
|
User message trace |
A |
Y |
A |
Y |
|
Maintenance log |
A |
Y |
A |
Y |
|
Message log for user-authentication information management commands |
A |
N |
A |
N |
The following briefly explains the rotation and switchover modes of output-destination files. For details, see 3.2.1 Specifiable contents in the Application Server Maintenance and Migration Guide.
- Organization of this subsection
(1) Output-destination file rotation modes
The following table shows the rotation modes:
Description |
|
---|---|
Numbers of files are added to the file name.
|
|
The file name is fixed, and the numbers of files are added to the name of backup files.
|
(2) Output-destination file switchover modes
The current log file or trace file switches based on a certain condition. The two switchover modes are as follows:
-
Switching with the file size
When the file size reaches the specified value, you can switch the output destination file.
-
Switching with the file size or at a timing
If either of the following conditions is met, you can switch the output destination file.
-
The specified time has been reached.
-
The specified file size has been reached.
-
You need to estimate the proper trace file size. Estimate the total size of trace files based on the following information:
-
Quantity of messages received per day (in messages)
-
Duration of saved trace information (in days)
Calculate the total size of files, and then estimate the size of one trace file and the number of files that will be needed based on the calculated total file size.
Set the trace file size and number of trace files in the HCSC server runtime definition file. For details about the file, see 6.5.6 HCSC server runtime definition file in the Service Platform Reference Guide.
(3) Notes on acquisition of log and trace data: General notes
The following notes apply to all logs and traces other than the performance analysis traces:
-
Files cannot be edited.
-
A text viewer or editor with a lock option is not supported. If files are locked, no trace can be output.
-
File access permissions cannot be changed.
If you need to set access permissions manually, set appropriate access permissions. If the access permissions you set are not appropriate, trace output is disabled.
-
The file update time cannot be changed.
If you change the file update time, the output target file may be altered.
-
Do not rename or delete a file during trace output processing.
The target file can be determined from information in the management file. If the management file is not available or is damaged, the output target file is determined based on the file update time. If you need to rename or delete a file, first terminate all trace output processes.
(4) Notes on acquisition of log and trace data: Notes for only HCSC-Manager logs
-
The linefeed code at the end of a message is always CR+LF regardless of the platform you are using.
-
The following notes also apply to exception and maintenance logs:
-
After you have changed the file size and/or number of files, to apply the changes, you must delete files. Before you delete a file, terminate the trace output process. Delete all files in the directory specified for the cscmng.log.dir property in the HCSC-Manager definition file.
-
In an output trace file, data up to the first EOF character (0x1A) is valid. Data following the EOF character is not guaranteed. Note that the first EOF character may be followed by another EOF character.
-
Even when a trace is output, updating of the file update time is not guaranteed. Whether or not the trace has been output cannot be determined based on the file update time. The file update time is updated when trace output processing is terminated.
-