Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Deployments: JDBC Module: Configuration: JDBC Multi Data Source: General

Configuration Options Related Tasks Related Topics

Use this page to define the general configuration for this JDBC multi data source. A JDBC multi data source is an abstraction around a group of data sources that provides load balancing and failover between data sources.

#### Configuration Options

Name | Description
--- | ---
Name | A name that identifies this multi data source in the application. The name must be unique among all data sources and multi data sources packaged with the application or deployed as stand-alone modules. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.Name` Changes take effect after you redeploy the module or restart the server.
JNDI Name | The path to where this multi data source is bound, either on the global JNDI tree or in the local environment. By default, the JNDI name is the name of the multi data source. To specify multiple JNDI names for the multi 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 multi data source. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.JNDINames` Changes take effect after you redeploy the module or restart the server.
Algorithm Type | The algorithm type for this JDBC multi data source. Failover means that connection requests are sent to the first connection pool in the list; if the request fails, the request is sent to the next connection pool in the list, and so forth. Load-Balancing means that the multi data source will distribute the connection requests evenly to its member data sources. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.AlgorithmType` Changes take effect after you redeploy the module or restart the server.
Failover Request if Busy | For multi data sources with the failover algorithm, enables the multi data source to failover connection requests to the next data source if all connections in the current data source are in use. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.FailOverRequestIfBusy` Changes take effect after you redeploy the module or restart the server.
Connection Pool Failover Callback Handler | The absolute name of the application class that implements the interface weblogic.jdbc.application.extensions.ConnectionPoolFailoverCallback. MBean Attribute (Does not apply to application modules): `JDBCDataSourceParamsBean.ConnectionPoolFailoverCallbackHandler` Changes take effect after you redeploy the module or restart the server.
Test Frequency Seconds | The number of seconds between when WebLogic Server tests unused connections. (Requires that you specify a Test Table Name.) Connections that fail the test are closed and reopened to re-establish a valid physical connection. If the test fails again, the connection is closed. In the context of multi data sources, this attribute controls the frequency at which WebLogic Server checks the health of data sources it had previously marked as unhealthy. When set to `0`, the feature is disabled. MBean Attribute (Does not apply to application modules): `JDBCConnectionPoolParamsBean.TestFrequencySeconds` Minimum value: `0` Maximum value: `2147483647`

Related Tasks

- Create JDBC multi data sources
- Delete JDBC multi data sources
- Register a failover callback handler

Related Topics

- Packaged JDBC Modules
- Configuring JDBC Multi Data Sources
- Configuring and Deploying WebLogic JDBC Resources