bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JDBC Tx Data Source --> Configuration

Tasks Additional Documentation Attributes

Overview

On the JDBC Tx Data Source—>Configuration tab, you specify attributes for the selected Tx Data Source. Tx Data Source objects, along with the Java Naming and Directory Interface (JNDI), provide access to connection pools for database connectivity. You use Tx Data Sources for connecting to databases in a distributed transaction.

Tasks

Creating and Configuring a Tx Data Source

Cloning a JDBC Tx Data Source

Assigning a Tx Data Source to a Server or Cluster

Deleting a Data Source or Tx Data Source

Additional Documentation

(Requires an Internet connection.)

Managing JDBC Connectivity in the WebLogic Server Administration Guide

Managing Transactions in the WebLogic Server Administration Guide

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Name | The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. MBean: weblogic.management. configuration. JDBCTxDataSourceMBean Attribute: Name | Configurable: yes Readable: yes Writable: yes
JNDI Name | The JNDI path to where this TxDataSource is bound. Applications that look up the JNDI path will get a javax.sql.DataSourceinstance that corresponds to this DataSource. MBean: weblogic.management. configuration. JDBCTxDataSourceMBean Attribute: JNDIName | Configurable: yes Readable: yes Writable: yes
Pool Name | The name of the JDBC connection pool that is associated with this TxDataSource. Calls from applications to getConnection()on this TxDataSource will return a connection from the associated connection pool. MBean: weblogic.management. configuration. JDBCTxDataSourceMBean Attribute: PoolName | Configurable: yes Readable: yes Writable: yes
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. If this TxDataSource 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 Configurable: yes Readable: yes Writable: yes
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 Readable: yes Writable: yes
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 Configurable: yes Readable: yes Writable: yes
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 Configurable: yes Readable: yes Writable: yes