Transcript Semantic Business Process Management - the SUPER project Presenters ■ Agata Filipowska (PUE) ■ Barry Norton (KMI) ■ Carlos Pedrinaci (KMI) ■ Dumitru Roman (STI Innsbruck) Santa Clara, USA, April.

Semantic Business
Process Management
- the SUPER project
Presenters
■ Agata Filipowska (PUE)
■ Barry Norton (KMI)
■
Carlos Pedrinaci (KMI)
■
Dumitru Roman (STI Innsbruck)
Santa Clara, USA, April 2008
Acknowledgement & Copyrights
■
This material is based upon works supported by the EU under the
SUPER project (FP6 - 026850)
■
Material Preparation
► KMI: John Domingue, Carlos Pedrinaci, Barry Norton
► Poznan University: Agata Filipowska
► IAAS, University of Stuttgart: Dimka Karastoyanova, Jörg Nitzsche, Tammo van Lessen, Zhilei
Ma, Frank Leymann, Branimir Wetzstein
► IDS Scheer: Sebastian Stein
► DERI Innsbruck: Michael Stollberg
► DERI Galway: Armin Haller, Maciej Zaremba
► Ontotext: Marin Dimitrov
© by the SUPER project consortium
© SUPER
© SUPER 24.04.2020
24.04.2020
OASIS Symposium 2008
2
Tutorial outline
■ Motivation for the Semantic Business Process
Management (SBPM)
■ Ontologies and Semantic Web Services
■ Methodology for SBPM
■ Architecture of a sBPM System
► Process deployment
► Process execution
■ Demonstration
► SUPER tooling
► Modelling and Execution (TID Use Case)
► Composition (TP Use Case)
© SUPER 24.04.2020
OASIS Symposium 2008
3
Introduction to BPM
Vision, Strategy, and Models
Vision
What are we doing
Define the right
things to do
Strategy
Business Process
Do the right things
right
Adapted from: John L. Barrett, “Process Visualization: Getting the Vision Right Is Key,”
Information Systems Management, 1994, pp. 14-23.
© SUPER 24.04.2020
OASIS Symposium 2008
5
Business Process
“A process is simply a structured, measured set of activities
designed to produce a specific output for a particular
customers or market.” -- Thomas Davenport
Characteristics:
■ Why?
► What are the assumptions?
► How would changing the assumptions affect the work and its value?
■ Who?
► Is a shop floor worker performing the task?
► Do we need a technical specialist?
■ When?
► Are we finishing the machine by tomorrow?
■ Where?
► Is the work performed in our plant in Russia?
■ What?
► Is the inventory sufficient?
► What machine is involved, what software is needed?
© SUPER 24.04.2020
OASIS Symposium 2008
6
Business Processes in a
Company
Business Processes
■
… drive all company‘s activities
■
… represent the core assets of a
company
■
… give decision makers control over
the company’s activities
■
… deliver services faster and more
efficiently to the customer
■
… allow a company to react to
changing market conditions
How do I
get the big
picture
about my
activities?
How do I
communicate
my business
processes in a
common
fashion?
How do I keep
track of all
evolutions in my
businesses?
How do I make
sure my
businesses get
more efficient
and more
profitable?
© SUPER 24.04.2020
OASIS Symposium 2008
7
Practicing Business Processes
Practicing business processes requires
■
… methodologies and tools
■
… detailed understanding of all activities enterprise-wide
■
… an optimized design, monitoring and control and optimized
■
… information gathering / requirement analysis in form of processes
■
… extracting insights from already modeled and executed processes to
optimize and reengineer
© SUPER 24.04.2020
OASIS Symposium 2008
8
BPM - challenges
What are my services?
© SUPER 24.04.2020
OASIS Symposium 2008
10
What are my services?
© SUPER 24.04.2020
OASIS Symposium 2008
11
What are my services?
© SUPER 24.04.2020
OASIS Symposium 2008
12
Querying the Process Space
© SUPER 24.04.2020
OASIS Symposium 2008
13
The Critical IT / Business Divide
© SUPER 24.04.2020
OASIS Symposium 2008
14
The Critical IT / Business Divide
© SUPER 24.04.2020
OASIS Symposium 2008
15
Matching Activities and Port Types
Based on Semantics
Semantic Web Services
© SUPER 24.04.2020
OASIS Symposium 2008
16
Matching Model Representations &
Semantics
© SUPER 24.04.2020
OASIS Symposium 2008
17
Modelling Stack
·
·
·
Making sense of a domain\problem
Communication tool
What is it all about?
·
·
·
·
Service
Booking
form
Flight data
Receipt
booking
request
Check
booking
request
Mrs. Miller
Call
center
Booking
request
checked
Service
Flight
disposition
Service
Alternative
flight
offer
Booking
request
Mrs. Walker
Create
flight
booking
Plane
ticket
Flight
booking
created
Client data
Offer
alternative
flight
·
·
·
·
Visualizing\specifying business process
Focus: Business Problem
Who does what, when, how and why?
Usually multiple layers
·
·
·
·
Process execution specification
·
Formal, clearly specified grammar
·
Focus: Implementation
Which component is called when, how, by
whom with which data?
·
·
·
Web service encapsulation
Focus: Implementation
Which components can and should be
exposed how as services?
·
·
WS*
...
·
Implementation of components
·
·
Programming languages
...
Service
Mr. Green
Flight
disposition
Alternative
flight
offered
<process name="Mediation Example - Ordering BPEL Snippet - 1" suppressJoinFailure="yes" targetNamespace="...">
<sequence>
<receive name="Initial_Receive" createInstance="true"/>
<invoke name="Invoke_Check_Order_Consistency"/>
<switch>
<case condition="bpws:getVariableData('consistency', '') = 'OK'">
<flow>
<invoke name="Invoke_Update_Provisioning_Systems_Subprocess"/>
<invoke name="Invoke_CustomerReply_Confirmation_Note"/>
</flow>
</case>
<otherwise>
<invoke name="Invoke_CustomerReply_Rejection_Note"/>
</otherwise>
</switch>
<reply name="Final_Reply"/>
</sequence>
</process>
© SUPER 24.04.2020
OASIS Symposium 2008
·
·
Solution maps
Mind maps
Ad-hoc modelling
techniques
...
·
·
·
Business Scenario Maps
Event-driven process
chains
Flowchart techniques
BPMN
...
BPEL
...
18
Ontologies and
Semantic Web
Services
Barry Norton, Dumitru Roman,
Michael Stollberg
Outline
■ Introduction
► The need of semantics for realizing the SOA vision
► SWS – Tasks to be Automated
■ The WSMO Approach
► Top-Level Entities: Ontologies, Goals, Web services, Mediators
► The specification language WSML
■ Semantic Execution Environments
► Reference Ontology
► Reference Architecture
► Concrete Architectures – WSMX and IRS-III
© SUPER 24.04.2020
OASIS Symposium 2008
2020
The Web Service Usage Process
web-based SOA as new system design paradigm
points to
WSDL
Repository
describes
find usable
Web Service
Consumer
Web
Service
SOAP
WS usage via message exchange
© SUPER 24.04.2020
OASIS Symposium 2008
21
Some deficiencies of WS technology
■ Current technologies allow usage of Web
Services
■ But:
► only syntactical information descriptions
► syntactic support for discovery, composition and execution
=> Web Service usability, usage, and integration needs to be inspected
manually
► no semantically marked up content / services
► no support for the Semantic Web
=> Current Web Service Technology Stack did not
realize the promise of Web Services
© SUPER 24.04.2020
OASIS Symposium 2008
22
SWS – Tasks to be automated
Describe the
service
explicitly, in a
formal way
Invoke & Monitor
services following
programmatic
conventions
Service
Description
Service
Enactment &
Monitoring
Service
Publishing
Service
Mediation
Service
Composition
Combine
services to
achieve a goal
© SUPER 24.04.2020
Make available
the description
of the service
Locate different
services
suitable for a
given goal
Service
Discovery
Service
Negotiation &
Contracting
OASIS Symposium 2008
Choose the
most
appropriate
services among
the available
ones
23
SWS Usage Process
Request
submission
matchmaking
R with all WS
Discoverer
Data
Mediator
uses
uses
if: directly
usable
Process
Mediator
else: try other WS
if: composition
needed
Composer
uses
uses
Communication
Conformance
uses
Service
Repository
composition
(executable)
else: try other WS
if: compatible
if: successful
else: try other WS
Executor
information lookup
for particular service
if: execution
error
© SUPER 24.04.2020
OASIS Symposium 2008
24
So what is needed?
■ Semi-automated support is needed for
► Annotating/designing services and the date they use
► Finding and comparing service providers
► Negotiating and contracting services
► Composing, enacting, and monitoring services
► Dealing with numerous and heterogeneous data formats, protocols and
processes, i.e. mediation
=> Conceptual Models, Formal Languages,
Execution Environments
© SUPER 24.04.2020
OASIS Symposium 2008
25
The WSMO Approach
WSMO, WSML,
WSMO4J, WSMO Studio
The WSMO Approach
A conceptual model for SWS
A formal language for WSMO
A modeller for WSMO and editor
for WSML
A object model for WSMO and parsing for WSML
© SUPER 24.04.2020
OASIS Symposium 2008
27
The Web Service Modeling Ontology
(WSMO)
Design Principles
Web Compliance
Strict Decoupling
Centrality of Mediation
Ontology-Based
WSMO
Ontological Role Separation
Execution Semantics
Description versus Implementation
© SUPER 24.04.2020
OASIS Symposium 2008
28
Top-level elements defined by WSMO
(http://www.wsmo.org)
Objectives that a client
may have when consulting
a Web Service
Provide the
formally
specified
terminology of the
information used
by all other
components
Semantic description of
Web Services:
- Capability (functional)
- Interfaces (usage)
Connectors between
components with mediation
facilities for handling
heterogeneities
© SUPER 24.04.2020
OASIS Symposium 2008
29
WSMO – the Ontology element
■ Ontology elements:
► Concepts - set of concepts that belong to the ontology
►Attributes - set of attributes that belong to a concept
►
►
►
►
►
Relations - define interrelations between several concepts
Instances - set of instances that belong to the represented ontology
Axioms - axiomatic expressions in ontology (logical statements)
Non-functional properties
Imported ontologies - importing existing ontologies where no heterogeneities
arise
► Used mediators - ontology import with terminology mismatch handling
■ Ontologies - used as the ‘data model’ throughout WSMO
► all WSMO element descriptions rely on ontologies
► all data interchanged in Web Service usage are ontologies
► Semantic information processing & ontology reasoning
© SUPER 24.04.2020
OASIS Symposium 2008
30
WSMO – the Web service element
© SUPER 24.04.2020
OASIS Symposium 2008
31
The big challenges of defining a WSMO
service
■ Capabilities
► What is a service able to do?
► What are the requirements on the input and output?
 Preconditions, Assumptions, Postconditions and Effects need to
be defined.
■ Interfaces
► How can a service be accessed?
► How does a service solve its task?
 Choreography and Orchestration of services need to be defined.
© SUPER 24.04.2020
OASIS Symposium 2008
32
WSMO – Goals, Mediators
■ Goals
► Defined in a similar way as WSMO Web services
■ Mediation
► Data Level - mediate heterogeneous Data Sources
► Protocol Level - mediate heterogeneous Communication Patterns
► Process Level - mediate heterogeneous Business Processes
■ WSMO Mediators:
► OO Mediators - terminology import with data level mediation
► WW Mediators - enable interoperability of heterogeneous Web Services
► WG Mediators - link a Web Service to a Goal and resolve occurring
mismatches
► GG Mediators – Support specs of goals by reusing exiting goals
© SUPER 24.04.2020
OASIS Symposium 2008
33
WSMO and the other SWS approaches
© SUPER 24.04.2020
OASIS Symposium 2008
34
OWL-based Web service ontology
(OWL-S)
■ Conceptual Model
► A set of ontologies used to
describe different aspects SWS
■ Language: OWL
■ Some OWL-S drawbacks
► OWL not sufficiently expressive for all aspects of a service
►more expressive languages have been syntactically integrated:
SWRL, KIF, DRS, and PDDL – how do these languages
interoperate?
► Inherits some of the drawbacks of OWL (e.g. lack of proper layering,
improper use of OWL for describing and reasoning about processes)
► No explicit support for Mediation in the language
© SUPER 24.04.2020
OASIS Symposium 2008
35
Semantic Web Services Framework
(SWSF)
■ Two major components: an ontology and a language
used to axiomatize it
■ Semantic Web Services Ontology (SWSO) – an
extension of OWL-S conceptual model, e.g. a rich
behavioural process model based on PSL
► FLOWS – First-Order Logic Ontology for Web Services
► ROWS - Rule Ontology for Web Services
■ The Semantic Web Services Language (SWSL)
► SWSL-FOL - based on First Order Logic; includes features from HiLog and FLogic
► SWSL-Rules - a logic programming language; includes features from Courteous
logic programs, HiLog, and F-Logic
■ Some SWSF drawbacks
► unclear how all the paradigms part of this approach work together
► first-order logic ontology for Web services, but not a Web language
© SUPER 24.04.2020
OASIS Symposium 2008
36
The Web Service Modelling Language
(WSML)
■ Ontology / Rule Languages
►
►
►
►
WSML
WSML Core: efficiency and compatibility
WSML DL: decidability, open world semantics
WSML Rule: efficient existing rule engines
WSML Full: unifying language, theorem proving
■ Languages for dynamics
WSML Full
► Transaction Logic over ASMs
■ Mapping languages
Dynamic
Aspects
Static
Aspects
WSML Rule
WSML DL
WSML Core
► for dynamics (process mediation)
► for data (data mediation)
RDF (S)
XML
Unicode
© SUPER 24.04.2020
OASIS Symposium 2008
URI
37
WSML – relation to SW
standards
© SUPER 24.04.2020
OASIS Symposium 2008
38
WSMO/WSML – Some Modelling
Examples
■ Concept example
concept phoneNumber
nonFunctionalProperties
dc#description hasValue "concept of a
phone number"
endNonFunctionalProperties
countryCode ofType _string
areaCode ofType _string
number ofType _string
■ Sub-concept example
concept mobilePhoneNumber subConceptOf
phoneNumber
nonFunctionalProperties
dc#description hasValue "concept of a
mobile phone number"
endNonFunctionalProperties
mobileProvider ofType Provider
© SUPER 24.04.2020
• Relation example
relation hasRoute(ofType routeDescription, ofType route)
nonFunctionalProperties
dc#description hasValue "Relation that holds between
a route description and a route"
endNonFunctionalProperties
■ Instance example
instance myPhoneNumber memberOf phoneNumber
countryCode hasValue “43“
areaCode hasValue “664“
number hasValue “49322607“
■ Axiom example
axiom ValidInformationQuality
definedBy
forall {?x} (
?x memberOf informationQualityType
implies
?x[value hasValue “low“] or
?x[value hasValue “high“]).
OASIS Symposium 2008
39
WSMO/WSML – Some Modelling
Examples (cont’)
webService _"https://asg-platform.org/AttractionBooking/MobtelPhoneLocationService"
nfp
dc#title hasValue "MobtelPhoneLocationService"
dc#publisher hasValue "Mobtel“
dO#informQualityType hasValue "high"
endnfp
importsOntology _"https://asg-platform.org/AttractionBooking/domainOntology.wsml"
capability MobtelPhoneLocationServiceCapability
sharedVariables {?P}
precondition
definedBy
?P memberOf dO#phoneNumber.
postcondition
definedBy
?L memberOf dO#location
and
dO#hasLocation(?P,?L).
interface MobtelPhoneLocationServiceInterface
choreography MobtelPhoneLocationServiceChoreography
stateSignature
in
dO#phoneNumber withGrounding
ssWSDL#wsdl.interfaceMessageReference(MobtelPhoneLocationServicePortType/doIt/In)
out
dO#location withGrounding
ssWSDL#wsdl.interfaceMessageReference(MobtelPhoneLocationServicePortType/doIt/Out)
transitionRules
forAll{?P} with (?P memberOf dO#phoneNumber) do
add(?L memberOf dO#location and dO#hasLocation(?P,?L))
endForall
© SUPER 24.04.2020
OASIS Symposium 2008
40
Semantic Web Services – Summary
■ The WSMO Approach to SWS
► Covers many aspects of SWS; unifying approach
► Large-scale ongoing initiative supported by both industry and
academia
■ Standardization activities are emerging in this area
► OWL-S, SWSF, WSDL-S, WSMO – submitted to W3C
► OASIS SEE technical committee formed (based on WSMX)
► SAWSDL – a W3C recommendation
■ More collaboration is needed between research community
and the industrial community
■ The biggest challenge for the future: the movement to
service-orientation and the semantic enablement of
industrial scale infrastructures and applications
■ STI International: http://sti2.org/
© SUPER 24.04.2020
OASIS Symposium 2008
41
Semantic Execution
Environments
Reference Ontology, Reference
Architecture, Concrete Architectures
Semantic SOA Reference Ontology
■ Defined by Semantic Execution Environment
Technical Committee1 at OASIS
■ Derives from SOA Reference Model (SOA-RM),
now an OASIS specification
■ Extends to semantic features, informed by
existing ad hoc ‘standards’
■ Formally defined as an ontology
► using WSML in order to enable…
1
http://www.oasis-open.org/committees/semantic-ex/
© SUPER 24.04.2020
OASIS Symposium 2008
43
Semantic SOA Reference Architecture
■ Reference Architecture (RA) components can be formalised in
terms of WSML goals
■ Entry points, and lightweight component definitions, can be
defined as WSML services with orchestrations over these goals
© SUPER 24.04.2020
OASIS Symposium 2008
44
Semantic SOA RA Broker Components 1
■ Knowledge bases:
► Goals for ‘create/retrieve/update/delete’ (CRUD) operations on
ontological definitions
■ Service registry:
► Goals for CRUD operations on web services, goals and
mediator definitions
■ Logical reasoner:
► Goals for evaluation of logical expressions over ontological
definitions; free variables provide basic query interface
© SUPER 24.04.2020
OASIS Symposium 2008
45
Semantic SOA RA Broker Components 2
■ Discovery:
► Query interface for service definitions; submit a goal and instance
data, receive candidate services (optionally with mediation
requirements)
■ Selection:
► Submit candidate goals and ontological basis to judge between them
and receive best candidate
■ Composition:
► In case discovery is unsuccessful, re-submit goal and, if possible,
receive a new composite service
© SUPER 24.04.2020
OASIS Symposium 2008
46
Semantic SOA RA Broker Components 2
■ Data Mediation:
► Mediate between different ontological representations of data,
e.g. service consumer’s information model in goal and service
provider’s in web service
■ Process Mediation:
► Mediate between different behaviours, e.g. service consumer’s
process model in goal choreography and service provider’s in
web service choreography
© SUPER 24.04.2020
OASIS Symposium 2008
50
Mediation
■ Heterogeneity…
► mismatches on structural / semantic / conceptual / level
► occur between different components that shall interoperate
► especially in distributed & open environments like the Internet
■ Concept of Mediation (Wiederhold, 94):
► Mediators as components that resolve mismatches
► declarative approach:
► semantic description of resources
► ‘intelligent’ mechanisms resolve mismatches independent of content
► mediation cannot be fully automated (integration decision)
■ Levels of Mediation within Semantic Web Services:
1.
2.
3.
4.
Representation Level:
Data Level:
Functional Level:
Process Level:
© SUPER 24.04.2020
heterogeneous Languages & Protocols
heterogeneous Data Sources
heterogeneous Functionalities
heterogeneous Communication Processes
OASIS Symposium 2008
51
Data Mediation Techniques
■ resolve semantic mismatches between
terminologies
■ realized by ontology integration
► mappings between heterogeneous ontologies (design time)
► data transformation (runtime)
Ontology Mapping
Ontology Alignment
Mapping
Rules
Ontology A is made
compatible to ontology B
© SUPER 24.04.2020
Ontology Merging
OASIS Symposium 2008
52
Mapping Language Example
Ontology O2
Ontology O1
Person
Human
- name
- age
- name
Adult
Child
michael memberOf Person
- name = Michael Stollberg
- age = 28
classMapping(unidirectional o2:Person o1.Adult
attributeValueCondition(o2.Person.age >= 18))
this allows to transform the instance ‘michael’ of concept person in
ontology O2 into a valid instance of concept ‘adult’ in ontology O1
© SUPER 24.04.2020
OASIS Symposium 2008
53
Semantic SOA RA Broker Components 3
■ Choreography Execution:
► In on-the-fly process mediation the goal and service
choreographies are executed
► With pre-mediated processes a ‘client choreography’ is
executed
■ Orchestration Execution:
► To execute a composite service its orchestration is executed
(in SUPER this is handed off to an external process engine)
© SUPER 24.04.2020
OASIS Symposium 2008
62
Semantic SOA RA Broker Components 4
■ Grounding:
► The ontological representation of data is ►lifted from syntactic representations (e.g. XML)
►lowered into syntactical form
■ Transport:
► In order to communicate with brokered services, many
transport mechanisms are interfaced by a SEE
© SUPER 24.04.2020
OASIS Symposium 2008
63
Semantic SOA Concrete Architectures
■ Semantic SOA Reference Model can be mapped to
WSMO
■ Semantic SOA Reference Architecture
Components and Entry Points can be expressed
as an API in WSMO4J
■ Two implementations exist for this API, therefore
two WSMO-compliant SEEs:
► WSMX – open source reference implementation
► IRS4BPM – builds on existing IRS and OCML toolsets and PSM
libraries
© SUPER 24.04.2020
OASIS Symposium 2008
64
The SUPER
methodology
SUPER Methodology Framework
Strategic Semantic Business
Process Management
MULTI-DOMAIN
SPECIFIC DOMAIN
Semantic
Business Process
Analysis
Text
Semantic
Business Process
Modelling
Text
SOLUTIONS MAPS
YATOSP-eTOM
Others
Others
Semantic
Business Process
Execution
Semantic
Business Process
Configuration
Text
Ontological Foundation
© SUPER 24.04.2020
OASIS Symposium 2008
66
SBP Modelling
Semantic
Business Process
Modelling
Text
Text
© SUPER 24.04.2020
OASIS Symposium 2008
67
SBP Configuration
Text
Text
Semantic
Business Process
Configuration
Text
© SUPER 24.04.2020
OASIS Symposium 2008
68
SBP Execution
© SUPER 24.04.2020
Text
Semantic
Business Process
Execution
OASIS Symposium 2008
Text
Text
69
SBP Analysis
Semantic
Business Process
Analysis
Text
Text
Text
© SUPER 24.04.2020
OASIS Symposium 2008
70
Architecture of the
SUPER sBPMS
Architecture Static View
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution
Environment
Modelling
Tool
Monitoring
Tool
Mining
Tool
SUPER Tooling
Semantic Service Bus
Deployment Component
Composition
Discovery
Mediation
SUPER
platform
services
Semantic
Web
Services
Execution
History
Business
Process
Library
SUPER Repositories
Translation
© SUPER 24.04.2020
OASIS Symposium 2008
72
Deployment Process: Semantic Process
Artefacts Bundle (SPAB)
BPEL4SWS
WSDL
WSMO
WSDL
WSMO Mediators
WSMO
Goals
Deployment
descriptor
© SUPER 24.04.2020
OASIS Symposium 2008
73
Deployment Process
S PAB
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution
Environment
WSDL
SUPER
platform
services
WSMO
Mediators
WSMO
Deployment
Deployment Component
Goals
Descriptor
Mediation
Semantic
Web
Services
Translation
SUPER Repositories
Discovery
© SUPER 24.04.2020
Mining
Tool
SUPER Tooling
BPEL4SWS
WSDL Bus WSMO
Semantic Service
Composition
Modelling Monitoring
Tool
Tool
Execution
History
OASIS Symposium 2008
Business
Process
Library
74
Semantic Business Process Execution
Mediation
Request to
Service
SUPER
platform
services
Web
Service
1
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution Environment
© SUPER 24.04.2020
Semantic
Web
Services
Execution
History
SUPER Repositories
OASIS Symposium 2008
75
Semantic Business Process Execution
Mediation
Request to
Service
SUPER
platform
services
Web
Service
1
2
Achieve Goal
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution Environment
© SUPER 24.04.2020
Semantic
Web
Services
Execution
History
SUPER Repositories
OASIS Symposium 2008
76
Semantic Business Process Execution
Mediation
Request to
Service
SUPER
platform
services
Web
Service
1
2
Achieve Goal
3 Discover Service
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution Environment
© SUPER 24.04.2020
Semantic
Web
Services
Execution
History
SUPER Repositories
OASIS Symposium 2008
77
Semantic Business Process Execution
Mediation
Request to
Service
SUPER
platform
services
Web
Service
4 Invoke Service
1
2
Achieve Goal
3 Discover Service
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution Environment
© SUPER 24.04.2020
Semantic
Web
Services
Execution
History
SUPER Repositories
OASIS Symposium 2008
78
Semantic Business Process Execution
Mediation
Request to
Service
SUPER
platform
services
Web
Service
4 Invoke Service
1
2
Achieve Goal
5 Return result to engine
3 Discover Service
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution Environment
© SUPER 24.04.2020
Semantic
Web
Services
Execution
History
SUPER Repositories
OASIS Symposium 2008
79
Semantic Business Process Execution
Mediation
Request to
Service
1
6
SUPER
platform
services
Web
Service
4 Invoke Service
Return Result
2
Achieve Goal
5 Return result to engine
3 Discover Service
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution Environment
© SUPER 24.04.2020
Semantic
Web
Services
Execution
History
SUPER Repositories
OASIS Symposium 2008
8080
SUPER Tool Support
Architecture Static View
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution
Environment
Modelling
Tool
Monitoring
Tool
Mining
Tool
SUPER Tooling
Semantic Service Bus
Deployment Component
Composition
Discovery
Mediation
SUPER
platform
services
Semantic
Web
Services
Execution
History
Business
Process
Library
SUPER Repositories
Translation
© SUPER 24.04.2020
OASIS Symposium 2008
82
The Web Service Execution Environment
(WSMX)
■ A software framework for runtime binding of service
requesters and service providers
■ WSMX interprets service requester’s goal to
►
►
►
►
discover matching services
select (if desired) the service that fits best
provide mediation (if required)
make the service invocation
■ Is based on the conceptual model provided by WSMO
■ Has a formal execution semantics
■ SO and event-based architecture based on microkernel
design using technologies as J2EE, Hibernate, JMX, etc.
© SUPER 24.04.2020
OASIS Symposium 2008
83
WSMX Motivation
■ Provide middleware ‘glue’ for Semantic Web Services
► Allow service providers focus on their business
■ Provide a reference implementation for WSMO
■ Provide an environment for goal based service discovery
and invocation
► Run-time binding of service requester and provider
■ Provide a flexible Service Oriented Architecture
► Add, update, remove components at run-time as needed
■ Keep open-source to encourage participation
► Developers are free to use in their own code
■ Define formal execution semantics
► Unambiguous model of system behaviour
© SUPER 24.04.2020
OASIS Symposium 2008
84
WSMX Design Principles
Strong Decoupling & Strong Mediation
autonomous components with mediators for interoperability
Interface vs. Implementation
distinguish interface (= description) from implementation (=program)
Peer to Peer
interaction between equal partners (in terms of control)
WSMO Design Principles == WSMX Design Principles
== SOA Design Principles
© SUPER 24.04.2020
OASIS Symposium 2008
85
WSMX Components
Internet
Internet
Peer
Message
Vertical Services e.g. Security
Message
Execution Management
End User Tools
Developer Tools
Problem Solving Layer
Discovery
Adaptation
Composition
Data Mediation
Process
Mediation
Communication
(external)
Fault Handling
Choreography
Monitoring
Application Services Layer
Storage
Message
Message
Peer
Reasoning
Base Services Layer
© SUPER 24.04.2020
OASIS Symposium 2008
86
WSMX Architecture
WSMT – Web Services Modeling Toolkit
WSMX Managment
Ontology Visualizer
Mapping Tools
Service
Providers
Administration Framework Interface
System Interface
Adapter 2
...
Adapter n
Data and Communication Protocols Adapters
Adapter 1
Agent
acting on
behalf of
service
requester
WSML Editor
WSMX
Service
Requesters
Back-End
Application
WSMX Monitor
WSMX Manager
WSMX Manager Core
CM
Wrapper
RM
Wrapper
Parser
Wrapper
Discovery
Wrapper
Selector
Wrapper
DM
Wrapper
PM
Wrapper
Choreography
Wrapper
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Communication
Manager
Resource
Manager
Parser
Discovery
Selector
Data
Mediator
Process
Choreography
Mediator
Invoker Receiver
Resource Manager Interface
© SUPER 24.04.2020
Web
Service 2
...
Web
Service p
Grounding
WSMO Objects
Web
Service 1
Reasoner Interface
Non WSMO
Objects
Reasoner
Component
Wrapper
Interface
New
Component
OASIS Symposium 2008
87
WSMX Usage Scenario
© SUPER 24.04.2020
OASIS Symposium 2008
88
Summary WSMX
■
■
■
■
■
Conceptual model is WSMO
End to end functionality for executing SWS
Has a formal execution semantics
Real implementation
Open source code base at SourceForge
http://sourceforge.net/projects/wsmx/
■ Event-driven component architecture
© SUPER 24.04.2020
OASIS Symposium 2008
89
IRS - III
The Internet Reasoning Service is an infrastructure for
publishing, locating, executing and composing Semantic
Web Services
© SUPER 24.04.2020
OASIS Symposium 2008
90
Design Principles
■ Ontological separation of User and Web Service
Contexts
■ Capability Based Invocation
■ Ease of Use
■ One Click Publishing
■ Agnostic to Service Implementation Platform
■ Connected to External Environment
■ Open
■ Complete Descriptions
■ Inspectable
■ Interoperable with SWS Frameworks and Platforms
© SUPER 24.04.2020
OASIS Symposium 2008
91
Features of IRS-III
■
■
■
■
■
Based on Soap messaging standard
Provides Java API for client applications
Provides built-in brokering and service discovery support
Provides capability-centred service invocation
Publishing support for variety of platforms
► Java, Lisp, Web Applications, Java Web Services
■ Enables publication of ‘standard code’
► Provides clever wrappers
► One-click publishing of web services
■ Integrated with standard Web Services world
► Semantic web service to IRS
► ‘Ordinary’ web service
© SUPER 24.04.2020
OASIS Symposium 2008
92
IRS-III Framework
IRS-3 Server
Lisp
IRS Publisher
Java
O
Web Service Specifications
+ Registry of Implementors
S
Domain Models
IRS Publisher
IRS Publisher
A
Goal Specifications
+ SOAP Binding
Java WS
P
IRS Publisher
SOAP
IRS Client
© SUPER 24.04.2020
OASIS Symposium 2008
93
IRS-III Architecture
WSMO
Studio
Browser
Publishing
Clients
Invocation
Client
WSMX
J
a
v
a
A
P
I
© SUPER 24.04.2020
Web Service
Publishing Platforms
Java Code
Web Application
S
O
A
P
SOAP
Browser
Handler
Publisher
Handler
SOAP
Handler
Invocation
Handler
WS Publisher
Registry
OCML
WSMO Library
IRS-III Server
LispWeb Server
OASIS Symposium 2008
94
WSMO Studio
■ Integrated Service Environment for WSMO
■ Provide easy to use GUI for various WSMO tasks
► Working with ontologies
► Creating WSMO descriptions: goals, services, mediators
► Creating WSMO centric orchestration and choreography
specifications
► Import (export) from (to) various formats
► Front-end for ontology and service repositories
► Front-end for runtime SWS environments (WSMX, IRS-III)
■ Provides BPMO modelling
■ http://www.wsmostudio.org
© SUPER 24.04.2020
OASIS Symposium 2008
95
Editing a Goal in WSMO Studio
© SUPER 24.04.2020
OASIS Symposium 2008
96
WSMO Studio view onto IRS-III
© SUPER 24.04.2020
OASIS Symposium 2008
97
BPMO modelling
© SUPER 24.04.2020
OASIS Symposium 2008
98
Demonstration
Modelling Demonstration
■ We will model a business process that allows clients to
purchase digital content
■ In detail, we will…
► model the business process using the BPMO plug-in of WSMO Studio
► execute the BPEL4SWS process in a BPEL engine using a web client
► monitor process execution using a web-based process monitoring tool
© SUPER 24.04.2020
OASIS Symposium 2008
100
BPMO Modeling
■ The business process is modeled in BPMO and
uses a BPMN-like graphical notation
■ Semantic Annotation: WSMO Goals are
attached to the tasks of the process
■ After modeling:
► Process composition takes place
► BPMO definition is transformed into sBPEL
► sBPEL is serialized as BPEL4SWS and deployed to the SBPEL
engine
© SUPER 24.04.2020
OASIS Symposium 2008
101
Purchase Digital Content Process
© SUPER 24.04.2020
OASIS Symposium 2008
102
Purchase Digital Content Process
Web
Client
© SUPER 24.04.2020
OASIS Symposium 2008
103
Example - Client Process
© SUPER 24.04.2020
OASIS Symposium 2008
104
Example – Process Response
■ Result of the Execution of the Purchase Content Process
© SUPER 24.04.2020
OASIS Symposium 2008
105
Purchase Digital Content Process
BPEL4SWS
Process
© SUPER 24.04.2020
OASIS Symposium 2008
106
BPEL4SWS Process
■
The Content Purchase Process
© SUPER 24.04.2020
OASIS Symposium 2008
107
BPEL4SWS Process
<b4s:conversations>
<b4s:conversation b4s:name="Packager" b4s:goalURI="http://www.ip-super.org/ontologies/prereview#goalGetURL" />
<b4s:conversation b4s:name="LicenseServer" b4s:goalURI="http://irs.open.ac.uk/superPrereview#goalGetLicense" />
</b4s:conversations>
<sequence sa:modelReference="http://www.ip-super.org/ontologies/prereview#actServiceProvision">
<receive name="receiveContentRequest“
sa:modelReference="http://www.ip-super.org/ontologies/prereview#recContentRequest"
partnerLink="ServiceProvider"
portType="spwsdl:ServiceProviderPortType" operation="requestContent"
variable="contentRequest" createInstance="yes" />
<flow sa:modelReference="http://www.ip-super.org/ontologies/prereview#actFlow_1">
<extensionActivity>
<b4s:invoke name="invokeGoalGenerateLicense"
modelReference="http://www.ip-super.org/ontologies/prereview#actInvokeGoalGenerateLicense"
b4s:inputVariable="contentRequest" b4s:outputVariable="contentURL"
b4s:conversation="Packager" />
</extensionActivity>
<extensionActivity>
<b4s:invoke name="invokeGoalGenerateURL"
modelReference="http://www.ip-super.org/ontologies/prereview#actInvokeGoalGenerateURL"
b4s:inputVariable="contentRequest"
b4s:outputVariable="contentLicense"
b4s:conversation="LicenseServer" />
</extensionActivity>
</flow>
<reply> … </reply>
</sequence>
© SUPER 24.04.2020
OASIS Symposium 2008
108
TID’s Purchase Digital Content Process
SWS
(WSMX)
SWS
(IRS-III)
© SUPER 24.04.2020
OASIS Symposium 2008
109
Process model
BPMO
Ontology
BPMO Editor
© SUPER 24.04.2020
OASIS Symposium 2008
110
BPMO Process Description
wsmlVariant _"http://www.wsmo.org/wsml/wsml-syntax/wsml-flight"
namespace { _"http://www.ip-super.org/ontologies#" }
ontology Customer_Order_Fullfillment
namespace {_"http://www.ip-super.org/ontologies/BPMO#",
TPDomainOntology _"http://www.ip-super.org/ontologies/TP#"}
importsOntology
_"http://www.ip-super.org/ontologies/BPMO"
_"http://www.ip-super.org/ontologies/TP"
instance TPSA_Customer_Order_Fullfillment memberOf Process
hasWorkflow hasValue Sequence1
instance OrderDetailsConfirmation memberOf Task
hasWSMOGoal hasValue _"http://www.ip-super.org/ontologies# OrderDetailsConfirmationGoal"
// …
instance Sequence1 memberOf Sequence
hasOrderedElement hasValue {OrderedElement11, OrderedElement12}
instance OrderedElement11 memberOf OrderedElement
hasOrder hasValue 1
hasElement hasValue OrderDetailsConfirmation
// …
© SUPER 24.04.2020
OASIS Symposium 2008
111
Process Composition
Process model
WS registry
© SUPER 24.04.2020
OASIS Symposium 2008
112
Process Deployment
■ Deployment bundle contains:
► BPEL4SWS process
► WSDL description of the process
► Deployment descriptor (Process name -> WSDL service)
■ We assume that…
► The two WSDL Web Services are already deployed in Tomcat (Axis)
► Corresponding WSMO Goals and WSMO SWS are already deployed to
WSMX/IRS-III
© SUPER 24.04.2020
OASIS Symposium 2008
113
Process Execution
■
■
■
■
■
Process is started from a Web client
BPEL engine navigates through the process model
WSMO Goals are passed to the SEE implementations
After discovery, SEE invokes the WSDL Web Services
BPEL Engine and SEE publish events, which are
displayed by a web-based monitoring tool
© SUPER 24.04.2020
OASIS Symposium 2008
114
Semantic Business Process Execution
Web
Service
Request to
Service
1
6
Return Result
2
5
4
Invoke Service
Achieve Goal
Return result to engine
3
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
SUPER Execution Environment
© SUPER 24.04.2020
Discover Service
Semantic
Web
Services
Execution
History
SUPER Repositories
OASIS Symposium 2008
115
http://www.ip-super.org