Technical data

JDBC Configuration Guidelines for Connection Pools, MultiPools and DataSources

Administration Guide 16-23

Only One Non-XA Participant

When a non-XA resource (with enableTwoPhaseCommit = true) is registered with

the WebLogic Server Transaction Manager, it is registered with the name of the class

that implements the XAResource interface. Since all non-XA resources with

enableTwoPhaseCommit = true use the JTS driver for the XAResource interface,

all non-XA resources (with

enableTwoPhaseCommit = true) that participate in a

global transaction are registered with the same name. If you use more than one non-XA

resource in a global transaction, you will see naming conflicts or possible heuristic

failures.

Non-XA Connection Pool and Tx Data Source Configuration Example

The following shows configuration attributes for a sample JDBC Connection Pool

using a non-XA JDBC driver.

Table 16-16 WebLogic jDriver for Oracle: Connection Pool Configuration

Attribute

Name Attribute Value

Name

fundsXferAppPool

Targets

myserver

URL

jdbc:weblogic:oracle

DriverClassname

weblogic.jdbc.oci.Driver

Initial Capacity

MaxCapacity

CapacityIncrement

Properties

user=scott

password=tiger

server=localdb