To this end, you can easily create and develop a business
process in an intuitive graphical programming environment called the BPEL
Designer and deploy it to a separate runtime environment for execution. This
runtime is the OpenESB runtime that is integrated with the GlassFish
application server.
The BPEL Process starts with a receive activity, proceeds with invoking external
services and finishes by replying back to the Client. A BPEL process typically
interacts with one or more external Web Services (the BPEL process is also a web
service). These external web services are called partner services.
Chapter 1
[ 11 ]
The above figure shows a preview of how a simple BPEL process can be designed
using the NetBeans BPEL Designer. In the above example, there are two partner
services, one is the BPEL client implementation and the other one is the web service
EJB implementation which has one operation processItinerary.
In order to understand the simple BPEL process, let us define some of the terms most
commonly used while designing a BPEL process.
Partner Services
Any external service or client that interacts with the BPEL process is called a partner
service. A process starts and ends somewhere, and involves the interaction of at least
one other outside partner.
Pages:
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29