| |
JDBC Multi Data Source: Configuration: 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.
Multi data sources are bound to the JNDI tree. Applications can look up a multi data source on the JNDI tree and then reserve a database connection from a data source. The multi data source manages the connection request and provides a connection from one of its data sources.
Configuration Options
Name Description Name A unique name that identifies this multi data source in the WebLogic domain.
MBean Attribute (Does not apply to application modules) :
JDBCDataSourceBean.NameChanges take effect after you redeploy the module or restart the server.
JNDI Name The JNDI path to where this multi data source is bound.
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.DataSourceinstance that corresponds to this multi data source.MBean Attribute (Does not apply to application modules) :
JDBCDataSourceParamsBean.JNDINamesChanges take effect after you redeploy the module or restart the server.
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.AlgorithmTypeChanges take effect after you redeploy the module or restart the server.
Failover Request if Busy For multi data sources with the
failoveralgorithm, 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.FailoverRequestIfBusyChanges take effect after you redeploy the module or restart the server.
Failover Callback Handler The name of the application class to handle the callback sent when a multi data source is ready to failover or fail back connection requests to another data source within the multi data source.
The name must be the absolute name of an application class that implements the
weblogic.jdbc.extensions.ConnectionPoolFailoverCallbackinterface.MBean Attribute (Does not apply to application modules) :
JDBCDataSourceParamsBean.ConnectionPoolFailoverCallbackHandlerChanges take effect after you redeploy the module or restart the server.
Test Frequency Seconds The number of seconds a WebLogic Server instance waits between attempts when testing 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.TestFrequencySecondsMinimum value:
0Maximum value:
2147483647
|