Display transaction recovery audit messages

+

Search Tips   |   Advanced Search

Display transaction recovery audit messages

We can choose whether information messages are displayed on the administrative console and written to the SystemOut.log file upon transaction service recovery. To do this, set the DISABLE_RECOVERY_AUDIT_LOGGING custom property for the transaction service for the server.

IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .

On distributed platforms the default is for information messages to appear both on the administrative console and in the SystemOut.log file during the recovery of transaction services. If we do not want these messages to be displayed we can use the DISABLE_RECOVERY_AUDIT_LOGGING custom property.

(ZOS) On z/OS information messages do not appear by default, either on the administrative console or in the SystemOut.log file during the recovery of transaction services. If we want these messages displayed we can use the DISABLE_RECOVERY_AUDIT_LOGGING custom property.

On z/OS, if we choose to turn on transaction recovery audit messages, other audit messages (such as those relating to servant recovery and XA resource recovery) are also displayed in the console and the SystemOut.log file.


Tasks

  1. In the administrative console, click...

            Servers > Server Types > WebSphere application servers > server > [Container Settings] Container Services > Transaction Service > [Additional Properties] Custom Properties.

  2. Click New.

  3. Enter the values required, depending on the operating system:

    • (iSeries) To suppress the information messages, type DISABLE_RECOVERY_AUDIT_LOGGING in the Name field, and TRUE in the Value field.

    • To display the information messages, type DISABLE_RECOVERY_AUDIT_LOGGING in the Name field, and FALSE in the Value field.

  4. Click Apply or OK.

  5. Save changes to the master configuration.

  6. Restart the server in recovery mode.

  • Restarting an application server in recovery mode
  • Manage transaction logging for optimum server availability
  • Use High Performance Extensible Logging to troubleshoot applications
  • Transaction service custom properties