Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Oracle BPM Suite 12c Modeling Patterns
  • Table Of Contents Toc
  • Feedback & Rating feedback
Oracle BPM Suite 12c Modeling Patterns

Oracle BPM Suite 12c Modeling Patterns

By : Acharya
4 (4)
Buy this Book
close
close
Oracle BPM Suite 12c Modeling Patterns

Oracle BPM Suite 12c Modeling Patterns

4 (4)
By: Acharya
Buy this Book

Overview of this book

This book is an invaluable resource if you are an Enterprise architect, solution architect, developer, process analyst, or application functional and technical consultant who uses Business Process Management and BPMN to model and implement Enterprise IT applications, SaaS, and cloud applications.
Table of Contents (12 chapters)
close
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Flow Control Patterns
chevron up
1. Flow Control Patterns
Sequence flow pattern
Getting ready for executing use cases
Exclusive choice and simple merge pattern
Multichoice and synchronizing merge pattern
The parallel split and synchronization pattern
Conditional parallel split and parallel merge pattern
Multimerge pattern
Discriminator and partial join pattern
Complex synchronization pattern
Summary
2
2. Multi-instance and State-based Patterns
2. Multi-instance and State-based Patterns
Multiple instances with prior design-time knowledge pattern
Multiple instances with prior runtime knowledge pattern
Multiple instances without prior runtime knowledge pattern
Static partial join for multiple instances pattern
Canceling partial join pattern
Dynamic partial join for multiple instances pattern
Structured loop pattern
Arbitrary cycle pattern
Trigger patterns
Implicit termination pattern
Explicit termination pattern
Cancelation patterns
Summary
3
3. Invocation Patterns
3. Invocation Patterns
Web service pattern
One-way invocation pattern
Publish-subscribe pattern – initiating the business process through an event
Multievent instantiation pattern – process instantiation over multiple events
Human task initiator pattern – initiating processes through human tasks
Guaranteed delivery pattern – process instantiation over JMS – Queue/Topic
Understanding multiple start events
Summary
4
4. Human Task Patterns
4. Human Task Patterns
Learning about human tasks
Milestone pattern
Routing pattern
Task assignment pattern
List builder pattern
Parallel routing pattern
Serial routing pattern
Single routing pattern
Notify/FYI pattern
Task aggregation pattern
Dispatching pattern
Escalation pattern
Rule-based reassignment and delegation pattern
Ad hoc routing pattern
Request information feature
Reassignment and delegation pattern
Force completion pattern
Routing rule pattern
Deadlines
Escalation, expiry, and renewal feature
Exclusion feature
Error assignee and reviewers
Notifications
Content access policy and task actions
Enterprise content management for task documents
Summary
5
5. Interaction Patterns
5. Interaction Patterns
Defining use cases to demonstrate interaction patterns
Conversation pattern
Asynchronous interaction pattern
Synchronous request-response pattern
Subprocess interaction patterns
Embedded subprocess interaction pattern
Event-driven interaction pattern
Summary
6
6. Correlation Patterns
6. Correlation Patterns
Correlation mechanism
Message-based correlation pattern
Cancel instance pattern
Update task pattern
Query pattern
Suspend process pattern
Suspend activity pattern
Cancel activity pattern
Summary
7
7. Exception Handling Patterns
7. Exception Handling Patterns
Classifying exceptions
Business process state
Reassigned Exception Handling Pattern
Allocated Exception Handling Pattern
Changing the Boundary Catch Event from Interrupting to Non-interrupting
Force-Terminate Exception Handling Pattern
Force-Error Exception Handling Pattern
Force-Complete Exception Handling Pattern
Invoked Exception Handling Pattern
Invoked State Exception Handling Pattern
Continue Execution Exception Handling Pattern
Force-Terminate Execution Exception Handling Pattern
Force-Error Execution Exception Handling Pattern
External Exception Handling Pattern
Process-Level Exception Handling Pattern
System-Level exception handling pattern
External Triggers
Summary
8
8. Adaptive Case Management
8. Adaptive Case Management
Defining adaptive case management
Exploring ACM use case scenarios
Case stage
Event pattern
Milestone pattern
Case interaction pattern
Localization feature
Holistic view pattern
Ad hoc feature
Summary
9
9. Advanced Patterns
9. Advanced Patterns
Strategic Alignment Pattern
Capturing the business context
Emulating Process Behavior
The Debugger feature
Round Trip and Business-IT Collaboration
Summary
10
A. Installing Oracle BPM Suite 12c
A. Installing Oracle BPM Suite 12c
Installing JDK
Installing BPM suite
Configuring the default domain
Enabling the demo user community
Custom domain creation
The BPM/SOA configuration
Summary
11
Index
Index

The parallel split and synchronization pattern

The parallel gateways are points in the process where multiple parallel paths are defined and they are also used to synchronize (wait for) parallel paths.

Parallel gateways represent concurrent tasks in business flows, and a fork gateway is always accompanied by a join gateway, where a fork gateway illustrates concurrent flows and expresses the fact that all outgoing paths must be pursued. On the other hand, a join synchronization gateway mandates that all the concurrent paths must be completed ahead of process advancement to subsequent tasks/activities.

A fork divides a path into two or more parallel paths and this is known as an AND split. It's the point in the process flow where activities can be performed concurrently rather than sequentially. In an OR gateway, one or another path is taken; however, in an AND gateway, a single thread of execution will be split into two or more branches that can execute tasks concurrently. For example, once an employee's on-boarding process has started, then enter the employee's information in the ERP system and also start the process for the provision of e-mail IDs, stationary, desk allocation, and so on in parallel.

Parallel split pattern

The following table shows the details of the parallel split pattern:

Signature

Parallel Split Pattern

Classification

Basic Flow Control Pattern

Intent

Breaks the flow into one of the two or more paths that execute concurrently.

Motivation

Fundamental constituent to the concurrent execution of two or more paths.

Applicability

Decision point in the business process where all the outgoing paths must be pursued.

Implementation

Widely adopted in most of the modeling languages using the AND split. When many activities have to be carried out at the same time and in any order, AND splits (parallel split) can be used to fork the concurrent flow where two or more concurrent threads independently process the activities (gateways, events, and so on) that reside on the corresponding control flow branches.

Known issues

NA

Known solution

NA

Synchronization pattern

The following table shows the details of the synchronization pattern:

Signature

Synchronization Pattern

Classification

Basic Flow Control Pattern

Intent

Synchronize paths that exit a parallel split.

Motivation

To synchronize the flow from multiple parallel branches. Parallel join merge exactly one thread from each incoming branch into a single thread on the outgoing branch by converging the threads of all the parallel branches.

Applicability

Merge point to synchronize the parallel paths. The AND join to be symmetrically paired up with a corresponding upstream AND split.

Implementation

Widely adopted in most of the modeling languages using the AND join.

Accepts multiple incoming sequence flow and blocks the sequence until all activities within the flows are completed; then, the flow continues. Till the concurrent tokens are not synchronized, multiple incoming sequence flows are blocked. Upon synchronization, one token is passed out of the merge gateway's outgoing flow.

Known issues

Nonavailability of a token at the AND join that got created from the AND split.

Known solution

The solution lies in how meticulously the process is modeled, and it's anticipated that the issue will not arise in a structured context.

Note

Design consideration by modelers is taken into account if you really need parallel processing, that is, whether, in reality, the distinct branches are executed in parallel.

Navigate to SalesQuoteDemo | SalesQuoteProject | ParallelSplitSynchronization process. When the sales quote is initiated, it halts for quote acceptance by the salesrep user at the ApproveQuote user task. Once it is approved, it's reviewed by business practice, and on approval from the fkafka user, the token reaches the parallel gateway, which is the divergent fork point. Both DealsApproval and TermsApproval need to be performed in parallel, and hence, the choice was a parallel gateway to diverge the flow. This is discussed in the following bullet points:

  1. Click on Organization Unit in the project to verify the user assignment to the roles. We will make sure that the user assignment to roles should happen based on following table:

    Task

    Role

    User

    Accept Quote

    Salesrep

    salesrep

    Business Review

    Business practice

    fkafka

    Approvers

    Approvers

    jcooper

    Contracts

    Contracts

    jstein

  2. If not already deployed, deploy SalesQuoteProject.
  3. Log in to EM console or use any tool of choice to execute the ParallelSplitSynchronization process using the ParallelSplitSynchronization.xml test data available in the testsuites folder in the project.
  4. Log in to the Oracle BPM workspace as the salesrep user and approve the AcceptQuote task.
  5. Log in to the Oracle BPM workspace as the fkafka user and approve the Business Practice Review task.
  6. Token has now reached the ApproveDeal and ApproveTerms task.
  7. Log in to EM console and check the Audit Trail of the process.

We can find that a group of threads is created for each sequence flow from the parallel gateway that forks/diverges the path. This is shown in the following screenshot:

Synchronization pattern

Check the process flow using the graphical view of the process in the process audit trail, as shown in the preceding screenshot. We can analyze that both the paths are processed in parallel. Execute the following steps:

  1. Log in to the BPM workspace as a jcooper user and approve the ApproveDeal task. We can notice that at the convergence point, that is, at the join (merge parallel gateway), tokens will be synchronized. Hence, the process waits for the other token to reach the convergence point, which is the AND join parallel gateway.
  2. Click on the process audit trail in EM for the process. We can witness that Approve Deal thread is completed, while the other thread for the Approve Terms is still processing.
  3. Log in to the BPM workspace as a jstein user and approve the Approve Terms task.
  4. Once both the tokens arrive at the AND join (Deals&TermsApproval_Merge) the tokens are synchronized, and one token is passed out of the merge gateway's outgoing flow.
End of Section 6
Next Section
bookmark search playlist download
font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY