Logging in WebSphere Application Server

Logging can be configured using the WebSphere Application Server administration console. Configuration details vary based on the exact version being used. Refer to the vendor documentation for version specific information.

Java BTM extension logging can be configured by navigating to "TroubleShooting > Logs and Trace" in the WAS administration console. Then navigate to the specific server instance where logging is required, and then to "Diagnostic Trace".

Define a trace specification as required. Full logging can be enabled with the following two specifications:

com.mqsoftware.*=all=enabled:com.bmc.*=all=enabled

Apply the above trace specification for all available logging.

You can use the "Modify" feature in the WAS administration console to define a more precise specification as required.

Components do not appear explicitly in the WAS logging component tree unless already initialized. If a Java BTM extension is not visible in the component tree, then manually enter a trace specification (as above), and apply it. The configuration is applied when the component is first initialized.

Log output is written to the output directory of the WAS server being administered.

  • INFO level logging messages are written to the WAS Server system.out log file.
  • FINE (or higher) level logging messages are written to the WAS Server trace.log file, provided that the trace service is enabled in the WAS Server.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*