Type 3 driver .E2.80.93 Network-Protocol driver .28middleware driver.29 JDBC driver

1 type 3 driver – network-protocol driver (middleware driver)

1.1 functions
1.2 advantages
1.3 disadvantages

type 3 driver – network-protocol driver (middleware driver)

schematic of network protocol driver

the jdbc type 3 driver, known pure java driver database middleware, database driver implementation makes use of middle tier between calling program , database. middle-tier (application server) converts jdbc calls directly or indirectly vendor-specific database protocol.

this differs type 4 driver in protocol conversion logic resides not @ client, in middle-tier. type 4 drivers, type 3 driver written entirely in java.

the same client-side jdbc driver may used multiple databases. depends on number of databases middleware has been configured support. type 3 driver platform-independent platform-related differences taken care of middleware. also, making use of middleware provides additional advantages of security , firewall access.

functions

sends jdbc api calls middle-tier net server translates calls dbms-specific network protocol.the translated calls sent particular dbms.
follows three-tier communication approach.
can interface multiple databases – not vendor specific.
the jdbc client driver written in java, communicates middleware-net-server using database independent protocol, , net server translates request database commands database.
thus client driver middleware communication database independent.

advantages

since communication between client , middleware server database independent, there no need database vendor library on client. client need not changed new database.
the middleware server (which can full-fledged j2ee application server) can provide typical middleware services caching (of connections, query results, etc.), load balancing, logging, , auditing.
a single driver can handle database, provided middleware supports it.
e.g.: ida server

disadvantages

requires database-specific coding done in middle tier.
the middleware layer added may result in additional latency, typically overcome using better middleware services.




^ http://docs.oracle.com/cd/e19509-01/820-5069/ggzci/index.html