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-7
Configuring the JDBC Connection Pools for SQL/MX
KeepXAConnTillTxComplete
Tells the WebLogic Server not to close the connection until the global transaction
is complete. This attribute must be set in the JDBCConnectionPool for the
WebLogic Server to invoke the setTransactionIsolation method.
When generating primary keys using a named sequence table, the WebLogic
Server sets the transaction isolation level on the JDBC connection to
TRANSACTION_SERIALIZABLE. To change the transaction isolation level, the
WebLogic Server must be instructed to keep the connection until the transaction is
complete. This implies that all requests to acquire a connection from a specific
JDBCConnectionPool for a given transaction will return the same connection
object.
RollbackLocalTxUponConnClose
If set to true, the connection pool calls rollback() on the connection before
putting it back in the pool. Enabling this attribute impacts performance because the
rollback call requires communication with the database server.
The NonStop SQL/MX JDBC/MX driver requires that local transactions be ended
before enlisting a connection in a global transaction; therefore, you must set
RollbackLocalTxUponConnClose to true.
SupportsLocalTransaction
Applies only to the JDBC/MX connection pools. The JDBC/MX driver can
determine if it was called within the context of an external transaction (in the case
of the WebLogic Server, a transaction that was imported into TMF as a branch of a
WebLogic Server global transaction). If so, it defers transaction management to the
application managing the transaction. Otherwise, the JDBC driver manages the
transactions by itself. This flag tells the WebLogic Server that the JDBC driver has
the ability to do JDBC work even without a WebLogic Server transaction in
progress and is used in some sample applications used by the WebLogic Server
(including repopulating the MedRec database).
URL
Designates different database instances so that the JDBC driver can determine
whether it can open the database based on the URL provided. The JDBC driver
should be able to parse the URL and make a connection to the database. Unlike
the driver name, the JDBC URL does not change between non-XA and XA drivers.
The JDBC URL is: jdbc:sqlmx: