Displaying transaction recovery audit messages
We can choose whether information messages are displayed on the 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.
This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
On distributed platforms the default is for information messages to appear both on the 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 console or in the SystemOut.log file during the recovery of transaction services. These messages displayed we can use the DISABLE_RECOVERY_AUDIT_LOGGING custom property.
On z/OS, if you 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.
- In the console, click Servers > Server Types > WebSphere application servers > server_name > [Container Settings] Container Services > Transaction Service > [Additional Properties] Custom Properties.
- Click New.
- Enter the values required, depending on the operating system:
- To suppress the information messages, type DISABLE_RECOVERY_AUDIT_LOGGING in the Name field, and TRUE in the Value field.
- (zos) To display the information messages, type DISABLE_RECOVERY_AUDIT_LOGGING in the Name field, and FALSE in the Value field.
- Click Apply or OK.
- Save the changes to the master configuration.
- Restart the server in recovery mode.
Related tasks
Restarting an application server in recovery mode (iseries)(dist) Manage transaction logging for optimum server availability
Use High Performance Extensible Logging to troubleshoot applications
Transaction service custom properties