The following sections describe WebLogic JDBC resources, how they are configured, and how those resources apply to a WebLogic domain:
In WebLogic Server, you can configure database connectivity by configuring JDBC data sources and multi data sources and then targeting or deploying the JDBC resources to servers or clusters in your WebLogic domain.
Each data source that you configure contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications lookup a data source on the JNDI tree or in the local application context (
java:comp/env), depending on how you configure and deploy the object, and then request a database connection. When finished with the connection, the application calls
connection.close(), which returns the connection to the connection pool in the data source.
Figure 2-1 shows a data source and a multi data source targeted to a WebLogic Server instance.
For more information about data sources in WebLogic Server, see Configuring JDBC Data Sources.
A multi data source is an abstraction around a data sources that provides load balancing or failover processing between the data sources associated with the multi data source. Multi data sources are bound to the JNDI tree or local application context just like data sources are bound to the JNDI tree. Applications lookup a multi data source on the JNDI tree or in the local application context (
java:comp/env) just like they do for data sources, and then request a database connection. The multi data source determines which data source to use to satisfy the request depending on the algorithm selected in the multi data source configuration: load balancing or failover. For more information about multi data sources, see Configuring JDBC Multi Data Sources.
A key to understanding WebLogic JDBC configuration and management is that who creates a JDBC resource or how a JDBC resource is created determines how a resource is deployed and modified. Both WebLogic Administrators and programmers can create JDBC resources:
Table 2-1 lists the JDBC module types and how they can be configured and modified.
WebLogic JDBC configuration is stored in XML documents that conform to the
weblogic-jdbc.xsd schema (available at http://www.bea.com/ns/weblogic/920/weblogic-jdbc.xsd). You create and manage JDBC resources either as system modules or as application modules. JDBC application modules are a WebLogic-specific extension of Java EE modules and can be configured either within a Java EE application or as stand-alone modules.
Regardless of whether you are using JDBC system modules or JDBC application modules, each JDBC data source or multi data source is represented by an XML file (a module).
When you create a JDBC resource (data source or multi data source) using the Administration Console or using the WebLogic Scripting Tool (WLST), WebLogic Server creates a JDBC module in the
config/jdbc subdirectory of the domain directory, and adds a reference to the module in the domain’s
config.xml file. The JDBC module conforms to the
weblogic-jdbc.xsd schema (available at http://www.bea.com/ns/weblogic/920/weblogic-jdbc.xsd).
JDBC resources that you configure this way are considered system modules. System modules are owned by an Administrator, who can delete, modify, or add similar resources at any time. System modules are globally available for targeting to servers and clusters configured in the domain, and therefore are available to all applications deployed on the same targets and to client applications. System modules are also accessible through JMX as
Data source system modules are included in the domain’s
config.xml file as a
JDBCSystemResource element, which includes the name of the JDBC module file and the list of target servers and clusters on which the module is deployed. Figure 2-2 shows an example of a data source listing in a
config.xml file and the module that it maps to.
In this illustration, the
config.xml file lists the
examples-demo data source as a
jdbc-system-resource element, which maps to the
examples-demo.xml module in the
Similarly, multi data source system modules are included in the domain’s
config.xml file as a
jdbc-system-resource element. The multi data source module includes a
data-source-list parameter that maps to the data source modules used by the multi data source. The individual data source modules are also included in the
config.xml. Figure 2-3 shows the relationship between elements in the
config.xml file and the system modules in the
In this illustration, the
config.xml file lists three JDBC modules—one multi data source and the two data sources used by the multi data source, which are also listed within the multi data source module. Your application can look up any of these modules on the JNDI tree and request a database connection. If you look up the multi data source, the multi data source determines which of the other data sources to use to supply the database connection, depending on the data sources in the
data-source-list parameter, the order in which the data sources are listed, and the algorithm specified in the
algorithm-type parameter. For more information about multi data sources, see Configuring JDBC Multi Data Sources.
JDBC resources can also be managed as application modules, similar to standard Java EE modules. A JDBC application module is simply an XML file that conforms to the
weblogic-jdbc.xsd schema and represents a data source or a multi data source.
JDBC modules can be included as part of an Enterprise Application as a packaged module. Packaged modules are bundled with an EAR or exploded EAR directory, and are referenced in all appropriate deployment descriptors, such as the
ejb-jar.xml deployment descriptors. The JDBC module is deployed along with the enterprise application, and can be configured to be available only to the enclosing application or to all applications. Using packaged modules ensures that an application always has access to required resources and simplifies the process of moving the application into new environments. With packaged JDBC modules, you can migrate your application and the required JDBC configuration from environment to environment, such as from a testing environment to a production environment, without opening an EAR file and without extensive manual JDBC reconfiguration.
In contrast to system resource modules, JDBC modules that are packaged with an application are owned by the developer who created and packaged the module, rather than the Administrator who deploys the module. This means that the Administrator has more limited control over packaged modules. When deploying a resource module, an Administrator can change resource properties that were specified in the module, but the Administrator cannot add or delete modules. (As with other Java EE modules, deployment configuration changes for a resource module are stored in a deployment plan for the module, leaving the original module untouched.)
By definition, packaged JDBC modules are included in an enterprise application, and therefore are deployed when you deploy the enterprise application. For more information about deploying applications with packaged JDBC modules, see Deploying Applications to WebLogic Server.
A JDBC application module can also be deployed as a stand-alone resource using the
weblogic.Deployer utility or the Administration Console, in which case the resource is typically available to the server or cluster targeted during the deployment process. JDBC resources deployed in this manner are called stand-alone modules and can be reconfigured using the Administration Console or a JSR-88 compliant tool, but are unavailable through JMX or WLST.
Stand-alone JDBC modules promote sharing and portability of JDBC resources. You can create a data source configuration and distribute it to other developers. Stand-alone JDBC modules can also be used to move JDBC configuration between domains, such as between the development domain and the staging domain.
|Note:||When deploying JDBC modules as standalone modules, a multi-datasource needs to have a deployment order that is greater than its member databasources deployment orders.|
For more information about JDBC application modules, see Configuring JDBC Application Modules for Deployment.
For information about deploying stand-alone JDBC modules, see “.”
All WebLogic JDBC module files must end with the -jdbc.xml suffix, such as
examples-demo-jdbc.xml. WebLogic Server checks the file name when you deploy the module. If the file does not end in
-jdbc.xml, the deployment will fail and the server will not boot.
When you use production redeployment (versioning) to deploy a version of an application that includes a packaged JDBC module, WebLogic Server identifies the data source defined in the JDBC module with a name in the following format:
This name is used for data source runtime MBeans and for registering the data source instance with the WebLogic Server transaction manager.
If transactions in a retiring version of an application time out and the version of the application is then undeployed, you may have to manually resolve any pending or incomplete transactions on the data source in the retired version of the application. After a data source is undeployed (in this case, with the retired version of the application), the WebLogic Server transaction manager cannot recover pending or incomplete transactions.
For more information about production redeployment, see:
In support of the modular deployment model for JDBC resources in WebLogic Server, BEA provides a schema for WebLogic JDBC objects:
weblogic-jdbc.xsd. When you create JDBC resource modules (descriptors), the modules must conform to the schema. IDEs and other tools can validate JDBC resource modules based on the schema.
The schema is available at http://www.bea.com/ns/weblogic/920/weblogic-jdbc.xsd.
When you create JDBC resources using the Administration Console or WLST, WebLogic Server creates MBeans (Managed Beans) for each of the resources. You can then access these MBeans using JMX or the WebLogic Scripting Tool (WLST). See Developing Custom Management Utilities with JMX and WebLogic Scripting Tool for more information.
Figure 2-4 shows the hierarchy of the MBeans for JDBC objects in a WebLogic domain.
JDBCSystemResourceMBean is a container for the JavaBeans created from a data source module. However, all JMX access for a JDBC data source is through the
JDBCSystemResourceMBean. You cannot directly access the individual JavaBeans created from the data source module.
WebLogic Server JDBC supports JSR-77, which defines the Java EE Management Model. The Java EE Management Model is used for monitoring the runtime state of a Java EE Web application server and its resources. You can access the Java EE Management Model to monitor resources, including the WebLogic JDBC system as a whole, JDBC drivers loaded into memory, and JDBC data sources.
To comply with the specification, BEA added the following runtime MBean types for WebLogic JDBC:
JDBCServiceRuntimeMBean—Which represents the JDBC subsystem and provides methods to access the list of
JDBCDataSourceRuntimeMBeanscurrently available in the system.
JDBCDriverRuntimeMBean—Which represents a JDBC driver that the server loaded into memory.
JDBCDataSourceRuntimeMBeans—Which represents a JDBC data source deployed on a server or cluster.
|Note:||WebLogic JDBC runtime MBeans do not implement the optional Statistics Provider interfaces specified by JSR-77.|
For more information about using the Java EE management model with WebLogic Server, see Monitoring and Managing with the Java EE Management APIs.
Basic tasks you need to perform when creating JDBC resources with the WLST are:
# Create JDBC
# The prefix specifies the prefix on property names.
# Example: for property "mypool.Name=mypool", the prefix would be "mypool."
from java.lang import System
print "@@@ Starting the script ..."
url = sys.argv
usr = sys.argv
password = sys.argv
if servermb is None:
print '@@@ No server MBean found'
print("*** Creating JDBC with property prefix " + prefix)
# Create the Connection Pool. The system resource will have
# generated name of <PoolName>+"-jdbc"
myResourceName = props.getProperty(prefix+"PoolName")
print("Here is the Resource Name: " + myResourceName)
jdbcSystemResource = wl.create(myResourceName,"JDBCSystemResource")
myFile = jdbcSystemResource.getDescriptorFileName()
print ("HERE IS THE JDBC FILE NAME: " + myFile)
jdbcResource = jdbcSystemResource.getJDBCResource()
# Create the DataSource Params
dpBean = jdbcResource.getJDBCDataSourceParams()
# Create the Driver Params
drBean = jdbcResource.getJDBCDriverParams()
propBean = drBean.getProperties()
driverProps = Properties()
e = driverProps.propertyNames()
while e.hasMoreElements() :
propName = e.nextElement()
myBean = propBean.createProperty(propName)
# Create the ConnectionPool Params
ppBean = jdbcResource.getJDBCConnectionPoolParams()
if not props.getProperty(prefix+"ShrinkPeriodMinutes") == None:
if not props.getProperty(prefix+"TestTableName") == None:
if not props.getProperty(prefix+"LoginDelaySeconds") == None:
# Adding KeepXaConnTillTxComplete to help with in-doubt transactions.
xaParams = jdbcResource.getJDBCXAParams()
# Add Target
You can modify or monitor JDBC objects and attributes by using the appropriate method available from the MBean.
For more information, seein the WebLogic Scripting Tool.
This section provides best practices information when using WLST to configure JDBC resources:
You can target or deploy JDBC resources to a cluster to improve the availability of cluster-hosted applications. For information about JDBC objects in a clustered environment, see “” in Using WebLogic Server Clusters.
Multi data sources are supported for use in clusters. However, note that multi data sources can only use data sources in the same JVM. Multi data sources cannot use data sources from other cluster members.