The investigation logs on Admin Servers are classified into the following types:
Log name | Description | File size | Number of generations |
|---|---|---|---|
vsys_trace_log | Trace logs for the management of L-Platform template and L-Platform are output to this log. | 10MB | 10 generations (*) |
vsys_batch_log | Trace logs for the batch processing section of the management of L-Platform template and L-Platform are output to this log. | ||
myportal_trace.log | Trace logs for the Manager View are output to this log. | ||
cfmg_api_log | Logs for the CFMG APIs are output to this log. | ||
Event log | Information such as errors that occur while the Manager View is being used is output to this log. Refer to "Chapter 20 Messages Starting with VSYS" in the "Messages" for information on event logs. | - | - |
* Note: If this number is exceeded, old generations will be deleted, starting with the oldest generation.
Output Destination
The log output destinations are shown below:
[Windows Manager]
Output folder | Output destination file |
|---|---|
Installation_folder\RCXCFMG\logs | vsys_trace_log, vsys_batch_log, cfmg_api_log |
Installation_folder\RCXCTMG\MyPortal\log | myportal_trace.log |
[Linux Manager]
Output destination directory | Output destination file |
|---|---|
/var/opt/FJSVcfmg/logs | vsys_trace_log, vsys_batch_log, cfmg_api_log |
/var/opt/FJSVctmyp/log | myportal_trace.log |
Output format
Output format |
|---|
<date/time> <log level> <message ID> <message text> |
Item | Description | |
|---|---|---|
date/time | yyyy-mm-dd hh:mm:ss,sss | |
log level | One of the following: | |
info | Information level message | |
warn | Warning level message | |
error | Error level message | |
fatal | Fatal level message | |
message ID (*) | Prefix and message number: - The prefix for myportal_trace.log is "MGRV". | |
message text (*) | Message content | |
* Note: Refer to the '"Messages" for information on the message ID and message text.
Procedure for changing the investigation output destination
Use the following procedure to change the output destination for investigation logs.
Rewrite the settings files corresponding to each log.
The following table shows the settings file and the location to change:
[Windows Manager]
Log name | Settings file | Location to change (one location) |
|---|---|---|
vsys_trace_log | Installation_folder\RCXCFMG\config\vsys_log4j.xml | <param name="File" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\vsys_trace_log" /> |
vsys_batch_log | Installation_folder\RCXCFMG\config\batch_log4j.xml | <param name="File" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\vsys_batch_log" /> |
myportal_trace.log | Installation_folder\RCXCTMG\MyPortal\config\managerview_log4j.xml | <param name="file" value=" C:/Fujitsu/ROR/RCXCTMG/MyPortal/log/myportal_trace.log" /> |
cfmg_api_log | Installation_folder\RCXCFMG\config\api_log4j.xml | <param name="file" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\cfmg_api_log" /> |
[Linux Manager]
Log name | Settings file | Location to change (one location) |
|---|---|---|
vsys_trace_log | /etc/opt/FJSVcfmg/config/vsys_log4j.xml | <param name="File" value="/var/opt/FJSVcfmg/logs/vsys_trace_log" /> |
vsys_batch_log | /etc/opt/FJSVcfmg/config/batch_log4j.xml | <param name="File" value="/var/opt/FJSVcfmg/logs/vsys_batch_log" /> |
myportal_trace.log | /etc/opt/FJSVctmyp/config/managerview_log4j.xml | <param name="file" value="/var/opt/FJSVctmyp/log/myportal_trace.log" /> |
cfmg_api_log | /etc/opt/FJSVcfmg/config/api_log4j.xml | <param name="File" value="/var/opt/FJSVcfmg/logs/cfmg_api_log" /> |
Restart the manager.
Refer to "2.1 Starting and Stopping the Manager" for information on how to Restart the manager.
