In Mainframe Enablement for SOA Part I and II, we have discussed the approaches to enable CICS applications and IMS; now let us explore an approach to expose DB2 data or application as service.
JDBC Solution
The DB2 application or data can be exposed as Web services, implemented in J2EE Application Server via Java Database Connectivity (JDBC). These Web services can be accessed directly from a Web service consumer using the Web Service protocols.
The Java Database Connectivity (JDBC) is an application programming interface (API) that the Java programming language uses to access relational database, such as DB2. The actual implementation of the JDBC interface is provided by the database vendor as a driver. This provides portability because all access using the JDBC is through standard calls with standard parameters. This enables an application developer to write code with little regard to the database being used, because all of the platform-dependent code is stored in the JDBC drivers.
There are 4 types of JDBC driver and z/OS supports Type 2 and Type 4. A type 2 driver is platform- and database-specific implementation. Type 4 drivers are implemented using Java and are platform independent but are database-specific as they use proprietary database protocol to connect. For example, DB2 Type 4 driver access DB2 through DRDA. These pure Java drivers deliver high performance, scalable remote connectivity and manageability for Java-based enterprise applications to a remote DB2 running in z/OS database server
Architecture
Advantages of this approach
- Extremely easy to use and quite popular approach with Java developers.
No comments:
Post a Comment