SQL Components

You can catalog SQL tables, views and store procedures. Use SQL components from your processes and BPM objects to query, update and execute SQL statements on external databases.

Supported Databases

You can catalog components from JDBC-compliant databases. You need a special JDBC driver for each database vendor.

Oracle BPM includes JDBC drivers for several database vendors including Oracle, IBM DB2, Microsoft SQL Server, Informix and Sybase. To use an external JDBC driver you must first include the .jar files of the driver as an External Resource of type Java Class Library.

JDBC Connections on Runtime

The Process Execution Engine manages and pools the connections to the database servers automatically.

When the Engine runs on an EJB container (such as Oracle WebLogic or IBM WebSphere), it leverages the JDBC data source functionality provided by the container. In such environments, all JDBC connectivity and connection pooling is handled by the EJB container.

Cataloging a SQL Component
Before using SQL tables from processes or BPM Objects, you must include them into the component catalog. When you catalog SQL table components, Studio gathers all the information it needs for integrating with your SQL database and executing statements at runtime.
Using SQL Components
You can catalog SQL tables, views and store procedures. Use SQL components from your processes and BPM objects to query, update and execute SQL statements on external databases.
SQL Components as Instance Variables
You can use cataloged SQL table components as process instance variables. This is useful when you want to persist data associated with a process instance into a separate database.
Mapping SQL to BPM Components
This sections explains how JDBC/SQL objects and types map to BPM components and PBL types when cataloging SQL tables, views and procedures.

Parent topic: External Components

Related concepts

Java Class Library

Related reference

SQL Database