Information Technology Reference
In-Depth Information
Most ESBs provide an integration with jBPM6 by means of two different frameworks:
Spring ( http://www.spring.io ) , a framework for component integration and initialization,
and Camel ( http://camel.apache.org ), a framework for service interconnection through en-
dpoint declarations. Both (Spring and Camel) are supported by most of the latest ESB
tools, and the KIE projects provide two projects to expose KieSessions through both
the aforementioned frameworks: kie-spring and kie-camel .
The full picture could be a combination of process interactions (for services and human
tasks) and the BPM system and service interactions wrapped with the ESB; this allows
different system providers to just worry about writing new services, new processes, or
new versions of both.
The business process flows will describe how the work is being done in the company and
not the technical details required for sending information from one place to another. This
is later provided by the actual implementation of WorkItemHandlers in the runtime
configuration; this is possible thanks to the semantics proposed by business process mod-
eling languages such as BPMN2, which will be introduced in Chapter 3 , Using BPMN 2.0
to Model Business Scenarios .
Business experts appear in this scenario as users of the BPM systems in the roles of busi-
ness process creators, editors, and auditors. Meanwhile, other roles don't need to interact
with the processes nor the services, but only with the tasks assigned to them. In a scenario
like this, it is the process's responsibility (and not the responsibility of specific applica-
tions) to access the services and exchange information with them through Service tasks, a
component we will see in detail in Chapter 3 , Using BPMN 2.0 to Model Business Scen-
arios .
Search WWH ::




Custom Search