Administration Console Online Help
|
JDBC Data Source --> Configuration
Tasks Additional Documentation Attributes
Overview
On the JDBC Data Source—>Configuration tab, you specify attributes for the selected Data Source. Data Source objects, along with the Java Naming and Directory Interface (JNDI), provide access to connection pools for database connectivity.
Tasks
Creating and Configuring a JDBC Data Source
Cloning a JDBC Data Source
Assigning a JDBC Data Source to a Server or Cluster
Additional Documentation
(Requires an Internet connection.)
Managing JDBC Connectivity in the WebLogic Server Administration Guide
Configuring WebLogic JDBC Features in Programming WebLogic JDBC
Row Caching with the WebLogic RMI Driver in Programming WebLogic JDBC
Introduction to WebLogic JDBC in Programming WebLogic JDBC
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. JDBCDataSourceMBean
Attribute: Name
|
Configurable: yes
Readable: yes
Writable: yes
|
JNDI Name
|
The JNDI path to where this DataSource is bound.
Applications that look up the JNDI path will get a javax.sql.DataSourceinstance that corresponds to this DataSource.
MBean: weblogic.management. configuration. JDBCDataSourceMBean
Attribute: JNDIName
|
Configurable: yes
Readable: yes
Writable: yes
|
Pool Name
|
The name of the connection pool with which the DataSource is associated.
Calls from applications to getConnection()on this DataSource will return a connection from the associated connection pool.
MBean: weblogic.management. configuration. JDBCDataSourceMBean
Attribute: PoolName
|
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. JDBCDataSourceMBean
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. JDBCDataSourceMBean
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 WebLogic Server to the client as needed.
MBean: weblogic.management. configuration. JDBCDataSourceMBean
Attribute: StreamChunkSize
|
Units: bytes
Minimum: 1
Maximum: 65536
Default: 256
Configurable: yes
Readable: yes
Writable: yes
|