Book Image

OSWorkflow: A guide for Java developers and architects to integrating open-source Business Process Management

Book Image

OSWorkflow: A guide for Java developers and architects to integrating open-source Business Process Management

Overview of this book

OSWorkflow is an open-source workflow engine written entirely in Java with a flexible approach and a technical user-base target. It is released under the Apache License. You can create simple or complex workflows, depending on your needs. You can focus your work on the business logic and rules. No more Petri Net or finite state machine coding! You can integrate OSWorkflow into your application with a minimum of fuss. OSWorkflow provides all of the workflow constructs that you might encounter in real-life processes, such as steps, conditions, loops, splits, joins, roles, etc.This book explains in detail all the various aspects of OSWorkflow, without assuming any prior knowledge of Business Process Management. Real-life examples are used to clarify concepts.

Related Content you might be interested in

Current Title:

Small book image
OSWorkflow: A guide for Java developers and architects to integrating open-source Business Process Management
Aug, 2007 | 212 pages
No titles found
Table of Contents (13 chapters)
OSWorkflow
OSWorkflow
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
Introduction
Introduction
Free Chapter
1
BPM and Workflow Basics
BPM and Workflow Basics
Business Process Orientation
What's a BPMS?
Different Kinds of BPMS
Components of a BPM Solution
Open-Source BPMS
Summary
2
OSWorkflow Introduction and Basics
OSWorkflow Introduction and Basics
Downloading and Installing OSWorkflow
Navigating the Sample User Interface
OSWorkflow Basics
Setting Status and Old Status Values
Visual Process Modeling
Ways to Implement OSWorkflow
Summary
3
Adding Code to our Definitions
Adding Code to our Definitions
How to Deal with Transient Data
PropertySet and Transient Variables
Adding Code to our Definition
Other Useful Descriptor Concepts
Summary
4
Using OSWorkflow in your Application
Using OSWorkflow in your Application
OSWorkflow Configuration
Embedding OSWorkflow into your Application
Persisting Instance Information
Unit Testing your Workflow
Integrating with Spring
Workflow Security
Summary
5
Integrating Business Rules with JBoss Rules
Integrating Business Rules with JBoss Rules
Incorporating Business Logic into Business Processes
Simple Logic with Conditional Results
Complex Business Logic
Integrating with OSWorkflow
Summary
6
Task Scheduling with Quartz
Task Scheduling with Quartz
What is Quartz?
Trigger Functions
Scheduling a Job
Scheduling from a Workflow Definition
JobStores
Example Application—Customer Support
Example Application—Claims Processing
Summary
7
Complex Event Processing
Complex Event Processing
Complex Event Processing (CEP)
What is Esper?
Integration with OSWorkflow
Real-World Examples
Summary
8
Dashboards with Pentaho
Dashboards with Pentaho
What is Pentaho?
Pentaho Requirements
Downloading and Installing Pentaho
Setting up Pentaho to use the OSWorkflow Database
Using the Design Studio to Create our First Chart
Useful Charts for BAM Consoles
Summary

JobStores

The JobStore interface designed in Quartz is responsible for the persistence and retrieval of all job and trigger data. There are two built-in implementations of the JobStore interface, the RamJobStore and the JDBCJobStore.

The RamJobStore stores the job, trigger, and calendar data in memory, losing its contents after JVM restarts. On the other hand, JDBCJobStore uses the JDBC API to store the same data.

The JDBCJobStore uses a delegate to use specific functions of each database, for example, DB2, PostgreSQL, etc.

The JobStore configuration is located in the quartz.properties file. To set the JobStore, add the following line to the configuration file, if you want to use the RamJobStore:

org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore

The configuration of the JDBCJobStore is a little more complex as it involves datasources, transactions, and delegates:

To use local JDBC transactions, you only need to set the following parameters:

org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore...
Previous Section
End of Section 6
Next Section