Administration Console allows you to configure various JDBC
resources: connection pools, multipools, and data sources. First you
need to create one or more connection pools. You may want to create a
multipool in order to benefit from additional load-balancing or
failover capabilities. Next, set up the data sources, which provide
access to the JDBC pools. These resources then can be targeted to
multiple servers and/or clusters and accessed by multiple enterprise
applications. After this, you can use either the Administration
Console or the command-line
weblogic.Admin tool to
manage and monitor JDBC connectivity.
An alternative approach would be to configure an application-specific data source and connection pool, in which case the JDBC resources are isolated to a particular enterprise application. In this instance, the J2EE application fully captures the configuration of all JDBC resources that it needs, without having to rely on the proper configuration of the servers to which the application is deployed.
Once you have installed a third-party JDBC driver, you need to make the driver classes visible to WebLogic Server when it starts up. This means that you need to modify WebLogic startup scripts so that the system classpath includes the libraries for the JDBC driver. For instance, if you wish to use Microsoft’s SQL Server 2000 JDBC Driver, you need to modify the startWeblogic script to include the library JARs: