Database Reference
In-Depth Information
Usually BPEL process consists of multiple steps that provide an overall process.
Each step is called an
activity
. BPEL interacts with external services either by in-
voking operations on external web services or by receiving invocations from external
entities. In simple words, it is either the consumer that invokes operations to others
or the provider that receives invocations from others.
Invoking a BPEL process from Java
BPEL is a workflow system that manages coordination and communication for mul-
tiple concurrent conversations at the same time. Administrators can view the status
of each request in the Enterprise Manager (EM) console.
BPEL provides client interfaces via SOAP, JCA, or native Java. BPEL itself is a ser-
vice that can be invoked from Java programs. BPEL processes can be invoked using
Oracle-provided Java APIs. Usually the BPEL processes are invoked from a Java
program using Partner Link.
A BPEL process is available for invocation from standalone Java using one of the
following interfaces:
• WSDL Interface
• BPEL Process Manager Java API
• JDeveloper Web Services Proxy
• Business delegate Java interface
Invoking BPEL is similar to calling any other web service from a Java program. BPEL
implements a service that is defined in the WSDL. In case you are using Eclipse or
NetBeans for writing the Java code, right-click on your project and select
New Web
Service Client
. Select the
WSDL
for a BPEL process in the dialog box.
BPEL can be initiated from Java using business delegate Java interface from a loc-
ally or remotely used RMI. Partner Link allows BPEL to have conversations with
WSDL-defined web services.
In JDeveloper, we can invoke a BPEL process from Java programs using the SOAP
interface or native Java interfaces. The following figure shows the structure of invok-
ing a BPEL process:
