The CA RCM Support Tools feature assists administrators, system integrators, MSP administrators, tenant administrators, and tenant partner administrators to control collected information that is written to the Application Server log file. This user-set system logging information helps trace and debug CA RCM log files.
CA RCM Support Tools configures the log4j logging framework at runtime. Log4j is a package that produces log statements to various output targets. Log statements can remain in the shipped code without incurring a heavy performance cost. You control and configure logging behavior at runtime.
The concept of logger inheritance is a distinctive log4j feature. Logger inheritance enables you to control which log statements are produced at a user-determined detail level. This feature helps reduce logging output volume and minimize logging cost.
The CA RCM Support Tools feature is located under Administration, Support Tools.
The Info Collection feature enables you to select specific CA RCM system information and export it as a file. This feature assists the CA RCM support and sustaining teams to collect critical system information. This feature is also useful in analyzing system performance.
The Info Collection files provide a current technical view, which is an important debugging tool.
Select from the following CA RCM Info Collection options:
- Current Log File
- Historical Log Files
- Common Properties
- Operating System Properties
- Hardware Information
- Jboss Versions
- Workpoint processes
The following table lists the Info Collection file names, provides a description, and lists the file types the Info Collection feature generates:
|Current Log File||The application server log file.||eurekify.log|
|Historical Log Files||The application server historical log files.||RCM.History.Logs<Java time stamp>.zip|
|Properties||CA RCM properties information in the current system.||RCM.properties|
|Common Properties||CA RCM common properties information in the current system.||RCM_Common.properties|
|Versions||CA RCM versions information in the current system.||RCM_Versions.properties|
|Operating System Properties||CA RCM system information pertaining to the current system.||System.properties|
|Hardware Information||CA RCM system hardware information pertaining to the current system.||hardwareInfo.properties|
|JBoss Versions||JBoss system information in the current system.||jboss_versions.properties|
|Workpoint Processes||A compressed file that is composed of XML files that define Workpoint processes pertaining to the current system.||workpointProcesses.zip|
|Download All||A compressed file composed of all the Information Collection options.||RCM.Data.<year><IP address>.zip|
The Log Settings option enables administrators, system integrators, MSP administrators, tenant administrators, and tenant partner administrators to collect specific CA RCM information. Logging provides precise context about a CA RCM system. You can filter Java Packages and Classes by name or debug level. You can also set the debug level for a specific Java Package or Class.
The following table lists the user set log levels and provides a brief description:
|ALL||All levels including custom levels.|
|DEBUG||Designates specific informational events that are most useful for debugging purposes.|
|ERROR||Lists error events that enable CA RCM to continue running.|
|FATAL||Lists severe error events that can lead CA RCM to abort.|
|INFO||Lists informational messages that highlight the CA RCM progress at the overall level.|
|OFF||The highest possible rank. Turns off logging feature.|
|TRACE||Lists finer-tuned informational events then those of the DEBUG log setting events.|
|WARN||Lists potentially harmful situations.|
Note: These Log settings are reset to default status when the server is reset or restarted.