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-6
Configuring the JDBC Connection Pools for SQL/MX
A wrapper driver has been written for JDBC/MX. The wrapper driver does not do
transaction management, but implements the XA interface. The XA resource
implemented by JDBC/MX responds with XA_RDONLY, implying that no change was
done to the underlying resource. The static XA resource manager protects changes to
resources managed by JDBC/MX.
Returning XA_RDONLY tells the WebLogic Server transaction manager to ignore the
resource in the second phase of commit processing. If all the resources accessed with
a WebLogic Server transaction are JDBC/MX resources pools, the WebLogic Server
transaction manager does not write a transaction log during the commit processing.
This provides better performance and reliability as the transaction log is protected with
TMF audit trails.
The following is a sample configuration element for the JDBCConnectionPool using
the wrapper drivers. Note that the JDBC URL does not change from the underlying
JDBC driver that is being wrapped.
<JDBCConnectionPool
CapacityIncrement=”1”
DriverName=”DriverName”
InitialCapacity=”1”
MaxCapacity=”10”
Name=”PoolName”
RefreshMinutes=”0”
ShrinkPeriodMinutes=”15”
ShrinkingEnabled=”true”
Targets=”examplesServer”
TestConnectionsOnRelease=”false”
KeepXAConnTillTxComplete=”true”
TestConnectionsOnReserve=”false”
RollbackLocalTxUponConnClose=”true”
SupportsLocalTransaction=”true”
URL=”JDBCUrl”
/>
DriverName
Specifies the JDBC driver associated with the Pool. It can be the name of the class
for the Type 2 JDBC driver or the XA DataSource driver.
•
The Type 2 driver name is com.tandem.sqlmx.SQLMXDriver
•
The XA DataSource driver name is
com.hp.nsk.xares.WLSTxSQLMXDataSource
Name
The name of the connection pool that is used when referencing the connection
pool when configuring the data sources. PoolName is also used by the WebLogic
Server Mbeans management infrastructure.