InfoCenter Home >
4: Developing applications >
4.2: Building Web applications >
4.2.4: Putting it all together (Web applications) >
4.2.4.2: Obtaining and using database connections

4.2.4.2: Obtaining and using database connections

IBM WebSphere Application Server Version 3.5 provides two options for accessing database connections:

  • Connection pooling (model based on JDBC 2.0)
  • Connection manager (now deprecated, model based on JDBC 1.0)

Because connection pooling is the most efficient model for Web applications, it is recommended that you use connection pooling for all new applications requiring database access. You should consider migrating existing applications to connection pooling if your applications use connection manager or the standard JDBC 1.0 methods for getting database connections.

IBM WebSphere Application Server also provides data access beans, which offer a rich set of features for working with relational database queries and result sets.

For a comprehensive treatment of WebSphere connection pooling and data access, be sure to read the IBM whitepaper to be published on the Web during the summer of 2001.

Tips for data access programming

If your product installation uses Oracle or Sybase for the repository and you try to use DB2 datasources for enterprise beans, the DB2 JDBC driver might fail to load. To fix the problem, your administrator must run the db2profile script. For details, see the Related information.

Go to previous article: Putting it all together (Web applications) Go to next article: Accessing data with the JDBC 2.0 Optional Package APIs

 

 
Go to previous article: Putting it all together (Web applications) Go to next article: Accessing data with the JDBC 2.0 Optional Package APIs