Case Studies: Lecture Delivered By: Hari Krishna S M

Lecture 25
Case Studies
Lecture Delivered By: Hari Krishna S M

harikrishna.cs.et@msruas.ac.in
1
Faculty of Engineering & Technology © Ramaiah University of Applied Sciences
Objectives
After completing this lecture, the students will be able to:

• State the need for composition of web services
• Explain the concept of Web Service Composition (WSC)
• Identify standards and techniques for WSC
• Identify Quality attributes for web services
• Apply WSC to provide dynamic services in enterprise solutions
2
Topics
• Case Studies
• Understanding the approaches
• Adaptation
3
Case Study: Application Integration
4
Telco Ecosystem User
3rd Party
Telco Enterprise User
Providers
User
• Service/content providers are often 3rd parties

• Telco is the intermediary for delivery of services to
enterprises/consumers
– Must improve ease-of-use of its software infrastructure
– Must optimize the utilization of its IT infrastructure
• Need to adopt standards-based framework
– Use Web services to build end-user services
– Use semantic annotations allowing service functionality to be
programmatically composed
5
Composed Service: Helpline Automation
Customer Interaction
Problem
Reporting
Top-down or bottom-up
Problem Ticket
Problem Location-based
Classification Agent Selection
Expert Lookup
Agent Assignment
Problem Ticket, Problem Ticket,
Desk-based Expert ID Field Expert ID
Call Message
Setup Delivery
Help Desk On Site
Problem Ticket, Problem Ticket,

Resolution Status Resolution Status
Registry
Update
Source: A Service Creation Tool Based on End-to-End Composition

of Web Services. V. Agarwal et al, WWW 2005
6
Creation of a new service
• Manual business process integration
New service • Use tools like WSAD-IE to create flows
capabilities Specify end-user
service capability and business logic
• Deploy using a flow engine (such as
New service MQWF / WBI SF)
providers Select service
providers
Main Issues
Network /
environment Design the Scalabilityof composition solution
changes flow Level of automation
Modeling domain information
Leverage industry practices

Deploy the
service
Source: A Service Creation Tool Based on End-to-End Composition of Web Services. V. Agarwal et al, WWW 2005
7
Case Study: Online Data Aggregation
8
Travel Reservation Problem
• Online information services

– Services are data sources; can be modeled as databases which can be queried with no, or controlled, side-effects
– Composite service should be responsive but accuracy can be negotiated
– Services are heterogeneously owned, hence relatively autonomous in choosing specifications
Source: Getting from Here to There:. Interactive Planning and Agent. Execution for Optimizing Travel. José Luis Ambite et al, IAAI 2002
9
Source: Getting from Here to There:. Interactive Planning and Agent. Execution for Optimizing Travel. José Luis Ambite et al, IAAI 2002
10
A Framework for Understanding WSCE
11
A Model for WSCE*
• An Overall Web Service Composition and Execution view is important in

practice
Specification
of Requirement
Available
Capabilities Web Service
Events Composition and Execution
Execution Trace
[ Templates,
Policies ]
Today, it is not clear what are fundamentally different possible

types of WSCE approaches and which type to use in
a given scenario? *Services are assumed to be stateless
12
Basis for WSCE approaches
• Are composition and execution separable?
– No, Yes
• When does composition happen?
– Offline, Online
• How does composition happen?
– Search-based, Template-based
• What information is used for composition?
– Service types, Service instances published, Services
deployed, Templates/ Policies
• How are external events handled at runtime
(adaptation)?
– On-the-fly, gradual
13
Interleaved Approach
X={x1,x2,…x} Events
Specifications
Search-based
Composition Execution
T=
{t1,t2,…t}
On-line
Example: ConGolog, Heracles+Theseus

14
14
Faculty of Engineering
Faculty of Engineering && Technology
Technology ©
©Ramaiah UniversityofofApplied
Ramaiah University Applied Sciences
Sciences
Monolithic Approach
 ≥
I={i1, i2,… i} X={x1,x2,…x} Events
FRE
Specifications
Monolithic Runtime
Composition
T=
RIW {t1,t2,…t}
REW
W={W1,W2,…WL}
Off-line On-line
Example: SWORD, SHOP-2 based, Petrinet-based, Astro, METEOR-S

15
15
Technology ©
Sciences
Staged Approach
  ≥
C={c1,c2,…c} I={i1, i2,… i} X={x1,x2,…x} Events
FPC FRE
Logical Physical Runtime
Specifications
Composition Composition
RAW T=
RIW {t1,t2,…t}
REW
S={S1,S2,…SK} W={W1,W2,…WL}
Off-line Off-line On-line
Example: Synthy, Self-Serv with web communities (but informal modeling)

16
16
Technology ©
Sciences
Template-based Approach: Creation
of a Template
Interleaved
T= {t1,t2,…t}
Traces
Templates
Monolithic
W={W1,W2,…WL}
Executable Workflow
Staged
S={S1,S2,…SK}
Abstract Workflow
Generalize: remove commitments to get templates
17
Usage of a Template
Interleaved
T= {t1,t2,…t}
Traces
Monolithic
Templates
W={W1,W2,…WL}
WSCE
Executable Workflow
Staged
S={S1,S2,…SK}
Abstract Workflow
Add commitments to generate
workflow or trace
(Assign values to template parameters)
Example: Heracles+Theseus, METEOR-S (Semantic templates, other templates),

template-based planning
18
•
Basis for WSCE approaches
Are composition and execution separable?
– No, Yes
• When does composition happen?
– Offline, Online
• How does composition happen?
– Search-based, Template-based
• What information is used for composition?
– Service types, Service instances published, Services deployed, Templates/ Policies
• How are external events handled at runtime (adaptation)?
– On-the-fly, gradual
Separable? When How What How
Interleaved No Online Search Services deployed On-the-fly
Monolithic Yes Offline Search Services instances published Gradual
Staged Yes Offline Search Service types, Service instances Gradual

published
Template Yes Offline, Online Template Templates/ policies, Services On-the-fly, Gradual
instances published, deployed
19
Comparing Approaches
Interleaved Monolithic Staged Template
O(βλ)
Composition Effort O(λ) O(αλ + Mλ) O(Mλ )
Min: O(λ)
High:
Low: High:
Composition Control None <template, underlying
< RIW; FE > < RAW;RIW; FC; FE >
composition method>
Ability to Handle
None Low High Low
Composition Failure
Adaptation during
High Medium Medium Low to Medium
Execution
Information Simple Elaborate (Types and Elaborate (Templates

Simple (Instances)
Modeling (Instances) Instances) and Instances)
Search restricted by
Always a time-lag Always a time-lag template – can cause
Search should be between service between service INCOMPLETENESS; Any
Limitation dead-end free information offline v/s information offline restriction of the
online v/s online underlying composition
method
Details in: Understanding approaches for web service composition and execution,
Vikas Agarwal, Girish Chafle, Sumit Mittal, Biplav Srivastava, ACM COMPUTE 2008
20
Two Common Web Service Composition
and Execution (WSCE) Scenarios
• Online information services
– Services are data sources; can be modeled as databases which can be queried with no, or controlled,
side-effects
– Sub-scenarios:
• Comparison product review/ shopping sites, Online travel booking
• Mash-ups: ad-hoc data services created by users
• Enterprise Application Integration
– Services are applications; can be modeled as programs with or without side-effects
– Composite service should accurate but responsiveness can be negotiated
– Services are more homogeneously owned (e.g., intranet); hence some control in choosing
specifications can be exercised
– Sub-scenarios:
• Service creation to connect internal or partner organizations
• Scientific workflows: bioinformatics, Geological sciences
21
Selecting an Approach for Online
•
Scenario
Online information services
– Services are data sources; can be modeled as databases which can be queried with controlled
side-effects at the time of purchase
O(βλ)
Min: O(λ)
High:
Low: High:
composition method>
Composition Failure
None Low High Low
Resolution
Adaptation High Medium Medium Low to Medium
Elaborate (Types and Elaborate (Templates and

Information Modeling Simple (Instances) Simple (Instances)
Instances) Instances)
Search restricted by template

Always a time-lag between Always a time-lag between – can cause
Search should be dead-
Limitation service information offline v/s service information offline INCOMPLETENESS; Any
end free
online v/s online restriction of the underlying
composition method
22
Selecting an Approach for EAI
Scenario
 Scalability – with number of services
 Adaptability – to changes
 Failure Resolution
 User Interaction – control and supervision important
O(βλ)
Min: O(λ)
High:
Low: High:
composition method>
Composition Failure
None Low High Low
Resolution
Adaptation High Medium Medium Low to Medium
Elaborate (Types and Elaborate (Templates and

Information Modeling Simple (Instances) Simple (Instances)
Instances) Instances)
Search restricted by template

Always a time-lag between Always a time-lag between – can cause
Search should be dead-
Limitation service information offline v/s service information offline INCOMPLETENESS; Any
end free
online v/s online restriction of the underlying
composition method
23
Myth – WSC is Planning and Readily
Solvable!
• Resolve scale-up and search issues, and WSC will be solved with existing, or incrementally enhanced,
planners
• WSC has much commonality with Planning
– Services are Actions
– Side-affects and inputs/ outputs can be modeled as preconditions/ effects
– Use existing or favorite new methods
• Many research papers but not many wide-scale systems
– Success in generating compositions
– But generation is one thing, execution another
• How to prove composition is correct at runtime?
• Are middleware available to execute?
• Can domain models be built by typical IT professionals?
• Anecdote –
– Planner4J family of Java planners: Classical, Metric and Contingent planners in three different composition systems
– Never encountered a composition situation where the scalability of the planner was an issue!
– More work on making planner integratable with external systems
• Automatic Parameter Turning (AAAI 05)
• Analyzing plans (IAAI05)
• Validating input domain and problem models (ISWC 2005)
• Generating diverse plans (IJCAI 07)
• Reachability analysis to identify potentially relevant services from a large repository
• See AAAI06 Nectar paper for details
Planner4J: http://domino.research.ibm.com/comm/research_people.nsf/pages/biplav.Planner4J.html
24
Reality – Why is WSC not Solved as yet?
• Modeling domain is hard

– Which expert to believe? Companies in monopolistic
situations (e.g. Windows, SAP) have easier time.
– Can domain models be built by typical IT
professionals?
– What is the right level of abstractions?
• Handling runtime
– How to prove composition is correct at runtime?
– Are middleware available to execute?
• Tooling
25
Summary
• IT Issues Faced by Businesses Today
• Web Services Composition is very important
– Model for looking at WSC
– Case Studies
• Progress in automated WSC
– Myth: Resolve scale-up and search issues for WSC composition
– Reality: Resolve composition set-up issues (at problem set-up or
solving phases)
26

Case Studies: Lecture Delivered By: Hari Krishna S M

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Case Studies: Lecture Delivered By: Hari Krishna S M

Uploaded by

Copyright:

Available Formats

Lecture 25

Lecture Delivered By: Hari Krishna S M

After completing this lecture, the students will be able to:

• Service/content providers are often 3rd parties

Help Desk On Site

Problem Ticket, Problem Ticket,

Source: A Service Creation Tool Based on End-to-End Composition

Modeling domain information

Leverage industry practices

• Online information services

• An Overall Web Service Composition and Execution view is important in

Today, it is not clear what are fundamentally different possible

Example: ConGolog, Heracles+Theseus

Example: SWORD, SHOP-2 based, Petrinet-based, Astro, METEOR-S

Off-line Off-line On-line

Example: Synthy, Self-Serv with web communities (but informal modeling)

Generalize: remove commitments to get templates

Example: Heracles+Theseus, METEOR-S (Semantic templates, other templates),

Separable? When How What How

Interleaved No Online Search Services deployed On-the-fly

Monolithic Yes Offline Search Services instances published Gradual

Staged Yes Offline Search Service types, Service instances Gradual

Information Simple Elaborate (Types and Elaborate (Templates

Interleaved Monolithic Staged Template

Elaborate (Types and Elaborate (Templates and

Search restricted by template

Interleaved Monolithic Staged Template

Elaborate (Types and Elaborate (Templates and

Search restricted by template

• Modeling domain is hard

You might also like