Workflowpatterns with webMethods BPM Suite


I am from Software AG Germany/Presales and I would like to introduce you to a project about workflow patterns:

The Workflow Patterns initiative is a joint effort of Eindhoven University of Technology and Queensland University of Technology and is seen by many process specialists among other things as a reference for the evaluation of business process management suites (BPMS). So Software AG is often being faced with the question, if we support those patterns with our webMethods BPMS offering.
The purpose of this project is about to approve Software AGs ability to realize these patterns with webMethods in a reliable and comprehensive way.

I have seen this project as a kind of riddle and maybe you can do also :smiley:

Download the attachments at the end of this post. The assets contain an Integration Server package and a process project.
Mandatory components of the 9.x versioned environment are:

  • webMethods IS
  • Broker
  • My webMethods Server (MWS)
  • Software AG Designer


  • All docTypes are synchronized with Broker automatically when the package is loaded
  • All processes have to be deployed using the “build and upload for execution” functionality within Software AG Designer
  • All processes can be instantiated by using a service in the corresponding folder under: pub.<< process name >>.start:startProcessInstance
  • Some processes need some additional service calls to continue processing e.g. when signals are used
  • All process steps log the time-stamp and step-name in the server.log when they are called
  • All processing can be verified in MWS under Process Instances
  • All processes are documented directly in Software AG Designer including:
    ** Link to Workflow Pattern
    ** Description
    ** Motivation
    ** Context
  • Some processes contain additional information in the model by use of the text annotation

Project Status
The project should be seen as a basis for discussion as long as the realization is not yet verified by a significant number of specialists.
With this project the following control-flow patterns are now realized (some in different variations):

  • 1 Sequence
  • 2 Parallel Split
  • 3 Synchronization
  • 4 Exclusive Choice
  • 5 Simple Merge
  • 6 Multi-Choice
  • 7 Structured Synchronizing Merge
  • 8 Multi-Merge
  • 9 Structured Discriminator
  • 10 Arbitrary Cycles
  • 11 Implicit Termination
  • 12 Multiple Instances without Synchronization
  • 13 Multiple Instances with a Priori Design-Time Knowledge
  • 14 Multiple Instances with a Priori Run-Time Knowledge
  • 15 Multiple Instances without a Priori Run-Time Knowledge
  • 16 Deferred Choice
  • 17 Interleaved Parallel Routing
  • 18 Milestone
  • 19 Cancel Activity
  • 20 Cancel Case
  • 21 Structured Loop

The following patterns are not yet realized:

  • 22 Recursion
  • 23 Transient Trigger
  • 24 Persistent Trigger
  • 25 Cancel Region
  • 26 Cancel Multiple Instance Activity
  • 27 Complete Multiple Instance Activity
  • 28 Blocking Discriminator
  • 29 Cancelling Discriminator
  • 30 Structured Partial Join
  • 31 Blocking Partial Join
  • 32 Cancelling Partial Join
  • 33 Generalized AND-Join
  • 34 Static Partial Join for Multiple Instances
  • 35 Cancelling Partial Join for Multiple Instances
  • 36 Dynamic Partial Join for Multiple Instances
  • 37 Local Synchronizing Merge
  • 38 General Synchronizing Merge
  • 39 Critical Section
  • 40 Interleaved Routing
  • 41 Thread Merge
  • 42 Thread Split
  • 43 Explicit Termination

I would be glad to get some feedback if the solutions that I found, fits your understanding of what the workflowpatterns are about, or if they do not and why.

Extra-Bonus-Jackpot-Points are going to those, who help to complete the project so that all patterns are proved against webMethods and the riddle is solved :mrgreen:


WFP Assets (597 KB)