Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JDBC Data Source --> Configuration

Tasks Related Topics Attributes

## Overview

On the JDBC Data Source—>Configuration tab, you specify attributes for the selected Data Source. Applications get a database connection from a connection pool by looking up a data source on the Java Naming and Directory Interface (JNDI) tree nd then request a connection. The connection pool associated with the datasource provides the connection to the application.

## Tasks

Creating and Configuring a JDBC Data Source

Cloning a JDBC Data Source

Deploying a JDBC Data Source to a Server or Cluster

## Related Topics

Configuring JDBC DataSources

Creating and Deploying JDBC Components—Connection Pools, MultiPools, and Data Sources

Monitoring Transactions

## Attributes

Table 136-1

Attribute Label | Description | Value Constraints
--- | --- | ---
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. Note: If you are binding JDBC to multiple JNDI names, the default separator is a semicolon ( ; ). If you want to use a semicolon as part of the JNDI name, designate another character as a separator by specifying the`JNDINameSeparator` property for the datasource in the `config.xml` file (e.g., `JNDINameSeparator=".."`) MBean: `weblogic.management. configuration. JDBCTxDataSourceMBean` Attribute: `JNDIName` |

#### Advanced Attributes

Table 136-2

Attribute Label | Description | Value Constraints
--- | --- | ---
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 data types. Streaming data types (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
Honor Global Transactions | Specifies whether the data source can participate in a global transaction. When selected, the data source is created as a TxDataSource in the `config.xml` file. You select this option (the default) when creating the data source. You cannot change this setting after the data source is created. | Default: true
Emulate Two-Phase Commit for non-XA Driver | When set to true, this attribute allows a non-XA JDBC driver 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. Note: This option is only available when Honor Global Transactions is selected. MBean: `weblogic.management. configuration. JDBCTxDataSourceMBean` Attribute: `EnableTwoPhaseCommit` | Default: false Valid values: true false