Top
ServerView Resource Orchestrator Cloud Edition V3.0.0 Operation Guide

13.4.1 Investigation Logs on Admin Servers

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 (*1)

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 "14 Messages Starting with VSYS" in the Message Guide CE for information on event logs.

-

-

*1: 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]

Output folder

Output destination file

<Installation directory for this product>\RCXCFMG\logs

vsys_trace_log, vsys_batch_log, cfmg_api_log

<Installation directory for this product>\RCXCTMG\MyPortal\log

myportal_trace.log

[Linux]

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 (*1)

Prefix and message number:

- The prefix for myportal_trace.log is "MGRV".
- The prefix for cfmg_api_log is "PAPI".
- The prefix for all other logs is "VSYS".

message text (*1)

Message content

*1: Refer to the '"Message Guide CE" 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.

  1. Rewrite the settings files corresponding to each log.

    The following table shows the settings file and the location to change:

    [Windows]

    Log name

    Settings file

    Location to change (one location)

    vsys_trace_log

    <Installation directory for this product>\RCXCFMG\config\vsys_log4j.xml

    <param name="File" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\vsys_trace_log" />

    vsys_batch_log

    <Installation directory for this product>\RCXCFMG\config\batch_log4j.xml

    <param name="File" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\vsys_batch_log" />

    myportal_trace.log

    <Installation directory for this product>\RCXCTMG\MyPortal\config\managerview_log4j.xml

    <param name="file" value=" C:/Fujitsu/ROR/RCXCTMG/MyPortal/log/myportal_trace.log" />

    cfmg_api_log

    <Installation directory for this product>\RCXCFMG\config\api_log4j.xml

    <param name="file" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\cfmg_api_log" />

    [Linux]

    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" />

  2. Restart the manager.
    Refer to "7.2 Starting and Stopping the Manager" in the Setup Guide CE for information on how to Restart the manager.