Top
Systemwalker Software Configuration Manager Operation Guide
FUJITSU Software

4.1.1 Logs Output on the Admin Server

The types of logs that are output on the admin server are shown in the tables below.

Audit logs

Log name

Description

Size

Number of generations

cfmg_audit_log

Audit log.

10 MB

10 generations (*1)

*1: If this number is exceeded, previous generations will be deleted, starting with the oldest.

Investigation logs

Log name

Description

Size

Number of generations

managerview_trace_log

Trace log for the management console.

10 MB

10 generations (*1)

cfmgbase_trace_log

Trace log for the manager itself.

cfmgdiscovery_trace_log

Trace log for the discovery function.

cfmgcommand_trace_log

Trace log for the following commands:

  • Status display command

  • Start command

  • Stop command

  • Email resend command

  • Backup command

  • Restore command

  • Problem investigation data collection command

cfmgcommand_discovery_trace_log

Trace log with the following:

  • Information that is output when all information is collected using the patch information update command

  • Information that is output when parameter information is collected using the parameter information update command.

cfmgcommand_discovery_wsus_trace_log

Trace log with the following:

  • Information that is output when only WSUS information is collected using the patch information update command

cfmgcommand_discovery_yum_trace_log

Trace log with the following:

  • Information that is output when only yum information is collected using the patch information update command

cfmgcommand_discovery_sol_trace_log

A trace log with the following is output:

  • Information that is output when only Solaris information is collected using the patch information update command.

cfmgcommand_discovery_fjmw_trace_log

Trace log with the following:

  • Information that is output when only Fujitsu middleware information is collected using the patch information update command

mdr_cfmg_srv.log

A trace log with the following is output:

  • Information that is output when hardware/virtual environment information is collected using cmdbrefresh (Observed Record Collection Request Command).

Event log (Windows)

Contains information such as information about errors that occurs while patch application status information for deployed servers is being collected.

-

-

Syslog (Linux)

Contains information such as information about errors that occurred while patch application status information for deployed servers was being collected.

-

-

*1: If this number is exceeded, previous generations will be deleted, starting with the oldest.

4.1.1.1 Log Output Destination

The output destination for mdr_cfmg_srv.log is shown below.

[Windows]

Output folder

Output file

%SWCMDB_INSTALL_PATH%\FJSVcmdbm\var\log

Same as the log name.

[Linux]

Output folder

Output file

/opt/FJSVcmdbm/var/log

Same as the log name.

The output destination for other logs is shown below.

[Windows]

Output folder

Output file

<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\logs

Same as the log name.

[Linux]

Output folder

Output file

/var/opt/FJSVcfmgm/logs

Same as the log name.

4.1.1.2 Output Format for Audit Logs

The output format for audit logs is as shown below. It is possible to change the output destination for audit logs, the file size, and the number of generations held.

Output format for audit logs

Output format

<Operation date/time>,<User ID>,<Tenant name>,<Operation type>,<Parameters>,<Operation result>

Item

Description

Operation date/time

YYYY-MM-DD HH:MM:SS.sss (local time)

User ID

The user ID of the user that executed the operation

Tenant name

The tenant name of the user that executed the operation

Note: For operations performed by infrastructure administrators, "admin" is output.

Operation type

A string indicating the content of the operation

Parameters

The parameters specified by the request

Operation result

"SUCCESS" if the operation was successful and "FAILURE" if the operation failed

Operation type

Operation type

Description

/managerview/login.json

Performs login

/managerview/logout.json

Performs logout

/managerview/userInfo.json

Acquires user information

/managerview/org/list.json

Acquires a list of tenants

/managerview/ls/list.json

Acquires a list of servers

/managerview/ls/map.json

Acquires the map of unapplied patches

/managerview/ls/copy.json

Copies a list of servers

/managerview/ls.json

Acquires server details

/managerview/info/list.json

Acquires notifications

/managerview/windows.csv

Outputs Windows patch information to a CSV file

/managerview/patch/windows/list.json

Acquires a list of Windows patches

/managerview/patch/windows/map.json

Acquires the map of servers with unapplied Windows patches

/managerview/windows.json

Acquires Windows patch details

/managerview/patch/copy.json

Copies a list of Windows patches

/managerview/patch/linux.csv

Outputs Linux patch information to a CSV file

/managerview/patch/linux/list.json

Acquires a list of Linux patches

/managerview/patch/linux/map.json

Acquires the map of servers with unapplied Linux patches

/managerview/patch/linux.json

Acquires Linux patch details

/managerview/wsus.json

Refreshes

/managerview/patchType/list.json

Acquires a list of patch types

/managerview/patchSummary/list.json

Acquires a summary of patches

/managerview/midPatch.csv

Outputs Fujitsu middleware patch information to CSV file

/managerview/midPatch/list.json

Acquires a list of Fujitsu middleware patches

/managerview/midPatch/map.json

Acquires the map of servers with unapplied Fujitsu middleware patches

/managerview/midPatch.json

Acquires details on Fujitsu middleware patches

/managerview/baseLine/list.json

Acquires a list of configuration baselines

/managerview/baseLine/patchComp.json

Compares Windows patches

/managerview/baseLine/linux/patchComp.json

Compares Linux patches

/managerview/baseLine/midPatchComp.json

Compares Fujitsu middleware patches

/managerview/software/list.json

Acquires a list of software programs

/managerview/software.json

Acquires software details

/managerview/appliedPatch.csv

Outputs patch application information to a CSV file

/managerview/appliedPatch.do

Applies patches

/managerview/software/map.json

Acquires the map of servers for which software parameters can be configured

/managerview/lsParameter.json

Acquires parameter information

/managerview/lsParameter.csv

Outputs parameter information to CSV file

/managerview/parameterSettingDefinition.json

Acquires the parameter settings definition

/managerview/parameterDesignDefinition.json

Acquires parameter settings information

/managerview/parameterDefinition/list.json

Acquires a list of parameter settings information

/managerview/execParameter.csv

Outputs parameter settings information to CSV file

/managerview/execScript.csv

Outputs script execution information to CSV file

Procedure for changing the audit log output destination

Use the following procedure to change the audit log output destination:

  1. Rewrite the configuration file.

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

    [Windows]

    Log name

    Configuration file

    Location to change (one location)

    cfmg_audit_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_base_log4j.xml

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmg_audit_log" /> element under the <appender name="cfmgaudit" class="org.apache.log4j.RollingFileAppender"> element

    [Linux]

    Log name

    Configuration file

    Location to change (one location)

    cfmg_audit_log

    /etc/opt/FJSVcfmgm/config/manager_base_log4j.xml

    The <param name="File" value="/var/opt/FJSVcfmgm/logs/cfmg_audit_log"/> element under the <appender name="cfmgaudit" class="org.apache.log4j.RollingFileAppender"> element

  2. Restart Systemwalker Software Configuration Manager.

Procedure for changing the size of the audit log file

Use the following procedure to change the size of the audit log file:

  1. Rewrite the configuration file.

    The location to change is shown below.

    [Windows]

    Log name

    Configuration file

    Location to change (one location)

    cfmg_audit_log

    <Systemwalker Software Configuration Manager Installation directory>\SWCFMGM\config\manager_base_log4j.xml

    Change the underlined part of the <param name="MaxFileSize" value="10MB" /> element under the <appender name="cfmgaudit" class="org.apache.log4j.RollingFileAppender"> element to a desired value.

    Example: value="100MB" (to change the size of the audit log file to 100 MB)

    [Linux]

    Log name

    Configuration file

    Location to change (one location)

    cfmg_audit_log

    /etc/opt/FJSVcfmgm/config/manager_base_log4j.xml

    Change the underlined part of the <param name="MaxFileSize" value="10MB" /> element under the <appender name="cfmgaudit"class="org.apache.log4j.RollingFileAppender"> element to a desired value.

    Example: value="100MB" (to change the size of the audit log file to 100 MB)

  2. Restart Systemwalker Software Configuration Manager.

Procedure for changing the number of audit log generations to be held

Use the following procedure to change the number of generations to be held for each audit log.

  1. Rewrite the configuration file.

    The location to change is shown below.

    [Windows]

    Log name

    Configuration file

    Location to change (one location)

    cfmg_audit_log

    <Systemwalker Software Configuration Manager Installation directory>\SWCFMGM\config\manager_base_log4j.xml

    Change the underlined part of the <param name="MaxBackupIndex" value="9" /> element under the <appender name="cfmgaudit" class="org.apache.log4j.RollingFileAppender"> element to a desired value.

    Example: value="100" (to change the number of generations to 100)

    [Linux]

    Log name

    Configuration file

    Location to change (one location)

    cfmg_audit_log

    /etc/opt/FJSVcfmgm/config/manager_base_log4j.xml

    Change the underlined part of the <param name="MaxBackupIndex" value="9" /> element under the <appender name="cfmgaudit"class="org.apache.log4j.RollingFileAppender"> element to a desired value.

    Example: value="100" (to change the number of generations to 100)

  2. Restart Systemwalker Software Configuration Manager.

4.1.1.3 Investigation Logs

The output format for investigation logs is as below. The output destination for investigation logs can be changed.

Output format for investigation logs

Output format

<Date/time> <Log level> <Message ID> <Message text>

Item

Description

Date/time

YYYY-MM-DD HH:MM:SS.sss (local time)

Log level

One of the following:

info

Information message

warn

Warning message

error

Error message

fatal

Fatal message

Message ID

The prefix and message number

  • The prefix for managerview_trace_log is "MGRV".

  • The prefix for cfmgbase_trace_log is "BASE".

  • The prefix for cfmgdiscovery_trace_log is "DISCOVERY".

Message text

Body text of the message

Procedure for changing the investigation log output destination

Use the following procedure to change the investigation log output destination:

  1. Rewrite the configuration files corresponding to each log.

    The following table shows the configuration files and the locations to change:

    [Windows]

    Log name

    Configuration file

    Location to change (one location)

    managerview_trace_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_base_log4j.xml

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/managerview_trace_log" /> element under the <appender name="managerviewtrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgbase_trace_log

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgbase_trace_log" /> element under the <appender name="cfmgbasetrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgdiscovery_trace_log

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgdiscovery_trace_log" /> element under the <appender name="cfmgdiscoverytrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_trace_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_log4j.xml

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_discovery_trace_log" /> element under the <appender name="cfmgbasetrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_trace_log

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_trace_log" /> element under the <appender name="cfmgcommandtrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_base_trace_log

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_base_trace_log" /> element under the <appender name="cfmgbasetrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_trace_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_discovery_log4j.xml

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_discovery_trace_log" /> element under the <appender name="cfmgbasetrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_wsus_trace_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_discovery_wsus_log4j.xml

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_discovery_wsus_trace_log" /> element under the <appender name="cfmgdiscoverytrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_yum_trace_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_discovery_yum_log4j.xml

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_discovery_yum_trace_log" /> element under the <appender name="cfmgdiscoverytrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_sol_trace_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_discovery_sol_log4j.xml

    <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_discovery_sol_trace_log" /> under the element <appender name="cfmgdiscoverytrace" class="org.apache.log4j.RollingFileAppender">

    cfmgcommand_discovery_fjmw_trace_log

    <Systemwalker Software Configuration Manager installation directory>\SWCFMGM\config\manager_discovery_fjmw_log4j.xml

    The <param name="File" value="<Systemwalker Software Configuration Manager installation directory>/SWCFMGM/logs/cfmgcommand_discovery_fjmw_trace_log" /> element under the <appender name="cfmgdiscoverytrace" class="org.apache.log4j.RollingFileAppender"> element

    [Linux]

    Log name

    Configuration file

    Location to change (one location)

    managerview_trace_log

    /etc/opt/FJSVcfmgm/config/manager _base_log4j.xml

    The <param name="File" value="/var/opt/FJSVcfmgm/logs/managerview_trace_log" /> element under the <appender name="managerviewtrace" class="org.apache.log4j.RollingFileAppender"> element

    cfmgbase_trace_log

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgbase_trace_log" /> element under the <appender name="cfmgbasetrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgdiscovery_trace_log

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgdiscovery_trace_log" /> element under the <appender name="cfmgdiscoverytrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_trace_log

    /etc/opt/FJSVcfmgm/config/manager_log4j.xml

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgcommand_trace_log" /> element under the <appender name="cfmgcommandtrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_base_trace_log

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgcommand_base_trace_log" /> element under the <appender name="cfmgbasetrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery__trace_log

    /etc/opt/FJSVcfmgm/config/manager_discovery_log4j.xml

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgcommand_discovery_trace_log" /> element under the <appender name="cfmgdiscoverytrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_wsus_trace_log

    /etc/opt/FJSVcfmgm/config/manager_discovery_wsus_log4j.xml

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgcommand_discovery_wsus_trace_log" /> element under the <appender name="cfmgdiscoverytrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_yum_trace_log

    /etc/opt/FJSVcfmgm/config/manager_discovery_yum_log4j.xml

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgcommand_discovery_yum_trace_log" /> element under the <appender name="cfmgdiscoverytrace"class="org.apache.log4j.RollingFileAppender"> element

    cfmgcommand_discovery_sol_trace_log

    /etc/opt/FJSVcfmgm/config/manager_discovery_sol_log4j.xm

    <param name="File" value="/var/opt/FJSVcfmgm/logs/cfmgcommand_discovery_sol_trace_log" /> under the element <appender name="cfmgdiscoverytrace" class="org.apache.log4j.RollingFileAppender">

    cfmgcommand_discovery_fjmw_trace_log

    /etc/opt/FJSVcfmgm/config/manager_discovery_fjmw_log4j.xml

    The <param name="File"value="/var/opt/FJSVcfmgm/logs/cfmgcommand_discovery_fjmw_trace_log" /> element under the <appender name="cfmgdiscoverytrace"class="org.apache.log4j.RollingFileAppender"> element

  2. Restart Systemwalker Software Configuration Manager.

4.1.1.4 Event Logs or syslogs

Output format for event logs [Windows]

Source

Description

Systemwalker Software Configuration Manager

Message ID and message content

Output format for syslogs [Linux]

Date/time

Host name

Package name

Description

Jun 11 01:01:01

Server

FJSVcfmgm

Message ID and message content