JDBC providers are used by server applications to retrieve data from databases. The following procedure documents how to add an Oracle JDBC provider to WebSphere. Data sources will also be created to connected to the ALBPM engine and ALBPM directory.
To add a JDBC provider to WebSphere:
If the WebSphere server has not been started, choose Start | All Programs | IBM WebSphere | Application Server | Profiles | profile-name | Start the Server.
To launch the WebSphere Administrative Console, choose Start | All Programs | IBM WebSphere | Application Server | Profiles | profile-name | Administrative Console. You can also launch the console directly from a browser (http://host:port/ibm/console).
Enter your User ID and click Log in.
Add a JDBC provider:
In the left pane of the Administrative Console, click Resources | JDBC Providers.
In the right pane, on the JDBC Providers page, click Browse Servers. On the JDBC Providers | Select a Server Scope page, select a server Name and click OK.
On the JDBC Providers page, click New.
On the JDBC Providers | New page, configure the following properties and click Next.
|
Step 1: Database Type |
Select Oracle. |
|
Step 2: Provider Type |
Select Oracle JDBC Driver. |
|
Step 3: Implementation Type |
Select XA Data Source. |
In the Class Path field, enter the path to the database driver specified in Start and Configure the WebSphere Server (for example, C:\bea\albm5.7\j2eews\ext\ojdbc14.jar).
Click OK.
Add an engine data source to the JDBC provider:
On the JDBC Providers page, click the JDBC provider Name created in the previous steps.
On the JDBC Providers | provider-name page, click Data Sources.
On the JDBC Providers | provider-name | Data Sources page, click New.
On the JDBC Providers | provider-name | Data Sources | New page, configure the following properties and click OK.
|
Name |
Enter a name for the engine data source. |
|
JNDI Name |
This name must match the Engine Runtime Datasource Lookup Name defined for the ALBPM engine in Process Administrator. |
|
Component-Managed Authentication |
Select the engine connector previously created in Add a J2EE Engine Connector. |
|
Container-Managed Authentication |
Select the engine connector previously created in Add a J2EE Engine Connector. |
|
Mapping Configuration |
Select DefaultPrincipalMapping. |
|
URL |
Enter the URL to the data source in the syntax: jdbc:oracle:driver-type:@host:port:SID |
To test the new data source, on the JDBC Providers | provider-name | Data Sources page, select the checkbox for the engine data source and click Test Connection. The test result is displayed in the Messages section at the top of the page.
Add a directory data source to the JDBC provider:
On the JDBC Providers page, click the JDBC provider Name created in the previous steps.
On the JDBC Providers | provider-name page, click Data Sources.
On the JDBC Providers | provider-name | Data Sources page, click New.
On the JDBC Providers | provider-name | Data Sources | New page, configure the following properties and click OK.
|
Name |
Enter a name for the directory data source. |
|
JNDI Name |
This name must match the Engine DI Datasource Lookup Name defined for the ALBPM engine in Process Administrator. |
|
Component-Managed Authentication |
Select the directory connector previously created in Add a J2EE Directory Connector. |
|
Container-Managed Authentication |
Select the directory connector previously created in Add a J2EE Directory Connector. |
|
Mapping Configuration |
Select DefaultPrincipalMapping. |
|
URL |
Enter the URL to the data source in the syntax: jdbc:oracle:driver-type:@host:port:SID |
To test the new data source, on the JDBC Providers | provider-name | Data Sources page, select the checkbox for the directory data source and click Test Connection. The test result is displayed in the Messages section at the top of the page.
On the JDBC Providers | provider-name | Data Sources page, under Messages, click Save.
On the JDBC Providers | provider-name | Data Sources | Save page, click Save.