JDBC Data Source: Configuration: General

Applications get a database connection from a data source by looking up the data source on the Java Naming and Directory Interface (JNDI) tree and then requesting a connection. The data source provides the connection to the application from its pool of database connections.

This page enables you to define general configuration options for this JDBC data source.

Configuration Options

Name Description

Name	Description
Name	A unique name that identifies this data source in the WebLogic domain. MBean Attribute (Does not apply to application modules): `JDBCDataSourceBean.Name` Changes take effect after you redeploy the module or restart the server.
JNDI Name	The JNDI path to where this data source is bound. By default, the JNDI name is the name of the data source. To specify multiple JNDI names for the data source, enter each JNDI name on a separate line. Applications that look up the JNDI path will get a `javax.sql.DataSource` instance that corresponds to this data source. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.JNDINames` Changes take effect after you redeploy the module or restart the server.

Name

A unique name that identifies this data source in the WebLogic domain.

MBean Attribute (Does not apply to application modules):
JDBCDataSourceBean.Name

Changes take effect after you redeploy the module or restart the server.

JNDI Name

The JNDI path to where this data source is bound. By default, the JNDI name is the name of the data source.

To specify multiple JNDI names for the data source, enter each JNDI name on a separate line.

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

MBean Attribute (Does not apply to application modules):
JDBCDataSourceParamsBean.JNDINames

Changes take effect after you redeploy the module or restart the server.

Advanced Configuration Options

Name	Description
Supports Global Transactions	Select this option to enable non-XA connections from the data source to participate in global transactions. In most cases, if your application includes global transactions, you should use an XA JDBC driver to create database connections. You may need to enable this option for use with EJBs. If you enable support for global transactions with a non-XA JDBC driver, you must select an option for transaction processing. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.GlobalTransactionsProtocol` Changes take effect after you redeploy the module or restart the server.
Logging Last Resource	Enables a non-XA JDBC connection to participate in distributed transactions using the Logging Last Resource (LLR) transaction optimization. Recommended in place of Emulate Two-Phase Commit. With this option, the transaction branch in which the connection is used is processed as the last resource in the transaction and is processed as a one-phase commit operation. The result of the operation is written in a log file on the resource itself, and the result determines the success or failure of the prepare phase of the transaction. This option offers some performance benefits with greater data safety than Emulate Two-Phase Commit.
Emulate Two-Phase Commit	Enables a non-XA JDBC connection to emulate participation in distributed transactions using JTA. Select this option only if your application can tolerate heuristic conditions. With this option, the transaction branch in which the connection is used always returns success for the prepare phase of the transaction. This option offers performance benefits, but also has risks to data in some failure conditions.
One-Phase Commit	Enables a non-XA JDBC connection to participate in distributed transactions using the one-phase commit transaction processing. With this option, no other resources can participate in the global transaction.
Row Prefetch Enabled	Enables multiple rows to be "prefetched" (that is, sent from the server to the client) in one server access. 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 ignores this setting and does not use row prefetching when the client and WebLogic Server are in the same JVM. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.RowPrefetch` Changes take effect after you redeploy the module or restart the server.
Row Prefetch Size	If row prefetching is enabled, specifies the number of result set rows to prefetch for a client. The optimal prefetch size 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 Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.RowPrefetchSize` Minimum value: `2` Maximum value: `65536` Changes take effect after you redeploy the module or restart the server.
Stream Chunk Size	Specifies the data chunk size for steaming data types. Streaming data types (for example resulting from a call to `getBinaryStream()`) are sent in sized chunks from WebLogic Server to the client as needed. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.StreamChunkSize` Minimum value: `1` Maximum value: `65536` Changes take effect after you redeploy the module or restart the server.