View RSS Feed

jBPM

Overview of the JBoss jBPM architecture

Rate this Entry
by , 04-27-2012 at 05:45 PM (562 Views)
In jBPM, process definitions are packaged as process archives. A process archive is passed to the jPDL process engine for execution. The jPDL process engine traverses a process graph, executes defined actions, maintains process state, and logs all process events.

  • Process engine: This component executes defined process actions, maintains process state, and logs all process events via the following delegate components:


o A request handler
o A state manager
o A log manager
o A definition loader
o An execution service
  • Process monitor: This module tracks, audits, and reports the state of processes as they execute
  • Process language: The process definition language (jPDL) is based on GOP
  • Interaction services: These services expose legacy applications as functions or data to be used in process executions

Submit "Overview of the JBoss jBPM architecture" to Facebook Submit "Overview of the JBoss jBPM architecture" to Digg Submit "Overview of the JBoss jBPM architecture" to del.icio.us Submit "Overview of the JBoss jBPM architecture" to StumbleUpon Submit "Overview of the JBoss jBPM architecture" to Google

Comments