JDBC Module File Naming Requirements JDBC Modules in Versioned Applications JDBC Schema

Configuring WebLogic JDBC Resources 2-5 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 data source 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 Oracle 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 data source configuration between domains, such as between the development domain and the staging domain. For more information about JDBC application modules, see Appendix A, Configuring JDBC Application Modules for Deployment. For information about deploying stand-alone JDBC modules, see Deploying JDBC, JMS, WLDF Application Modules in Deploying Applications to Oracle WebLogic Server.

2.3.3 JDBC Module File Naming Requirements

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.

2.3.4 JDBC Modules in Versioned Applications

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: application_idversion_idmodule_namedata_source_name Note: When deploying JDBC modules as standalone modules, a multi data source needs to have a deployment order that is greater than the deployment orders of its member data sources. 2-6 Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server This name is used for data source run-time 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: ■ Developing Applications for Production Redeployment in Developing Applications for Oracle WebLogic Server ■ Using Production Redeployment to Update Applications in Deploying Applications to Oracle WebLogic Server

2.3.5 JDBC Schema

In support of the modular deployment model for JDBC resources in WebLogic Server, Oracle 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:xmlns.oracle.comweblogicjdbc-data-source1.0jdbc-data- source.xsd .

2.4 JMX and WLST Access for JDBC Resources