3. Service Assembly: BPEL module cannot be deployed directly to Sun Java
System Application Server. Only composite applications or service assemblies
having at least one JBI module can be deployed to the BPEL engine of the
server. For the purpose of this sample, we'll create a Composite Application
that has BPEL module deployed as JBI module. For more information on
BPEL engine, JBI modules, and Service Assemblies, refer to Chapter 1.
Our BPEL process communicates with the partner services through their
public interfaces. These interfaces are defined in partner-specific WSDL
files. When you drag-and-drop a partner service into a BPEL process,
these interfaces are imported.
Note that our partner service implementation is minimal as it is of less interest to
a BPEL developer. You can download the code and the DB scripts and work on an
appropriate implementation.
Building a Sample Application
[ 226 ]
The following business process diagram depicts our example:
BPEL process is also a web service. Just like any other web service, BPEL process
has a companion WSDL file that describes its public interfaces. This WSDL interface
enumerates the operations and messages that clients can target in order to create an
instance of the process.
BPEL processes are deployed to the BPEL runtime, which manages the process
lifecycle.
Pages:
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201