![Page 1: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/1.jpg)
METEOR-S Project Entry for SWS Challenge Phase II
Using Planning for Process Mediation
John Harney, Karthik Gomadam, John Miller, Amit Sheth, Kunal Verma, Zixin Wu
LSDIS Lab,
University of Georgia
![Page 2: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/2.jpg)
The problem of Process Mediation
Client Service Provider
I want to do
something
I can give you
these
Mediator
This is how to do it.
First step, second step,
etc.
![Page 3: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/3.jpg)
Process Mediation –SWS Challenge 2006
![Page 4: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/4.jpg)
Using Planning in Process Mediation• Planning Problem
– Find an execution path of services (tasks) given some state of the world to achieve a goal
– Classical planning algorithms use combinatorial search, backtracking and branching to secure a plan
Plan
No Plan
No Plan
![Page 5: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/5.jpg)
Using Planning in Web Service Composition• Planning Problem
– With many operations available, planning using these techniques:
• Becomes computationally complex (at times infeasible)
• Gives less desirable plans
– Need a method that alleviates planner complexity and retrieves “smart” plans
![Page 6: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/6.jpg)
Interaction Protocol Approach for Process Mediation
Client Service Provider(s)
Mediator
InteractionProtocol
Requirement
CreateInteractionProtocol
Planning
Execute
Validation
WSDL-S
![Page 7: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/7.jpg)
Interaction Protocol Approach for Process Mediation• Bottom-up (Process Synthesization)
– Construct a plan given:• Client’s requirements
i.e. preconditions/input, postconditions/output (goals)• Provider’s available operations (preconditions/input,
effects/output)• “Pseudo”-operations – combined operations
determined by the provider; encapsulate human knowledge.
![Page 8: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/8.jpg)
Interaction Protocol ApproachConsists of four phases:
1. Client presents requirements via semantic template
2. Provider creates a (set of) valid pseudo-operations
3. Planner synthesizes processes using provider defined interaction protocol (pseudo-operations) as well as other operations
4. Final plan validated and used by consumer (final BPEL process is deployed)
![Page 9: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/9.jpg)
Compose the solution on the fly
Constraints for planning come from:
1.Semantic requirements (preconditions, post-conditions, input, and output ) from the client (WSDL-S)
2.Precondition, effect, input, and output from the providers (WSDL-S)
3.Interaction protocol from the providers
![Page 10: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/10.jpg)
Interaction Protocol Approach• Client’s requirements can be captured in
Semantic Template (WSDL-S)
For the SWS Challenge 2006:
<wsdl:operation name="sendPO"> <wssem:precondition expression="haveCompanyInfo"/>
<wsdl:input message="impl:PIP3A4POR"/><wssem:postcondition expression="completeOrder ^ closeOrder"/>
</wsdl:operation>
![Page 11: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/11.jpg)
Interaction Protocol ApproachBesides the semantic annotation for “regular”
operatioins, Service Provider specify the Interaction Protocol which is a set of pseudo-operations
<wssem:interactionProtocol><wssem:pseudoOperation name="placeOrder">
<wssem:precondition expression="haveCustomerID"/><wsdl:input message="impl:PlaceOrderRequestMessage"/><wsdl:output
message="impl:CloseOrderResponseMessage"/><wssem:effect
expression="haveOrderID^completeOrder^closeOrder"/><wssem:process>
mooncompany:OMServicePortType:createNewOrder ; mooncompany:OMServicePortType:addLineItem * ; mooncompany:OMServicePortType:closeOrder
</wssem:process></wssem:pseudoOperation>
</wssem:interactionProtocol>
![Page 12: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/12.jpg)
Interaction Protocol Approach• Planner uses GraphPlan algorithm
– Represents possible plans using expandable graph data structure
– Alternating layers of ground literals and actions (ground instances of operators)
– Represents the literals and actions that might occur at each time step
– Attempts to extract plan when goal level of literals is reached
![Page 13: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/13.jpg)
Interaction Protocol Approach
• GraphPlan example (Preconditions -> “A ^ B” Goal -> “E”)– If preconditions exist for operation:
• Operation placed in sequential path• Effects of operation placed in new state
– Expansion continues until goal is reached– Plan is composed by backtracking to the initial level through
operationsInitial state Goal
literal
operation
A
O1
O1
O2
O1
O2
O3
O4
A
B
C
D
E
A
B
C
D
B
A
B
C
Plan → O1,O2,O4
![Page 14: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/14.jpg)
Interaction Protocol Approach• Graphplan Example with pseudo-operations
– Pseudo-operations reduce graph complexity (execution path length, number of actions, etc) with human defined super-operations
Initial state
Goal
literal
Atomic operation
Psuedo operation
O4
O3
O1
O2
A
CC
D
B
AA
B
C
D
E
PO1
Plan → PO1, O4
![Page 15: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/15.jpg)
Interaction Protocol Approach• GraphPlan extended
– Must also check whether output of one operation semantically matches the input of the next operation in sequence
• Need to refer both to ontology
InputOutputO1 O2
![Page 16: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/16.jpg)
Interaction Protocol Approach• GraphPlan extracts a sequential “backbone”
execution path that can be converted to BPEL– Includes pseudo-operation conversion
Plan w/ IP
PO1
O4
O1
O2
O4
Plan w/ Atomic Operations
BPEL
<Invoke O1>
…
<Invoke O2>
<Invoke O3>
…
![Page 17: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/17.jpg)
Service Provider 2 (POM)
Create
Add
Close
authToken
Contact
shipTo
billTo
orderId
authToken
orderId
item
orderId
lineItemId
authToken
orderId
orderId
ItemNo
SearchCustomer
CompanyName
CustId
Service Provider 1 (CRM)• Solution
– Process synthesized using client’s requirements and internal planning.
– Service provider provides pre-defined pseudo operations to make planning easier.
![Page 18: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/18.jpg)
Architecture
![Page 19: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/19.jpg)
Demo
• Open ProcessMediator.swf in IE or Firefox (requires Flash)
• Inputs:– Client Template: Blue_SemanticTemplate.wsdls– Provider Services: CRMService.wsdls,
OMService.wsdls
• Output– generatedProcess.bpel
![Page 20: METEOR-S Project Entry for SWS Challenge Phase II Using Planning for Process Mediation](https://reader035.vdocuments.site/reader035/viewer/2022062422/56812e01550346895d9361c4/html5/thumbnails/20.jpg)
The EndThanks