What email address or phone number would you like to use to sign in to Docs.com?
If you already have an account that you use with Office or other Microsoft services, enter it here.
Or sign in with:
Signing in allows you to download and like content, and it provides the authors analytical data about your interactions with their content.
Embed code for: A Novel Method And Environment for Scalable Web Services Orchestration(SERVICES2016-6036)
Select a size
Venkatesan Devanathan & Sridhar Sundaramoorthy Associate Professors , Anna University – Chennai INDIA
SERVICES2016-POSTER Session-1 – A Novel Method And Environment for Scalable Web Services Orchestration (Session Chair: Dr.Nour Ali, University of Brighton, U.K)
Paper Id: SERVICES2016-6036
Date: 27-June-2016 Room/Place: StanfordTime : 9:20 AM -9:40 AM
A Novel Method And Environment for Scalable Web Services Orchestration (Based on WS-Addressing & BPEL Technologies)
Venkatesan Devanathan &
Associate Professors ,
Anna University – Chennai
Presently web services COMPOSITION is based on specific hardcoded URI /WSDL files
This approach retains flavor of age-old TIGHTLY COUPLED client-server technology
Problems faced by an application composed of EXTERNAL services:
Service address migration/ versioning / scalability
Any INFRASTRUCTURE based solution?
HOW One CONSUMER application -- compose (say) PROVIDER services of same kind --running on several NODES?
Example--How sensor network controller or IOTs controller App.– can be architected – using services technology?
based solution help here?
What happens to a CONSUMER application – that compose a PROVIDER service – using its WSDL –and the provider service FAIL to show up after a while (say few years down the line)?
Can a CONSUMER application – that want to compose ANY one PROVIDER service of a PARTICULAR KIND– like – airTicket booking service-- say based on QoS, Cost,
Example :—I want my App. to play TERMINATOR-3
streaming video - from any streaming service - that has
Any INFRASTRUCTURE based
solution help here?
Any INFRASTRUCTURE based solution for web-services composition that is INHERENTLY loosely-coupled?
So that CONSUMER Apps. can achieve Non-functional capabilities : scalability, separation, modifiability, integrability , portability, performance, reliability, ease of creation and reusability
Like XML-SOAP separated consumer & provider platform integration issue;
Like WSDL abstracted & separated implementation from interface definition;
We propose Speech-act message based identification of PARTNER-LINKS embedded inWS-Addressing messages --SENT to a proxy like intermediary /middleware --to connect with PLs
This proxy is called “OPEN INTERACTION MIDDELWARE SERVICES (OIMS)”
PROPOSED SOFTWARE ENVIRONMENT & ARCHITECTURE
What is a “Speech-Act”?
Messages as operationally interpreted linguistic commands –called “Performatives”– Pragmatics oriented - Example: ask, tell, demand, reject …
While Composing a service by consumer App.- use speech act to identify/denote a Provider EPAMessages -not use syntactic URI.
Example: -IEEE/FIPA standard based speech-act:
(<<speech-act-type>> :sender <<sending-WebService-Id>> :receiver <<receiver WebService Id/description>> :content
<<action-specification such WS input, output, preferred partner specs.- cost/QoS..>> :ontology <<adopted-ontology-type in CONTENT>>
:sa-msg-id : <<message-Id>> :in-reply-to <<conversation-Id>> )
To simplify EPA encoding , server can provide a OIMS message template – that facilitate speech-act encoding of a service EPA – by consumer App.
Tech. details of proposed SOLUTION
How to deal with state based Provider/Consumer services applications?
How to add described Loose-coupling semantics to regular orchestration languages like WS-BPEL (that can have very complex semantics)
Instead of WS-BPEL, should we try this first on micro-services composition frameworks?
Which tool/platform? – Apache ODE/LSQ micro/or what else…?
SOME BASICS from SW. ARCH.-1
Software systems are designed based on 6 unit operations : separation, abstraction, compression, uniform composition, replication and resource sharing (Kazman et al. -Technical Report CMU/SEI-94-TR-10, August 1994).
These provide architectural basis for application quality attributes : scalability, separation, modifiability, integrability, portability, performance, reliability, ease of creation and reusability …( Mario Barbacci, et al., Technical Report, CMU/SEI-95-TR-021, ESC-TR-95-021,December 1995).
SOME BASICS from SW. ARCH.-2
Works of Dr.Nour Ali et al., Dr.Rami Bahsoon et al., Dr.Medvidovic.N et al., adds MOBILITY as one more unit operation at software architectural level
This work suggests a technique for “Loose coupling” – using speech acts- that can be visualized as one more unit operation at architectural level – for services composition applications.
We propose CLIENT App. to declare EPAs using IEEE/FIPA compliant “speech-acts” – not by URI; (using OIMS message templates) & compose Services based on it.
WS-A to be used to transport these OIMS message to a Proxy/Middleware from Consumer App.
Proxy to decode and connect with Provider EPAs dynamically using regular SOAP+”WS-A”+WSTechnology;
Proxy to marshal the replies back to Consumer App – using chained speech-acts.
Have looked at Apache ODE WS-BPEL & few micro-services platforms –for implementation…
Looking for real-world industrial situations /problems for prototype DEMO.
HELP US WITH YOUR FEEDBACK! We invite Co-authors/Collaborators!
Will our approach work?
Any Real-life industrial applications?
Any additions to the core –idea?
Please e-mail us, we love to partner with new co-authors for a matured industrially relevant matured work!
THANK YOU ALL SO MUCH!
airTicket booking service-- say based on QoS, Cost,
These provide architectural basis for application quality attributes : scalability, separation, modifiability, integrabilit