Home > Articles > Programming > Java

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

JDBC Drivers

DB2 UDB provides for JDBC connectivity through a number of Java classes and interfaces that implement the JDBC specification. The implementation is known as a JDBC driver. DB2 currently offers JDBC drivers known as legacy/CLI drivers and the universal JDBC driver.

Using the JDBC Type 2 DriverFigure 1

JDBC 2 Type 2 drivers use an OS-specific library to facilitate communication with DB2. DB2 ships with two different type 2 drivers: the legacy/CLI JDBC driver and the universal JDBC driver. This interaction is illustrated in Figure 1.

Figure 1 JDBC Type 2 driver implementation: the legacy/CLI JDBC driver.

The legacy/CLI JDBC driver is provided in the file db2java.zip which is in the default DB2 installation directory, "c:\Program Files\IBM\SQLLIB\java".

If you are trying to interact with a remote database using the legacy/CLI JDBC driver, you need to use the DB2 Configuration Assistant. Under the covers, this driver performs a native connect through a local DB2 client. If you have installed a DB2 UDB v8 server, you will have the Configuration Assistant and the rest of the DB2 product. If you are connecting to a remote DB2 server, you should install the DB2 Application Development Client or the DB2 Runtime Client. These clients are downloadable for free at http://www-306.ibm.com/software/data/db2/udb/support.html.

For Java development, the only required DB2 software is the runtime client, and it is a much smaller download image (around 68MB for Windows and 200MB for Linux). If you decide that the Universal JDBC driver in type 4 mode is all you really need, you can simply copy the db2jcc.jar file and its corresponding license jar file from an existing installation. These two files would result in less than 1MB of disk space.

If you are just getting started with DB2 locally on your own machine we would recommend that you download the DB2 Personal Developer's Edition product.

Figure 2 shows the DB2 Configuration Assistant (db2ca), it can be used to catalog the DB2 database and the node directory information that will be used by the JDBC driver to locate the DB2 database on a remote server.

Figure 2Figure 2 DB2 Configuration Assistant.

Before you start your endeavors of hooking up to DB2 via Java, it is a good idea to ensure connectivity to your remote database. This can be done using the Configuration Assistant, as shown in Figure 3.

Figure 3Figure 3 Test the DB2 connection.

The code of Listing 1 shows the programmatic access of the database we created earlier. Note that the implementation package name is com.ibm.db2.jdbc.app.DB2Driver. Listing 1, 2, and 3 all do the same thing. They simply retrieve data from the database we created using a simple SQL query.

Listing 1 Use of the legacy/CLI JDBC driver (db2java.zip), a JDBC-type driver to interact with DB2

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;

public class Type2ExampleLegacy {

    public static void main(String[] args) 
    {
       try
       {
           // load the DB2 Driver
           Class.forName("COM.ibm.db2.jdbc.app.DB2Driver");
           // establish a connection to DB2
           Connection db2Conn = 
         DriverManager.getConnection
             ("jdbc:db2:phoneDB","db2admin","db2admin");
            // use a statement to gather data from the database
            Statement st = db2Conn.createStatement();
            String myQuery = "SELECT * FROM PHONENUMBERS"; 
           // execute the query
            ResultSet resultSet = st.executeQuery(myQuery); 
            // cycle through the resulSet and display what was grabbed
            while (resultSet.next())
            {
             String name = resultSet.getString("name");
             String phoneNumber = resultSet.getString("phonenumber");
               System.out.println("Name: " + name);
               System.out.println("Phone Number: " + phoneNumber);
               System.out.println("-------------------------------");
           }
           // clean up resources
           resultSet.close();
           st.close();
           db2Conn.close();
       }
       catch (ClassNotFoundException cnfe)
       {
           cnfe.printStackTrace();
       }
       catch (SQLException sqle)
       {
           sqle.printStackTrace();
       }
    }
}

We are assuming that you have a background in JDBC. (If not, it might be a good idea to take a look at articles on this topic on the InformIT site.) The only difference is that they use the different drivers, driver architectures, and syntax to achieve their connectivity. Figure 4 shows the successful execution of the code.

Figure 4Figure 4 Successful execution of our sample code.

The Universal JDBC driver

With the advent of DB2 8.1 came the new Universal JDBC driver, which can be used either in a Type 2 architecture or a Type 4 architecture (see below). In a Type 2 mode, the Universal JDBC driver provides local application performance gains (because it avoids using TCP/IP protocol to communicate to the DB2 server). In Type 2 mode, there is also full support for distributed transactions. Therefore, if the application and the DB2 server are on the same machine, we recommend that you use the Universal JDBC driver in Type 2 mode. The driver is located in the file db2jcc.jar. Note from the code of Listing 2 that the implementation package is com.ibm.db2.jcc.DB2Driver. Also, at runtime, in type 2 mode and attempt will be made to load a file named db2jcct2.dll. This file is installed when the Runtime Client or Application Development client of the product are installed.

Listing 2 Use of the Universal driver (db2jcc.jar)in a JDBC Type 2 setup to interact with DB2.

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;

public class Type2ExampleUniversal {

    public static void main(String[] args) 
    {
       try
       {
           // load the DB2 Driver
           Class.forName("com.ibm.db2.jcc.DB2Driver");
            // establish a connection to DB2
            Connection db2Conn = 
         DriverManager.getConnection
             ("jdbc:db2:phoneDB","db2admin","db2admin");
            // use a statement to gather data from the database
            Statement st = db2Conn.createStatement();
            String myQuery = "SELECT * FROM PHONENUMBERS"; 
           // execute the query
            ResultSet resultSet = st.executeQuery(myQuery); 
            // cycle through the resulSet and display what was grabbed
            while (resultSet.next())
            {
             String name = resultSet.getString("name");
             String phoneNumber = resultSet.getString("phonenumber");
               System.out.println("Name: " + name);
               System.out.println("Phone Number: " + phoneNumber);
               System.out.println("-------------------------------");
           }
           // clean up resources
           resultSet.close();
           st.close();
           db2Conn.close();
       }
       catch (ClassNotFoundException cnfe)
       {
           cnfe.printStackTrace();
       }
       catch (SQLException sqle)
       {
           sqle.printStackTrace();
       }
    }
}

Using the JDBC Type 4 Driver

A Type 4 JDBC driver connects directly to the database server using Java. (Refer to Figure 1 for an illustration of this interaction.)

In a Type 4 setup, no client Configuration Assistant is needed to catalog remote databases as with the Type 2 driver. The same db2jcc.jar file is used for the Universal driver regardless of communication mode (Type 2 or Type 4). We demonstrate how to connect to our DB2 server in Listing 3. (Note that our implementation package name is again: com.ibm.db2.jcc.DB2Driver.)

At a quick glance, it is a bit difficult to see the difference between the syntax of Listing 2 (showing the use of the Universal driver as JDBC Type 2 driver) and Listing 3 (showing the use of the Universal driver as a JDBC Type 4 driver).

Listing 3 Use of the Universal driver (db2jcc.jar) in a JDBC Type 4 setup to interact with DB2.

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;

public class Type4ExampleUniversal {

    public static void main(String[] args) 
    {
       try
       {
           // load the DB2 Driver
           Class.forName("com.ibm.db2.jcc.DB2Driver");
            // establish a connection to DB2
            Connection db2Conn = 
         DriverManager.getConnection
             ("jdbc:db2://localhost:50000/phonedb","db2admin","db2admin");
            // use a statement to gather data from the database
            Statement st = db2Conn.createStatement();
            String myQuery = "SELECT * FROM PHONENUMBERS"; 
           // execute the query
            ResultSet resultSet = st.executeQuery(myQuery); 
            // cycle through the resulSet and display what was grabbed
            while (resultSet.next())
            {
             String name = resultSet.getString("name");
             String phoneNumber = resultSet.getString("phonenumber");
               System.out.println("Name: " + name);
               System.out.println("Phone Number: " + phoneNumber);
               System.out.println("-------------------------------");
           }
           // clean up resources
           resultSet.close();
           st.close();
           db2Conn.close();
       }
       catch (ClassNotFoundException cnfe)
       {
           cnfe.printStackTrace();
       }
       catch (SQLException sqle)
       {
           sqle.printStackTrace();
       }
    }
}

Let's go over some key differences. In the Type 4 driver, our connection URL takes the form jdbc:db2://server1:50000/phonedb (as opposed to the form jdbc:sample). The DB2 server in this case is listening for client connections on port 50000. This is the default port that DB2 listens to upon installation unless you specify otherwise.

Also, note that the hostname (server1) and the port number is included in the database connection URL. These (with the port number) provide the driver with information to connect directly to the database server without having to reference the database and node catalog entries, as was required for the legacy/CLI JDBC driver discussed earlier.

Note that if you are using DB2 UDB V8.1.2 or later versions of the Universal JDBC driver, then you have to include a license JAR file in your CLASSPATH in addition to the db2jcc.jar file. Refer to the DB2 documentation to determine which JAR file to include (this file is used to determine which DB2 server platforms you will be able to access).

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020