Manage JDBC providers for your application server

A JDBC provider specifies how database connections are created for data sources that are associated with the provider and which JDBC driver is used for the connection. Creating JDBC providers define the JDBC driver that your application uses. The Manage JDBC Providers form allows you to view the list of defined JDBC providers, create a new JDBC provider, modify the properties of an existing JDBC provider, or remove a JDBC provider from your application server. WebSphere Application Server - Express for iSeries supports these JDBC drivers:

For additional information on the IBM Toolbox for Java JDBC driver, see The IBM Toolbox for Java JDBC driver.

To manage your JDBC providers on an application server, follow these steps:

  1. Start the HTTP Server Administration interface.

  2. Click the Manage tab.

  3. Select an application server from the Server list.

  4. Expand Resource Configuration.

  5. Click Manage JDBC Providers.

From the Manage JDBC Providers form, you can do the following:

Create a new JDBC provider

With the exception of step 1, these steps also apply to the Create JDBC Provider wizard.

  1. Click Create.

  2. Specify a name for your new JDBC provider in the JDBC provider name field.

  3. Click Next.

  4. Select the database access method.

    • Local - IBM Developer Kit for Java JDBC(TM) driver
      Select this option if the application server and the database are located on the same system.

    • Remote - IBM Toolkit for Java JDBC(TM) driver
      Select this option if the application server and the database are located on separate systems or logical partitions (LPAR).

  5. Select Java Transaction API (JTA) enablement.

    • Enabled
      JTA is enabled. JTA supports two-phase commit, which is a database protocol that ensures a transaction is completely committed to the database. This is necessary for transactions that are comprised of multiple updates to one or more databases. If one of the updates fails, the entire transaction fails, and all updates that were made in the transaction are rolled back. This ensures that only complete information is saved.

    • Disabled
      JTA is disabled. If you do not need to use two-phase commit, disable JTA. For example, if a transaction only updates one database, JTA is not required. Disabling JTA can improve application performance.

  6. The summary page lists all of the choices you have made in the wizard. If any of the information displayed is incorrect, click Back until you reach the wizard form with the incorrect information and make your corrections. Click Finish to complete the wizard.

Edit the properties of existing JDBC provider

  1. Select a JDBC provider from the JDBC providers table.

  2. Click Properties.

  3. You can edit one or more properties shown for the JDBC provider.

    • Edit the JDBC provider name or description

      1. Click the General tab in the JDBC Provider Properties form. This value allows for an optional user-defined descriptions of the JDBC provider.

      2. Specify a new name for the JDBC provider in the JDBC provider name field.

      3. Specify a new description for the JDBC provider in the JDBC provider description field.

      4. Specify a new JDBC class path in the Class path field. This field is only available if the database access method is remote.

    • Add, edit, or delete a data source

      1. Click the Data Sources tab in the JDBC Provider Properties form. For more information on managing data sources, see Manage data sources for your application server.

  4. Click Apply or OK to save your changes.

Remove a JDBC provider

  1. Select a JDBC provider from the table.

  2. Click Remove.

  3. Click OK