NonStop Server Guide for BEA WebLogic Server 8.1

XA Resource Manager (XARM)
HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001
6-5
Configuring the JDBC Connection Pools for SQL/MX
Configuring the JDBC Connection Pools for
SQL/MX
The JDBC/MX driver does not support the optional XA support specified in the JDBC
specification because there is no need for the XA interfaces in the NonStop platform.
However, the WebLogic Server and other J2EE containers depend on data sources to
provide the XA resource for coordinating the participation of these resources in global
transactions.
The WebLogic Server can optionally provide an XA emulation driver for a non-XA
resource. However, only one resource with WebLogic Servers-provided XA emulation
can take part in a distributed transaction. Furthermore, using the WebLogic server-
provided XA resource can result in more heuristic completions. To take part in a
distributed transaction without depending on the WebLogic Server-provided XA
emulation, the resource manager should be XA-aware. An XA resource interface for
NonStop server resources does not have to do transaction management when used
with the WebLogic Server because the static resource manager handles the
transaction management and is enlisted in all WebLogic Server transactions.
maxthreads hp.nsk.xares.maxthreads Specifies the maximum number of threads
that can concurrently take part in a
transaction. Typically, set to the maximum
number of transactions configured so that
the case where each thread operates on
only one transaction is allowed for. Valid
values are 100 and higher. Default value is
1000.
enabletrace hp.nsk.xares.enabletrace Enables or disables tracing of the XA
operations by the XA resource manager.
Valid values are true and false. Default
value is false.
tracefile hp.nsk.xares.tracefile Specifies that the file cannot be opened and
trace output is redirected to System.err
destination. Valid value is null or a valid
path to a file. Default value is null. If set to
null, tracing is disabled.
auditfile hp.nsk.xares.auditfile If auditing is enabled in the flags, this file is
used as the audit file. If the filename is null
or invalid and auditing is enabled in the
flags, an audit file with the name
xaaudit-date+time.txt is created for
audit messages.
Table 6-1. Java System Properties Used by WLSNonStopTxHelper (continued)
Property Name
Used in
Property File
Name when Specified
with the -D Java
Command Line Option Description