SPAGIC

1
SPAGIC
The complete Free/Open Source SOA BPM Solution

• By
• Nawaz Khurshid
• LEGO- Lab(SOA Group) Fondazione Bruno Kessler

2
Objective

• . Integrate process in Enterprise Service Bus.
• . Implement the Integration architecture that
  support the routing,
• mediation and translation of these three basic
  layers.

3
SOA Reference Model

• Key points
• SOA/BPM Governance
• Full Open Source Model
• Product Independent

• Capabilities
• Efficiency of involved actors
• Reduce the gap between business analyst and
  technology specialist
• Business Process Monitoring and Management

4
Architecture

• JBI SA
• Other Orchestration Engine

MetaDB
BPEL
Workflow
Communication Layer

• ServiceMIX
• Open to other ESB

ESB Node
ESB node
ETL
JBI
BPM Layer
SOA/ESB Layer

• Apache ODE

5
An Open Platform
6
Standard

• BPMN Business Process Modeling Notation ( BPMN
  )
• STP IM Eclipse STP Intermediate Model
• ESB
• JBI Java Business Integration
• BPEL

7
BPMN

• Graphic Notation to design business processes
• Defined by OMG ( February 2006 )
• Actually there is no a standard for
  representing BPMN by XML
• It does not provide technological statements
• It must be enriched to be executed
• http//www.bpmn.org/

8
BPMN- Pool Lanes

• Pool Container of orchestration processes
• Lane Partitioning of a pool that represents
  a role, or a boundary of an organization unit

9
BPMN- Events
10
BPMN- Activities
11
BPMN- Flow Elements
12
BPMN- Gateway
13
BPMN- Artifact
14
STP- Intermediate model

• Eclipse Official Project
• Made collaborating with Eclipse
• Goals
• Define a generic model for processes and
  services
• Separate the design tools and the code
  generators
• Share the information between the different SOA
  technologies
• Interoperability between editors
• Conceptual transport between different
  development spaces.
• Capture common SOA design information.
• Possible incorporation of new editors.

15
Enterprise Service Bus

• There is no standard definition of ESB
• Sometimes its used as synonym of SOA
• Usually redefined by vendors according to the
  needs
• Architectural Model with enabling features
• Distributed Architecture
• Open Standard ( vs. Closed Standard )
• Transparent to the protocol
• Heavily based on XML and the standards WS-

16
JBI- Java Business Integration

• Decouples the applicative services from the
  connectivity management
• Binding Components (connectivity to external
  service)
• Service Engine (business logic and
  transformation services)
• Architectural model based on message exchange
  through a router
• Normalized Message Router

17
JBI- Binding Components/ Service Engines

• Binding Components ( Protocol Adapters )
• Responsible of protocol/trasport interactions
• Normalize and Denormalize the messages to and
  from different protocols formats ( Marshalling
  Unmarshalling )
• Examples HTTP/SOAP, Directory Poller, JMS
• Service Engine
• They implement the business logic
• They manage as input/output objects only the
  Normalized Message
• Examples XSLT Transformer, Query JDBC, Script

18
SPAGIC- Binding Components

• HTTP/SOAP
• CXF-BC (Celtix Xfire)
• File
• JMS
• Quartz Timer
• JDBC Poller
• TCP/IP
• Mail

19
SPAGIC- Service Engines

• XSLT Transformer
• Syntax Validator ( XSD Validator )
• validates payload against XSD schema.
• Drools Validator
• Rule, when and then construct.
• Drool file is provided to drool validator.
• Router
• construct for modeling gateways.
• select destination based on some rules on
  message content.
• Split Aggregator
• Parallel Join

20
Sample Drool File
21
SPAGIC- Service Engines

• Scripting
• groovy language
• JDBC Simple
• JDBC Advanced
• possibility to run stored procedures

22
Modeling Techniques
23

• Demo 1

• Syntax and Semantic Validation

24
Process 1
1.Receive a message 2.Perform Syntax
Validation. 3.If validation is OK 3.1. Perform
Semantic Validation 4. If validation is OK 4.1
Transform message. 5.End
25
BPMN
26

• Demo 2

• Invoking Supplier Web Service

27
Process 2

• 1.Receive a message
• 2.Make Script
• 3.Prepare input for Supplier Call.
• 4.Call Supplier Web Service
• 5.End

28
BPMN
29

• Demo 3

• Order Process
• Store Process

30
Order Process

• 1. Receive input.
• 2. Check Credit
• 2.1. Generate Invoice
• 2.1.1 End
• 2.2. Notify CRM System
• 2.2.2 End
• 2.3. Generate Input for Store Process
• 2.3.1 End

31
Store Process

• Receive Input from Order Process.
• Prepare Store Order
• Prepare data
• 3.1. Prepare data for Logistic
• 3.1.1 Invoke logistic service
• 3.2. Prepare data for supplier
• 3.2.1 Invoke supplier service
• 4. Display the combined output to console.

32
Order- Store Process store Process

• Receive Input from Order Process.
• Prepare Store Order
• Prepare data
• 3.1. Prepare data for Logistic
• 3.1.1 Invoke logistic service
• 3.2. Prepare data for supplier
• 3.2.1 Invoke supplier service
• 4. Display the combined output to console.

33
References
http//www.ibm.com/developerworks/library/ws-soa-d
esign1/ http//www.spagoworld.org http//www.bpmn.
org http//wiki.eclipse.org/STP_Intermediate_Metam
odel
34

• Thank you