InfoCenter Home >
4: Developing applications >
4.2: Building Web applications >
4.2.4: Accessing data >
4.2.4.2: Obtaining and using database connections

4.2.4.2: Obtaining and using database connections

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

  • Programming directly to the connection pooling model through the JDBC 2.0 Optional Package API
  • Use of the IBM data access beans, which also use connection pooling but give you additional ability to manipulate result sets

WebSphere Application Server versions earlier than 4.0 also supported the connection manager model, which was based on JDBC 1.0. If your Web applications used the connection manager model, you must migrate these in Version 4.0 to use connection pooling.

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.

Considerations for DB2/390

Speak with your DB2/390 administrator about setting the RRULOCK parameter to YES. This ensures that SELECT ... FOR UPDATE statements get an update lock rather than a sharable lock. If your database is using sharable locks and you attempt to commit updates later, the database can become deadlocked.

Go to previous article: Accessing data Go to next article: Accessing data with the JDBC 2.0 Optional Package APIs

 

 
Go to previous article: Accessing data Go to next article: Accessing data with the JDBC 2.0 Optional Package APIs