Network Deployment (Distributed operating systems), v8.0 > Reference > Custom properties
Transaction service custom properties
WAS allows you to configure a number of custom properties for transaction services.
With WAS v8 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh.
Transaction service custom properties can be specified in the admin console. To use any of these custom properties click on Servers > Server Types > WebSphere application servers > server_name> [Container Settings] Container Services > Transaction Service > [Additional Properties] Custom Properties.
We can define the following transaction service custom properties:
DELAY_CANCELLING_ALARMS
If the before completion stage of a transaction process is likely to include processes that could either take a long time to complete or could fail, then you might want the transaction to time out.
By default, transaction timeout alarms are cancelled prior to the before completion phase of the transaction begins. The DELAY_CANCELLING_ALARMS custom property allows the before completion phase of the transaction to be encompassed within the transaction timeout period.
To do this, set the custom property on the application server.
DELAY_CANCELLING_ALARMS custom properties. The table includes the data type, acceptable values, and default for the property.
Data type Boolean Acceptable values TRUE, FALSE Default FALSE
DISABLE_RECOVERY_AUDIT_LOGGING
We can control whether information messages are displayed on the admin 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.
On distributed platforms the default is for information messages to appear both on the admin console and in the SystemOut.log file during the recovery of transaction services. If you do not want these messages to be displayed you can use the DISABLE_RECOVERY_AUDIT_LOGGING custom property.
DISABLE_RECOVERY_AUDIT_LOGGING custom properties. The table includes the data type, acceptable values, and default for the property.
Data type Boolean Acceptable values TRUE, FALSE Default FALSE
REMOVE_PARTNER_LOG_ENTRY
We can remove entries from the transaction partner log file.
To do this, set the REMOVE_PARTNER_LOG_ENTRY custom property for the transaction service on the server that owns the partner log.
As part of the transaction recovery process, the partner log is checked to establish which resources are needed. To remove certain entries from the partner log, such as a resource that no longer exists, set this custom property on the application server that owns the transaction partner log containing the entries to remove.
The REMOVE_PARTNER_LOG_ENTRY custom property is effective only when both of the following situations apply.
- The application server is started in recovery mode.
- The application server has no transactions that currently require recovery. We can establish this by checking the SystemOut.log file.
REMOVE_PARTNER_LOG_ENTRY custom properties. The table includes the data type, acceptable values, and default for the property.
Data type Integer Acceptable values (one or more comma-delimited integer recovery ID) Default (null)
Display transaction recovery audit messages
Delaying the cancelling of transaction timeout alarms
Remove entries from the transaction partner log
Use HPEL to troubleshoot applications
Use the transaction service