Fusion Middleware Control Help for WebLogic Server

Domain Partition: JDBC Data Sources

Buttons     Column Display     

A JDBC data source is an object bound to the JNDI tree that provides database connectivity through a pool of JDBC connections. Applications can look up a data source on the JNDI tree and then borrow a database connection from a data source.

This page summarizes the JDBC data source objects that have been created in this domain partition.

Buttons

Name	Description
Create	Creates a new JDBC data source. Select one of the following types: Generic Data Source, GridLink Data Source, UCP Data Source, Proxy Data Source or Multi Data Source.
Create Like	Creates a new JDBC data source similar to one selected in the summary table.
Delete	Deletes the selected data source.

Column Display

You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.

The following table lists all of the data points that you can display in columns on this page.

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 for this Data Source. By default, the JNDI name is the name of the data source. Applications that look up the JNDI path 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.
Type	The type of data source: Generic, GridLink, UCP, Proxy, or Multi Data Source.
Resource Group	The name of the resource group for this JDBC data source.
Tags	Specifies the tags associated with this data source. Tags are used to organize and structure your WebLogic Server configuration by defining contextual relationships between configuration artifacts.
Targets	The server and clusters where the data source is deployed. MBean Attribute: TargetInfoMBean.Targets
Algorithm Type	The algorithm determines the connection request processing for the multi data source. You can specify one of the following algorithm types: Failover Connection requests are sent to the first data source in the list; if the request fails, the request is sent to the next data source in the list, and so forth. The process is repeated until a valid connection is obtained, or until the end of the list is reached, in which case an exception is thrown. Load balancing The multi data source distributes connection requests evenly to its member data sources. With this algorithm, the multi data source also provides failover processing. That is, if a request fails, the multi data source sends the request to the next data source in the list until a valid connection is obtained, or until the end of the list is reached, in which case an exception is thrown. MBean Attribute (Does not apply to application modules) : JDBCDataSourceParamsBean.AlgorithmType 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. This parameter applies only to the deprecated JDBC over RMI. 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. This parameter applies only to the deprecated JDBC over RMI. 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. This parameter applies only to the deprecated JDBC over RMI. 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.