# Proxy Abstract Services and dynamic composition: create services using abstract classes and annotations without providing any implementation.
# Annotation inheritance, create your customs annotations from the corea annotations.
# Compose your service workflows graphically using the jBPM native support.
# Implement services using Java or Ruby.
# 100% Annotation based configuration (plus .properties files for externalization).
# Can be used as a standalone container, in a web environment or integrated with other containers.
# Spring native support (Spring/Spring MVC).
# Testing support integrated within the framework using static Assert classes.
# Monitor and manage the services through JMX (status, start, stop...).
# Spring native support (Spring/Spring MVC).
# Maven plugin.
# Several embedded services are provided out of the box and ready to use.
jBPM (Java Business Process Management) is an open source Java framework for managing workflows.
This project provides:
* A simple standalone Eclipse project for checkout and experimentation
* Example jBPM integration with Hibernate, Spring, and Oracle XE (a free download)
* Simple JUnit tests for leaning by doing
* A companion powerpoint presentation in the downloads section
* How-Tos in this Wiki
Runa WFE is an environment for JBoss jBPM workflow engine. It is a cross-platform end user solution for business process development and execution. Together Runa WFE and JBoss jBPM provide an easy to use business process management system.
Runa WFE is an open source project.
What is this project
Runa WFE provides:
* an end user GUI to define business processes without any coding: draw flowcharts, define roles and variables, lay out forms
* an end user GUI to load and execute processes
* an administrative interface to create and remove users/groups and grant rights
* a possibility of writing automatic "bots" that can participate in business processes
* a possibility to code new GUI elements, variable types, organizational structure functions etc. that extend existing Runa WFE components and will be available to end users through the GUI
Runa WFE makes it possible to integrate your diverse enterprise applications in a unified system, by using "bots" that run inside "bot stations".
nexusBPM is an open-source enhancement of JBoss's jBPM product suite. We have added many features to both the editor and the engine.
nexusBPM provides en enhanced editor experience with a variety of preconfigured nodes such as FTP, SQL, Excel and others. All nexusBPM nodes can participate in dataflow which is very easy to use. Using dataflow means that information created by one node can be used by another for processing, formatting, output or decision making. The nexusBPM editor can even communicate with the nexusBPM server andsupports drag and drop upload and download capabilities as well as remote run commands.
nexusBPM provides an enhanced engine with support for scheduling flows using quartz, executing nexusBPM nodes using message driven beans and custom commands.
Open Source the BPMspace product is free to use, open for extensions and independent of its owners
Agile BPMspace processes can be easily adapted to the frequent changes in real life
Relational BPMspace relates business process objects (of different kinds) to each other, similar to records in different tables of a relational database.
In contrast to most database applications, the BPMspace data model (ontology) can be extended at runtime, without development effort.
Business Process Warehouse BPMspace maintains a repository of integrated process data, available for all types of queries, analysis, monitoring and (business) performance management
Business process management (BPM) – while also its own independent practice / school of thought – is an application of technology that is served by many products, not the least of which is jBPM. The best definition of BPM that I've found is: "Business Process Management (BPM) is the concept of shepherding work items through a multi-step process. The items are identified and tracked as they move through each step, with either specified people or applications processing the information. The process flow is determined by process logic and the applications (or processes) play virtually no role in determining where the messages are sent.".