Creating a JDBC provider

To enable Rule Execution Server, you create a JDBC provider in WebSphere® Application Server, as the first step in creating a data source.

Before you begin

To create a JDBC provider, you work in the WebSphere Integrated Solutions Console. Log in to the console as explained in Before you start: Opening the administration console.

About this task

The first step in creating a data source, based on the database schema that you have created in Step 3: Setting up your database, is to create a JDBC provider. You can install the JDBC provider on the cell, node, cluster, or server level. Follow these steps to install a Derby or DB2® JDBC provider at node level.

Note: Some drivers, such as Oracle OCI drivers, need to access additional libraries at run time (.dll or .so files). As a consequence, you must set up your working environment to access these libraries. For example, set the PATH and LD_LIBRARY_PATH environment variables.

Procedure

Click Resources > JDBC > JDBC Providers.
Under Scope, select the Node=xxx, Server=yyy, and then click New.
xxx is the name of your node and yyy the name of your server.s

In Step 1, select the database type, provider type, and an implementation type that supports XA features.

Table 1. JDBC provider options for DB2 and Derby
Database type	Derby	DB2
Provider type	Derby JDBC Provider	DB2 Universal JDBC Driver Provider
Implementation type	XA data source	Connection pool data source
Name	Enter a name, for example `Rule Execution Server JDBC Provider`	Enter, for example, `DB2 Universal JDBC Driver Provider for RES`

Click Next.
In Step 2, leave all the class path values, including the blanks, as the default values and click Next.
A summary is provided in Step 3.
Check that the class path to the JAR file of your driver and the implementation class are correct.
Default values are sufficient, except in very special cases.
Click Finish.
In the next panel, click Save to save the changes to the master configuration.
If you work in a cluster environment, make sure that the Synchronize changes with Nodes check box is selected.
Restart your server for the changes to be taken into account.
If you work with a DB2 database, the DB2 installation process might have installed the db2jcc_license_cisuz.jar file to a location that is not in the WebSphere Application Server path.
In this case, find the db2jcc_license_cisuz.jar file by running the following command.
Before you run this command, it is best to set yourself as the root user to avoid permissions messages.
```
find / -name db2jcc_license_cisuz.jar
```
From the WebSphere Integrated Solutions Console, open Environment > WebSphere variables and click DB2UNIVERSAL_JDBC_DRIVER_PATH.
Set the value to the path that the find command returned.
Click OK and Save to save the changes to the master configuration.