IBM WAS v6.1 Administration Unit 3 Runtime & JDBC Drivers

JDBC Driver implementation

Type Two jdbc drivers (thick) are vendor written class wrapper utilizing vendor specific protocols. This type will go across firewalls or Ethernet.

Type Three jdbc drivers (NET Protocol) Will go across WAN & Firewall.

Type Four jdbc drivers (Native Protocol) No external processes XA drivers support transaction recovery.

SUN - ODBC wrapper class can talk to anyone in level ONE only.

V.1 No Standards

V.2 Must be XA compliant - 2 phase commits 1st. standard written.

V.3 Drivers provide their own data source - better performance & control.

WAS 4.0- only supported client data source no vendor data sources.  

Data Sources Data sources can improve performance and portability for database access - Standard XA data sources Connection Pooling is provided by two parts J2C connection manager Relational resource adapter

Notes: Rather than having the JDBC drivers directly communicate with the database, the communication is abstract into a data source.

IBM allows developers to identify their owwn data sources in the Enhanced EAR file to automatically develop their data sources within a test environment.

1. Disable server from using the test data source connection pool
2. Use a script to skip developer test data source connection pool.