Fusion Middleware Control Help for WebLogic Server

JDBC Data Source: Configuration: General

Configuration Options     

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
Data Source 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.
Type	The type of data source: Generic, GridLink, or Multi Data Source.
Database Type	Select the database management system of your database. The console tailors the list of known JDBC drivers to the DBMS you select and constructs connection properties in a format that the DBMS supports.
Driver Class Name	Select that driver that you want to use to create physical database connections. The data source pools the database connections for use and reuse by your applications. * indicates that the driver is explicitly supported by Oracle WebLogic Server. If your driver is not listed, select "other."
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.
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.