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.
Table of Contents (13 chapters)
OSWorkflow
Credits
About the Author
About the Reviewers
Introduction

Setting up Pentaho to use the OSWorkflow Database


In this section, we will create a bridge between OSWorkflow and Pentaho BI. By using the OSWorkflow Workflow instance database as a data source in Pentaho, we'll have all this process information available for reporting and charting, thereby allowing us to spot trends and monitor the business process visually.

Remember that the Pentaho integrated distribution we downloaded is based on the JBoss application server. Well, this enables us to define a JBoss data source that Pentaho can use to access the OSWorkflow database.

The following XML is the data source definition file for JBoss; the file can have any name as long as it ends with the -ds suffix and has the XML extension. For example, osworkflow-ds.xml is a suitable name. This file must be placed in the deploy directory of the Pentaho JBoss server.

<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>solution1</jndi-name>...