Transaction service settings
請利用這個頁面來指定交易服務的設定。交易服務是一個伺服器執行時期元件,它能夠協調多個資源管理程式的更新,以確保資料的原子 (atomic) 更新。交易是由應用程式或這些應用程式所部署的儲存器來啟動和結束。
To view this administrative console page, click
.Transaction log directory
指定這部伺服器中交易服務用來儲存復原所用日誌檔的目錄名稱。
Optionally, you can specify the size of transaction log files.
For the z/OS® platform, specifies the location of the JTA Partner Log.
- If the applications use distributed resources or XA transactions; for example, multiple databases and resources are accessed in a single transaction.
- If you configure the system for high availability of transactions. In this situation, the
transaction log directory must be unique for each server in the cluster, and all servers in the
cluster must be able to access the transaction log directory.
In a high availability (HA) environment, both the transaction log and the compensation log directory for each server in a cluster must be unique.
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
If you do not specify this directory during server configuration, the transaction service uses a default directory that is based on the installation directory: app_server_root/ tranlog/cell_ name/node_ name/server_ name.
When an application that runs on the application server accesses more than one resource, the application server stores transaction information in the product directory so that it can coordinate and manage the distributed transaction correctly. When there is a higher transaction load, storing persistent information in this way can slow the performance of the application server because it depends on the operating system and the underlying storage systems. To achieve better performance, designate a new directory for the log files on a separate, physically larger, storage system.
- CPU use remains low despite an increase in transactions
- Transactions fail with several timeouts
- Transaction rollbacks occur with the exception "Unable to enlist transaction"
- The application server stops in the middle of a run and must be restarted
- The disk that the application server is running on shows higher use
- Store log files on a redundant array of independent disks (RAID).
In RAID configurations, the task of writing data to the physical media is shared across the multiple drives. This technique yields more concurrent access to storage for persisting transaction information, and faster access to that data from the logs. Depending on the design of the application and storage subsystem, performance gains can range from 10% to 100%, or more in some cases.
- Do not store log files with the operation system I/O mode set to concurrent I/O (CIO).
When you designate a transaction log directory, ensure that the file system uses only synchronous write-through and write serialization operations. Some operating systems, such as AIX® JFS2, support an optional concurrent I/O (CIO) mode, where the file system does not enforce serialization of write operations. On these systems, do not use CIO mode for application server transaction recovery log files.
To specify the size of transaction log files, include a file size setting. Use one of the following formats, where directory_name is the name of the transaction log directory and file_size is the new disk space allocation for the transaction log files, specified in KB (nK) or MB (nM). The minimum transaction log file size that you can specify is 64K. If you specify a value that is less than 64K, or you do not specify a value for the file size, the default value of 1M is used.
;file_size <!-- This format keeps the default directory -->
directory_name;file_size
dir://directory_name/directory_name;file_size
/directory_name/directory_name;file_size
For more information about transaction log sizes, see Managing transaction logging for optimum server availability.
Information | Value |
---|---|
Data type | String |
Default | Directory name:
app_server_root/tranlog/cell_name/node_name/server_name File size: 1MB |
Recommended | Create a file system with at least three to four disk drives raided together in a RAID-0 configuration. Then, create the transaction log on this file system with the default size. When the server is running under load, check the disk input and output. If disk input and output time is more than 5%, consider adding more physical disks to lower the value. |
![[z/OS]](../images/ngzos.gif)
On z/OS, this log is used for recovery of XA resources. When the application that runs on the WebSphere® product accesses XA resources, the WebSphere product stores information about the resource to enable XA transaction recovery. Use the following syntax:
- location type URL tag specifies the optional location type for the JTA
Partner Log:
- The default is dir://, which specifies that the JTA Partner Log location is in a fully qualified HFS directory specified by location_specification.
- location specification specifies the location name for the JTA Partner Log:
- To specify a logstream, use the syntax logstream://HLQ
If your application server installation followed the convention of configuring logstreams to the coupling facility (CF), the logstream is named according to the syntax HLQ.server.X, where HLQ is a user-defined value between 1-8 characters specified in the installation dialog. Use this HLQ value to specify the JTA Partner Log location.
避免困難: Set AUTODELETE(NO) for any logstreams.gotcha
- If the location type URL tag is dir://, use a fully qualified HFS directory for the location specification. The complete name of the directory must be unique in the WebSphere node.
- To specify a logstream, use the syntax logstream://HLQ
The default is dir://app_server_root/tranlog/server name.
To specify the size of transaction log files, include a file size setting. Use one of the following formats, where directory_name is the name of the transaction log directory and file_size is the new disk space allocation for the transaction log files, specified in KB (nK) or MB (nM). The minimum transaction log file size that you can specify is 64K. If you specify a value that is less than 64K, or you do not specify a value for the file size, the default value of 1M is used.
dir://directory_name/directory_name;file_sizeK
/directory_name/directory_name;file_sizeK
;file_sizeK <!-- This keeps the default directory -->
Total transaction lifetime timeout
在交易服務起始逾時完成之前,在這部伺服器上啟動之交易所容許的預設最長時間(秒)。 任何交易,只要未在這項逾時之前起始完成處理程序,都會加以回復。
This timeout is used only if the application component does not set its own transaction timeout.
![[z/OS]](../images/ngzos.gif)
The upper limit of this timeout is constrained by the maximum transaction timeout. For example, if you set a value of 500 for the total transaction lifetime timeout, and a value of 300 for the maximum transaction timeout, transactions will time out after 300 seconds.
If you set this timeout to 0, the timeout does not apply and the value of the maximum transaction timeout is used instead.
Information | Value |
---|---|
Data type | Integer |
Units | Seconds |
Default | 120 |
![]() ![]() |
![]() ![]()
|
![]() |
![]()
|
Asynchronous response timeout
指定伺服器在重傳前一個「Web 服務原子交易 (WS-AT)」通訊協定訊息前,等待入埠 WS-AT 通訊協定回應的時間量(秒)。
Information | Value |
---|---|
Data type | Integer |
Units | Seconds |
Default | 30 |
Range | 0 to 2 147 483 647 |
Client inactivity timeout
指定遠端用戶端發出的交易要求之間的持續時間上限(秒)。用戶端不作用超出這個逾時值的任何期間,都會在這個應用程式伺服器中造成交易的回復。
If you set this value to 0, there is no timeout limit.
Information | Value |
---|---|
Data type | Integer |
Units | Seconds |
Default | 60 |
Range | 0 to 2 147 483 647 |
Maximum transaction timeout
指定在這部伺服器中所執行交易的交易逾時上限(秒)。這個值應該大於或等於所指定的總交易逾時值。Specifies the maximum time to complete, in seconds, for transactions that run in this server. This value should be greater than or equal to the total transaction lifetime timeout AND greater than or equal to the application component timeout. If the maximum transaction timeout is set to a value less than either the total transaction lifetime timeout or the application component timeout, application component transactions that may require more time will timeout when the maximum transaction timeout is reached.
This timeout constrains the upper limit of all other transaction timeout periods.
Timeout setting | Transactions affected |
---|---|
Maximum transaction timeout | All transactions running in this server that are not affected by the total transaction lifetime timeout or an application component timeout. These transactions include transactions imported from outside this server, such as those imported from a client. |
Total transaction lifetime timeout | All transactions that originated in this server that are not affected by an application component timeout, in other words, the associated application component does not set its own timeout. |
Application component timeout | Transactions that are specific to an application component.
You cannot set this transaction timeout using the administrative console. If the component is a container-managed bean, set this timeout in the deployment descriptor for the component. For example, you can use an assembly tool, such as the Rational® Application Developer. If the component is a bean-managed bean, set this timeout programmatically by using the UserTransaction.setTransactionTimeout method. |
If you set a timeout to 0, that timeout does not apply, and is effectively disabled. If you set all timeouts to 0, transactions never time out.
Timeout setting | Value |
---|---|
Maximum transaction timeout | 360 |
Total transaction lifetime timeout | 240 |
Application component timeout | 60 |
To determine the occurrence of a timeout quickly, and to prevent further resource locking, the application server prevents further transactional work on the transactional path where the timeout condition has taken place. This applies equally to attempting to undertake work under the current transaction context and to attempting to perform work under a different transactional context.
Information | Value |
---|---|
Data type | Integer |
Units | Seconds |
Default | 300 |
![]() ![]() |
![]() ![]() ![]() ![]() |
![]() |
![]() ![]() |
Heuristic retry limit
指定應用程式伺服器重試完成信號(如:確定或回復)的次數。若有下列情況,即會進行重試:當資源管理程式或遠端友機發出暫時性異常狀況後,或者在所有「Web 服務原子交易 (WS-AT)」友機做出回應前,即過了所配置的非同步回應逾時時間。
If the application server abandons the retries, the resource manager or remote partner is responsible for ensuring that the resource or partner branch of the transaction is completed appropriately. The application server raises (on behalf of the resource or partner) an exception that indicates a heuristic hazard. If a commit request was made, the transaction originator receives an exception on the commit operation; if the transaction is container-initiated, the container returns a remote exception or Enterprise JavaBeans (EJB) exception to the EJB client.
During recovery of a subordinate server in a distributed transaction, when the number of heuristic retries is exceeded, the heuristic completion direction property specifies how the transaction is completed.
Information | Value |
---|---|
Data type | Integer |
Default | 0 |
Range | 0 to 2 147 483 647 A value of 0 (the default) means try again indefinitely. |
Heuristic retry wait
指定在資源管理程式或遠端友機擲出暫時性異常狀況之後,應用程式伺服器要等待幾秒,才能重新發出確定或回復等完成信號。
Information | Value |
---|---|
Data type | Integer |
Default | 0 |
Range | 0 to 2 147 483 647
|
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
Enable logging for heuristic reporting
指定對於同時涉及一段式確定資源和兩段式確定資源的交易所發出的「即將確定一段式資源」事件,應用程式伺服器是否要加以記載。
This property enables logging for heuristic reporting. If applications are configured to allow one-phase commit resources to participate in two-phase commit transactions, reporting of heuristic outcomes that occur at application server failure requires extra information to be written to the transaction log. If enabled, one additional log write is performed for any transaction that involves both one-phase and two-phase commit resources. No additional records are written for transactions that do not involve a one-phase commit resource.
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
Information | Value |
---|---|
Data type | Check box |
Default | Cleared |
Range |
|
Heuristic completion direction
指定用來完成具有探索式輸出之交易的方向;一種是由應用程式伺服器確定或回復交易,另一種是依靠管理者手動完成。
- The transaction manager reports a heuristic outcome for a last participant support (LPS) resource.
- The heuristic retry limit is exceeded during the recovery of a subordinate server in a distributed transaction.
- The transaction is imported from a Java EE Connector Architecture (JCA) provider.
This property applies only to transactions that are in the situations just described.
Information | Value |
---|---|
Data type | Drop-down list |
Default | ROLLBACK |
Range |
|
Accept heuristic hazard
指定這個伺服器上的所有應用程式是否接受內含一段式資源的兩段式交易中可能發生的探索性風險。 This setting configures last participant support (LPS) for the server. Last participant support is an extension to the transaction service that enables a single one-phase resource to participate in a two-phase transaction with one or more two-phase resources.
If the Accept heuristic hazard option is not selected, you must configure applications individually to accept the heuristic hazard. You can configure applications either when they are assembled, or following deployment by using the Last participant support extension pane.
Information | Value |
---|---|
Data type | Check box |
Default | Cleared |
Range |
|
Enable file locking
指定在開啟交易服務回復日誌時,是否啟用檔案鎖定。
Information | Value |
---|---|
Data type | Check box |
Default | Selected |
Enable transaction coordination authorization
指定是否啟用交易服務通訊協定訊息的安全交換。
When transaction coordination authorization is enabled, the transaction service verifies the caller is permitted to the administrator role before handling the transaction.
This setting has no effect unless you enable WebSphere Application Server security on the server.
Information | Value |
---|---|
Data type | Check box |
Default | Selected |
Default WS-Transaction specification level
Specifies the default WS-Transaction specification level to use for outbound requests that include a Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) coordination context.
You can choose from WS-Transaction 1.0, WS-Transaction 1.1 or WS-Transaction 1.2. For details of these specifications, see the topics about WS-AT support or WS-BA support in the application server.
The default WS-Transaction specification level is used if a level cannot be determined from the provider policy (the WS-Transaction WS-Policy assertion). This could be, for example, if the policy assertion is not available either from the WSDL of the target web service or from the WS-Transaction policy type of the client, or if the policy assertion is available but more than one specification level is applicable.
Information | Value |
---|---|
Data type | Drop-down list |
Default | 1.0 |
External WS-Transaction HTTP(S) URL prefix
選取或指定外部 WS-Transaction HTTP(S) URL 字首。
- If you are using an intermediary node, such as an HTTP server or Proxy Server for WebSphere, to send requests that comply with the Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) protocols.
- If you want to configure WS-Transaction EndpointReferences to be published with non-default protocol,host or port values in their URLs. For example, when configuring inbound WS-Transaction protocol requests to flow into the application server via a forward proxy, such as the WebSphere Proxy Server, use this field to specify an SSL channel chain when global security is not enabled, or to specify a non-SSL channel when global security is enabled.
If either a specified custom prefix or a selected prefix is configured, that prefix is used. If a specified custom or selected prefix is not set, then, by default, if security is enabled, one of the application server's SSL enabled web container channel chains is automatically selected. Otherwise, a non-SSL enabled web container channel chain is automatically selected.

If the intermediary node is not a Proxy Server, the prefix must be unique for each server.
If you are using a Proxy Server, prefixes can be the same for each server in a cluster, because the Proxy Server determines dynamically which server to forward the request to.
Select prefix
Select this option to select the external endpoint URL information to use for WS-AT and WS-BA service endpoints from the list.
Information | Value |
---|---|
Data type | Drop-down list |
Default | None |
Specify custom prefix
Select this option to specify the external endpoint URL information to use for WS-AT and WS-BA service endpoints in the field.
http://host_name:port
https://host_name:port
Information | Value |
---|---|
Data type | String |
Default | None |
Manual transactions
指定等待管理者手動完成的交易數目。
If there are transactions awaiting manual completion, you can click the Review link to display a list of those transactions on the Transactions needing manual completion panel.
Information | Value |
---|---|
Data type | Integer |
Default | 0 |
Retry transactions
指定有某些資源要重試的交易數目。
If there are transactions with resources being retried, you can click the Review link to display a list of those transactions on the Transactions retrying resources panel.
Information | Value |
---|---|
Data type | Integer |
Default | 0 |
Heuristic transactions
指定已依經驗完成的交易數目。
If there are transactions that have completed heuristically, you can click the Review link to display a list of those transactions on the Transactions with heuristic outcome panel.
Information | Value |
---|---|
Data type | Integer |
Default | 0 |
Imported prepared transactions
指定已匯入並備妥、但尚未確定的交易數目。
If there are transactions that have been imported and prepared but not yet committed, you can click the Review link to display a list of those transactions on the Transactions imported and prepared panel.
Information | Value |
---|---|
Data type | Integer |
Default | 0 |
Additional Properties
Under Additional Properties you can click the Custom properties link to display or change custom properties for your WebSphere Application Server transaction service.
You use Custom properties to specify whether information messages are displayed on the administrative console and written to the SystemOut.log file upon transaction service recovery.
To find out more about WebSphere Application Server transaction service custom properties, see the related link.