TransactionService

TransactionService

This type is a class for model objects.

Configuration of the transaction service.
Package: applicationserver
Supertype: Service

Classifier ID:  -1
Instance class name:  * Unspecified *
Instance class:  * Unspecified *

Attributes Summary

transactionLogDirectory : EString Specifies the name of a directory for this server where the transaction service stores log files for recovery.

totalTranLifetimeTimeout : EInt The maximum duration, in seconds, for transactions on this application server. Any transaction not requested to complete before this timeout will be rolled back.

clientInactivityTimeout : EInt The maximum duration, in seconds, between transactional requests from a remote client. Any period of client inactivity that exceeds this timeout results in the transaction being rolled back in this application server.

maximumTransactionTimeout : EInt @since 6.0.0 Maximum time, in seconds, for any transactions that execute in the server. This constrains the upper limit of the transaction timeout for all transactions that execute on the server. This value should be greater than or equal to the total transaction timeout which is the default timeout for transactions started on the server. This limit will constrain timeout set programmatically by BMT beans and values imported with contexts received from foreign servers.

heuristicRetryLimit : EInt @since 6.0.0 The number of times the Transaction Manager will retry a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means retry forever. If the retry is abandonned then the resource/partner administrator becomes responsible for ensuring that the resource/partner?s branch is completed appropriately. The Transaction Manager will raise, on the resource/partner?s behalf, an XAException indicating a HeuristicHazard. If a commit was requested, the transaction originator will receive an exception on the commit operation; if the transaction is container-initiated, then the container will return a RemoteException/EJBException to the EJB client.

heuristicRetryWait : EInt @since 6.0.0 The number of seconds the Transaction Manager will wait before retrying a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means that the Transaction Manager will determine the retry wait. The retry wait will be doubled each time there have been 10 failed retries.

waitForCommitOutcome : EBoolean @since 6.0.0 Indicates whether the Transaction Manager should retry commit requests synchronously (true) or asynchronously (false) following a transient exception from a Resource Manager/remote partner. The default value of false (which is the unconfigurable behaviour of WebSphere Application Server 5.x and earlier) means that the retries will be asynchronous and the transaction originator can assume that the commit will succeed. A value of true means that the retries will be synchronous, blocking the processing of the commit request. If the heuristic retry limit is exceeded, then a HeuristicMixed exception will be returned to the transaction originator. If the transaction is container initiated, then the container will return a RemoteException/EJBException to the EJB client.

enableLoggingForHeuristicReporting : EBoolean Enables logging for heuristic reporting (an advanced function available in the EEx add-on package). If applications are configured to allow one-phase resources to participate in two-phase 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 will be perfomed for any transaction that involves both one and two-phase resources. No additional records are written for transactions that do not involve a one-phase resource. Default=false

LPSHeuristicCompletion : LPSHeuristicCompletionKind @since 6.0.0 The heuristic completion action to be taken by the Transaction Service in an LPS transaction when the outcome of the 1PC resource is unknown. (EEx function only) The default behaviour is to rollback the 2PC resources. A setting of MANUAL means the Transaction Service will take no action and leave the 2PC resources in-doubt pending and administrative completion (eg via the Admin Console).

propogatedOrBMTTranLifetimeTimeout : EInt @for zOS only

enableFileLocking : EBoolean Enable NFS file locking

enableProtocolSecurity : EBoolean Enable security on transaction protocol messages

asyncResponseTimeout : EInt Timeout in seconds for responses to WS-AT protocol messages

httpProxyPrefix : EString Prefix of WS-Transaction Proxy for HTTP protocol

httpsProxyPrefix : EString Prefix of WS-Transaction Proxy for HTTPS protocol

wstxURLPrefixSpecified : EBoolean @since 7.0 Flag to indicate whether at URL prefix has been specified for WS-TX endpoints

WSTransactionSpecificationLevel : WSTransactionSpecificationLevel * No description is available *

acceptHeuristicHazard : EBoolean @since 7.0 Indication that LPS is enabled server-wide.

Attribute Details

transactionLogDirectory  -  Specifies the name of a directory for this server where the transaction service stores log files for recovery.
    Data Type: EString
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

totalTranLifetimeTimeout  -  The maximum duration, in seconds, for transactions on this application server. Any transaction not requested to complete before this timeout will be rolled back.
    Data Type: EInt
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

clientInactivityTimeout  -  The maximum duration, in seconds, between transactional requests from a remote client. Any period of client inactivity that exceeds this timeout results in the transaction being rolled back in this application server.
    Data Type: EInt
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

maximumTransactionTimeout  -  @since 6.0.0 Maximum time, in seconds, for any transactions that execute in the server. This constrains the upper limit of the transaction timeout for all transactions that execute on the server. This value should be greater than or equal to the total transaction timeout which is the default timeout for transactions started on the server. This limit will constrain timeout set programmatically by BMT beans and values imported with contexts received from foreign servers.
    Data Type: EInt
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

heuristicRetryLimit  -  @since 6.0.0 The number of times the Transaction Manager will retry a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means retry forever. If the retry is abandonned then the resource/partner administrator becomes responsible for ensuring that the resource/partner?s branch is completed appropriately. The Transaction Manager will raise, on the resource/partner?s behalf, an XAException indicating a HeuristicHazard. If a commit was requested, the transaction originator will receive an exception on the commit operation; if the transaction is container-initiated, then the container will return a RemoteException/EJBException to the EJB client.
    Data Type: EInt
    Default value:  0
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

heuristicRetryWait  -  @since 6.0.0 The number of seconds the Transaction Manager will wait before retrying a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means that the Transaction Manager will determine the retry wait. The retry wait will be doubled each time there have been 10 failed retries.
    Data Type: EInt
    Default value:  0
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

waitForCommitOutcome  -  @since 6.0.0 Indicates whether the Transaction Manager should retry commit requests synchronously (true) or asynchronously (false) following a transient exception from a Resource Manager/remote partner. The default value of false (which is the unconfigurable behaviour of WebSphere Application Server 5.x and earlier) means that the retries will be asynchronous and the transaction originator can assume that the commit will succeed. A value of true means that the retries will be synchronous, blocking the processing of the commit request. If the heuristic retry limit is exceeded, then a HeuristicMixed exception will be returned to the transaction originator. If the transaction is container initiated, then the container will return a RemoteException/EJBException to the EJB client.
    Data Type: EBoolean
    Default value:  false
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

enableLoggingForHeuristicReporting  -  Enables logging for heuristic reporting (an advanced function available in the EEx add-on package). If applications are configured to allow one-phase resources to participate in two-phase 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 will be perfomed for any transaction that involves both one and two-phase resources. No additional records are written for transactions that do not involve a one-phase resource. Default=false
    Data Type: EBoolean
    Default value:  false
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

LPSHeuristicCompletion  -  @since 6.0.0 The heuristic completion action to be taken by the Transaction Service in an LPS transaction when the outcome of the 1PC resource is unknown. (EEx function only) The default behaviour is to rollback the 2PC resources. A setting of MANUAL means the Transaction Service will take no action and leave the 2PC resources in-doubt pending and administrative completion (eg via the Admin Console).
    Data Type: LPSHeuristicCompletionKind
    Default value:  ROLLBACK
    Allowed values:
        0 - ROLLBACK
        1 - COMMIT
        2 - MANUAL
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

propogatedOrBMTTranLifetimeTimeout  -  @for zOS only
    Data Type: EInt
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

enableFileLocking  -  Enable NFS file locking
    Data Type: EBoolean
    Default value:  true
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

enableProtocolSecurity  -  Enable security on transaction protocol messages
    Data Type: EBoolean
    Default value:  true
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

asyncResponseTimeout  -  Timeout in seconds for responses to WS-AT protocol messages
    Data Type: EInt
    Default value:  30
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

httpProxyPrefix  -  Prefix of WS-Transaction Proxy for HTTP protocol
    Data Type: EString
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

httpsProxyPrefix  -  Prefix of WS-Transaction Proxy for HTTPS protocol
    Data Type: EString
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

wstxURLPrefixSpecified  -  @since 7.0 Flag to indicate whether at URL prefix has been specified for WS-TX endpoints
    Data Type: EBoolean
    Default value:  false
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

WSTransactionSpecificationLevel  -  * No description is available *
    Data Type: WSTransactionSpecificationLevel
    Default value:  WSTX_10
    Allowed values:
        0 - WSTX_10
        1 - WSTX_11
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

acceptHeuristicHazard  -  @since 7.0 Indication that LPS is enabled server-wide.
    Data Type: EBoolean
    Default value:  false
    Required:  false
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

(C) COPYRIGHT International Business Machines Corp. 1996-2006

Attributes Summary
transactionLogDirectory : EString	Specifies the name of a directory for this server where the transaction service stores log files for recovery.
totalTranLifetimeTimeout : EInt	The maximum duration, in seconds, for transactions on this application server. Any transaction not requested to complete before this timeout will be rolled back.
clientInactivityTimeout : EInt	The maximum duration, in seconds, between transactional requests from a remote client. Any period of client inactivity that exceeds this timeout results in the transaction being rolled back in this application server.
maximumTransactionTimeout : EInt	@since 6.0.0 Maximum time, in seconds, for any transactions that execute in the server. This constrains the upper limit of the transaction timeout for all transactions that execute on the server. This value should be greater than or equal to the total transaction timeout which is the default timeout for transactions started on the server. This limit will constrain timeout set programmatically by BMT beans and values imported with contexts received from foreign servers.
heuristicRetryLimit : EInt	@since 6.0.0 The number of times the Transaction Manager will retry a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means retry forever. If the retry is abandonned then the resource/partner administrator becomes responsible for ensuring that the resource/partner?s branch is completed appropriately. The Transaction Manager will raise, on the resource/partner?s behalf, an XAException indicating a HeuristicHazard. If a commit was requested, the transaction originator will receive an exception on the commit operation; if the transaction is container-initiated, then the container will return a RemoteException/EJBException to the EJB client.
heuristicRetryWait : EInt	@since 6.0.0 The number of seconds the Transaction Manager will wait before retrying a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means that the Transaction Manager will determine the retry wait. The retry wait will be doubled each time there have been 10 failed retries.
waitForCommitOutcome : EBoolean	@since 6.0.0 Indicates whether the Transaction Manager should retry commit requests synchronously (true) or asynchronously (false) following a transient exception from a Resource Manager/remote partner. The default value of false (which is the unconfigurable behaviour of WebSphere Application Server 5.x and earlier) means that the retries will be asynchronous and the transaction originator can assume that the commit will succeed. A value of true means that the retries will be synchronous, blocking the processing of the commit request. If the heuristic retry limit is exceeded, then a HeuristicMixed exception will be returned to the transaction originator. If the transaction is container initiated, then the container will return a RemoteException/EJBException to the EJB client.
enableLoggingForHeuristicReporting : EBoolean	Enables logging for heuristic reporting (an advanced function available in the EEx add-on package). If applications are configured to allow one-phase resources to participate in two-phase 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 will be perfomed for any transaction that involves both one and two-phase resources. No additional records are written for transactions that do not involve a one-phase resource. Default=false
LPSHeuristicCompletion : LPSHeuristicCompletionKind	@since 6.0.0 The heuristic completion action to be taken by the Transaction Service in an LPS transaction when the outcome of the 1PC resource is unknown. (EEx function only) The default behaviour is to rollback the 2PC resources. A setting of MANUAL means the Transaction Service will take no action and leave the 2PC resources in-doubt pending and administrative completion (eg via the Admin Console).
propogatedOrBMTTranLifetimeTimeout : EInt	@for zOS only
enableFileLocking : EBoolean	Enable NFS file locking
enableProtocolSecurity : EBoolean	Enable security on transaction protocol messages
asyncResponseTimeout : EInt	Timeout in seconds for responses to WS-AT protocol messages
httpProxyPrefix : EString	Prefix of WS-Transaction Proxy for HTTP protocol
httpsProxyPrefix : EString	Prefix of WS-Transaction Proxy for HTTPS protocol
wstxURLPrefixSpecified : EBoolean	@since 7.0 Flag to indicate whether at URL prefix has been specified for WS-TX endpoints
WSTransactionSpecificationLevel : WSTransactionSpecificationLevel	* No description is available *
acceptHeuristicHazard : EBoolean	@since 7.0 Indication that LPS is enabled server-wide.