Name

The name of this JDBC data source. This name is used to represent the JDBC data source in the Administration Console and in the configuration file (config.xml). Applications looking to request a connection do not use this name to look up the data source. Instead, they use the JNDI name.

MBean: weblogic.management.
configuration.
JDBCTxDataSourceMBean

Attribute: Name

JNDI Name

The JNDI path to where this TxDataSource is bound.

Applications that look up the JNDI path will get a javax.sql.DataSource instance that corresponds to this DataSource.

MBean: weblogic.management.
configuration.
JDBCTxDataSourceMBean

Attribute: JNDIName

Emulate Two-Phase Commit for non-XA Driver

When set to true, this attribute allows non-XA JDBC drivers to emulate participation in distributed transactions using JTA.

Use this option if the JDBC connection is the only participant in the transaction and there is no XA compliant JDBC driver available. With more than one resource participating in a transaction where one of them (the JDBC driver) is emulating an XA resource, you may see heuristic failures. See Emulating Two-Phase Commit.

If this DataSource is associated with an XA connection pool, or if there is only one resource participating in the distributed transaction, then this setting is ignored.

MBean: weblogic.management.
configuration.
JDBCTxDataSourceMBean

Attribute: EnableTwoPhaseCommit

Default: false

Valid values:

• true

• false

Row Prefetch Enabled

Controls row prefetching between a client and WebLogic Server for each ResultSet. When an external client accesses a database using JDBC through Weblogic Server, row prefetching improves performance by fetching multiple rows from the server to the client in one server access. WebLogic Server will ignore this setting and not use row prefetching when the client and WebLogic Server are in the same JVM.

MBean: weblogic.management.
configuration.
JDBCTxDataSourceMBean

Attribute: RowPrefetchEnabled

Default: false

Valid values:

• true

• false

Row Prefetch Size

The number of result set rows to prefetch for a client. The optimal value depends on the particulars of the query. In general, increasing this number will increase performance, until a particular value is reached. At that point further increases do not result in any significant performance increase. Very rarely will increased performance result from exceeding 100 rows. The default value should be reasonable for most situations.

MBean: weblogic.management.
configuration.
JDBCTxDataSourceMBean

Attribute: RowPrefetchSize

Minimum: 2

Maximum: 65536

Default: 48

Stream Chunk Size

Data chunk size for steaming datatypes. Streaming datatypes (for example resulting from a call to getBinaryStream()) will be pulled in StreamChunkSize sized chunks from the WebLogic Server to the client as needed.

MBean: weblogic.management.
configuration.
JDBCTxDataSourceMBean

Attribute: StreamChunkSize

Units: bytes

Minimum: 1

Maximum: 65536

Default: 256