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
Attributes
Table 129-1
|
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.
JDBCDataSourceMBean
Attribute: Name
|
|
|
JNDI Name
|
The JNDI path to where this DataSource 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.
JDBCDataSourceMBean
Attribute: JNDIName
|
|
|
Pool Name
|
The name of the JDBCConnectionPool to use for this DataSource.
MBean: weblogic.management.
configuration.
JDBCDataSourceMBean
Attribute: JDBCPoolName
|
|
Advanced Attributes
Table 129-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.
JDBCDataSourceMBean
Attribute: RowPrefetchEnabled
|
Default: false
Valid values:
|
|
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.
JDBCDataSourceMBean
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 WebLogic Server to the client as needed.
MBean: weblogic.management.
configuration.
JDBCDataSourceMBean
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
|
