Pattern-based Evaluation of IBM WebSphere BPEL (PDF)

Inhaltsangabe:Abstract:
There are numous Business Process Execution Language (BPEL) modeling tools available on the market today that differ in their power and ability to transform patterns into executable BPEL code. Examples for commercially available tools are ActiveBPEL [5], Oracle-BPEL [12] and IBM WebSphere Integration Developer [3]. Patterns describe business requirements and thus define the needs in workflow languages and their related modeling tools. Patterns are used as a basis to compare these tools.
In this student research paper should be examined to which extend the control-flow patterns presented in [1] are supported by IBM WebSphere Integration Developer V6.0 [3] on IBM WebSphere Process Server for Multiplatforms V6.0 [4]. IBM WebSphere Integration Developer uses the Business Process Execution Language for Web Services version 1.1 (BPEL4WS) [2, 7] as the basis but already implements functionality of WS-BPEL version 2.0. Control-flow patterns include basic control patterns, patterns involving multiple instances, state-based patterns and cancellation patterns. Extensive surveys of control-flow patterns have been made in [10] and [11].
The BPEL and the Web Service Description Language (WSDL) source code of the implementations are listed in the appendix. activities are mostly used as placeholders for comprehensive business logic and if this is not the case, they are explained in detail. Inhaltsverzeichnis:Table of Contents:
1.Introduction1
2.Evaluation of control-flow patterns in IBM WebSphere Integration Developer2
2.1Basic Control Flow Patterns2
Pattern 1 (Sequence)2
Pattern 2 (Parallel Split)2
Pattern 3 (Synchronization)3
Pattern 4 (Exclusive Choice)4
Pattern 5 (Simple Merge)6
2.2Advanced Branching and Synchronization Patterns7
Pattern 6 (Multi-choice)7
Pattern 7 (Synchronizing Merge)8
Pattern 8 (Multi-merge)8
Pattern 9 (Discriminator)9
2.3Structural Patterns10
Pattern 10 (Arbitrary Cycles)10
Pattern 11 (Implicit Termination)11
2.4Patterns involving Multiple Instances11
Pattern 12 (Multiple Instances without Synchronization)11
Pattern 13 (Multiple Instances with a Priori Design Time Knowledge)12
Pattern 14 (Multiple Instances with a Priori Runtime Knowledge)13
Pattern 15 (Multiple Instances without a Priori Runtime Knowledge)14
2.5State-based Patterns16
Pattern 16 (Deferred Choice)16
Pattern 17 (Interleaved Parallel Routing)17
Pattern 18 (Milestone)19
2.6Cancellation Patterns20
Pattern 19 (Cancel [...]