5. Middleware / System Integrations
In the university we learn:
There is no intention to handle the concept
of human interaction in these 3/N Layers.
6. Middleware / System Integrations
When we start doing system integration
we forget about people completely.
Obviously we cannot do only system integrations,
because if not there will be no systems to integrate.
Example: BPEL 1.0 - Pure WS interactions
7. Middleware / System Integrations
We need the concept of Human Interaction
when we are doing System Integrations...
Y U NO USE IT??
18. BPMn2
• Graphical and formal language to describe business
situations
• Standard shared between different vendors
• It’s not just another XML file
• High Level syntax and execution semantics defined
by the spec
• Its a bridge between analysts and developers
24. WS-HT (in JBPM5)
jBPM5 provides an implementation of the WS-HT spec
• It’s a decoupled component
• It can be reused by any application
• It’s shared between different domains and integrated
with your company components
• It integrates easily with existing user directories
• No need to use business process if you don’t want to
27. TASK LIST ORIENTED UIs
Some advantages:
• Unified access to all the integrated systems:
• No need to use more than one system
• Unified concepts to interact with the system:
• Tasks will be shown as they become relevant to each role
• Easy to understand and follow
• Very similar to the concept of inbox in our email clients
• Can be prioritized depending on business requirements
28. BPMS
After some implementations...
Applying these generic concepts we save a lot of time,
but we don’t get domain specific tools
It’s never enough ...