Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library 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 jBPM6 Developer Guide
  • Table Of Contents Toc
jBPM6 Developer Guide

jBPM6 Developer Guide - Third Edition

By : Salatino
2 (4)
Buy this Book
close
close
jBPM6 Developer Guide

jBPM6 Developer Guide

2 (4)
By: Salatino
Buy this Book

Overview of this book

If you are a Java developer or architect who needs to have a better understanding of how Business Process Management frameworks behave in real-life implementations, this book is for you. This book assumes that you know the Java language well and are familiar with some widely used frameworks such as Hibernate. You should also know the basics of relational databases and Maven-based applications.
Table of Contents (13 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Why Do We Need Business Process Management?
Icon
1. Why Do We Need Business Process Management?
Icon
Theoretical background
Icon
Introduction, analysis, and explanations of standard specifications
Icon
Technical details and common practices of jBPM6
Icon
The conceptual background of BPM
Icon
The BPM discipline
Icon
BPM applications in the real world
Icon
Summary
2
2. BPM Systems' Structure
Icon
2. BPM Systems' Structure
Icon
Components of a BPMS
Icon
Node instance structures
Icon
External interactions
Icon
Predictive analytics and decision management
Icon
Summary
3
3. Using BPMN 2.0 to Model Business Scenarios
Icon
3. Using BPMN 2.0 to Model Business Scenarios
Icon
Introduction to BPMN 2.0
Icon
Modeling business scenarios with BPMN 2.0
Icon
Technical perspective
Icon
Summary
4
4. Understanding the KIE Workbench
Icon
4. Understanding the KIE Workbench
Icon
What you need to start a jBPM6 environment
Icon
Summary
5
5. Creating a Process Project in the KIE Workbench
Icon
5. Creating a Process Project in the KIE Workbench
Icon
An IDE to our knowledge
Icon
Implementing our first process
Icon
Sprint management process design
Icon
The Web Process Designer advanced topics
Icon
Providing a runtime for our process
Icon
Summary
6
6. Human Interactions
Icon
6. Human Interactions
Icon
Understanding human interactions
Icon
jBPM6 Human task component's overview
Icon
Summary
7
7. Defining Your Environment with the Runtime Manager
Icon
7. Defining Your Environment with the Runtime Manager
Icon
Understanding the role of the runtime manager
Icon
The different implementations available
Icon
The UI configuration of runtime managers
Icon
Creating your own runtime manager
Icon
Summary
8
8. Implementing Persistence and Transactions
chevron up
Icon
8. Implementing Persistence and Transactions
Icon
Why do we need persistence and transactions?
Icon
Persistence in jBPM6
Icon
Other persistence mechanisms
Icon
Summary
9
9. Integration with Other Knowledge Definitions
Icon
9. Integration with Other Knowledge Definitions
Icon
What is a rule?
Icon
Old-fashioned integration
Icon
The Drools rule engine
Icon
Temporal reasoning and processes
Icon
Summary
10
10. Integrating KIE Workbench with External Systems
Icon
10. Integrating KIE Workbench with External Systems
Icon
Defining your architecture
Icon
Extending the KIE Workbench architecture
Icon
Remote engine invocations
Icon
Deploying the KIE Workbench in the cloud
Icon
Summary
11
A. The UberFire Framework
Icon
A. The UberFire Framework
Icon
UberFire
Icon
Extending and reusing the UberFire UI components
Icon
Summary
12
Index
Icon
Index

Why do we need persistence and transactions?

So far, we've dealt with very short-lived processes. Running inside a JUnit test, process instances last very few milliseconds, and having them in memory is sufficient for those environments. However, in real-life situations, we don't usually create interactions between systems and humans without having long wait states in between. This is especially relevant for the case of processes with human tasks, where users backed up with too much work might have a pending task assigned to them for hours, days, or even more. For each of the processes in your environment, you should be able to determine whether it should be a persistent or a nonpersistent process depending on how long-lived each of its process instances will be. From this perspective, you will find these two top-level categories:

  • In-memory processes

  • Long running processes (also known as persistent processes)

In-memory processes are usually short-lived processes that perform entirely automatic...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
jBPM6 Developer Guide
End of Section 8
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

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

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon