5. Technologies
• Base software assets
– Liferay Portal Server [www.liferay.com]
– Activiti BPM Platform [www.activiti.org]
– Sesame2 Ontology Server [www.openrdf.org]
– Jasig Central Authentication Service [www.jasig.org/cas]
• Leveraged open standards
– Business Process Model and Notation (BPMN) 2.0
[www.omg.org/spec/BPMN/2.0]
– Resource Description Framework (RDF)
[www.w3.org/RDF]
5
10. COMPEL Motivation
Multidisciplinary teams (gap)
• Roles
• Business Analysts
vs
• Service Integrators
• Disperse Knowledge
• Domain specific business
processes and conceptualisations
vs
• SOA-based technologies: WS*,
WSDL, UDDI, SOAP, XML/XSD,
JAX-WS APIs, etc
11. COMPEL BPM limitations
Technical limitations
• Discoverability/Advertising
• Very limited uptake of IoS
• Obsolete service registries (UDDI)
• Incorporating new trends in SoC/IoS: ROA, REST,
Mashups, etc.
• BPM vs SOA composition
languages
• BPMN vs BPEL
• Standard graphical
notation
• Technology and
tooling complexity
12. COMPEL Challenges
Scaling to the Web of Services (IoS)
Web 2.0 Crowd-sourcing
Assisted (automated) BPM at design and run time
• Automating discovery:
• Exact vs approximate
matchmaking
• Automating work and data
flow
• Dynamic runtime
• Late binding, rebinding, self*
capabilities (healing,
compensation, etc)
13. COMPEL The solution
• COMPEL is an open and multiplatform solution
to design business processes (BPMN, BPEL) by
aggregation of SOA based services.
• Processes are designed by business analysts. The
processes and their tasks are defined using their
domain vocabulary (process semantics).
• For each task, Light Semantic Composition
suggests the most matching services as far as
description is concerned and the user makes his
choice.
• The services are located in a centralised
repository where providers register and describe
them semantically
13
14. COMPEL The editor
• Coarse‐grain light semantics for
– Task description, Process description, requirements,
preferences, context
• Domain ontology based annotations
• Exact and approximate dynamic discovery
• Semi‐automatic late binding
• Automated data flow generation and executable BPMN
generation
• Registry for process annotations and service descriptions
• Execution of the business process (through GUI & REST
API)
14