BMC Remedy Approval Server logging
To verify that the approval server is running or to audit its activities, you can turn on logging as described in Configuring settings on the Basic tab. After you provide the log file name and location and save the server settings, the approval server begins logging events. The first entry in the log file is:
<APPR> Approval Server Trace Log -- ON <timeStamp>
If you call BMC Support, have a copy of this log available for faster resolution. Logging is not set ON by default.
Information added to the logs at the minimum logging level (NORMAL) also appears in logs that are configured for the maximum level (ALL). The higher levels provide more detailed information.
The minimum logging level for the BMC Remedy Approval Server is NORMAL (or INFO). When you set this logging level, only severe issues are written to the logs.
ALL (or DEBUG) is the highest logging level for the BMC Remedy Approval Server. These logs can be used to help trace issues in the process flow.
Structure of logs
The structure of the approval server logs depends on whether BMC Remedy Approval Server was configured with the default plug-in server or a separate plug-in server.
Default plug-in server:
When approval server is configured using the default plug-in server, the following log files are created:
Stores information about all exceptions in the approval server as well as the Java plug-in. It also logs all error messages.
Stores information about the initialization logs for the Java plug-in
Stores information about the initialization logs for all the plug-ins loaded in the default plug-in
Separate plug-in server:
When approval server is configured using a separate plug-in server, the following log files are created:
Stores information about all exceptions for the approval server plug-in
Stores information about the initialization logs for the approval plug-in
Stores information about the initialization logs when approval server is loaded in the Java plug-in