paper8

Information about paper8

Published on November 26, 2007

Author: Sevastian

Source: authorstream.com

Content

Demonstrating WSMX: Least Cost Supply Management:  Demonstrating WSMX: Least Cost Supply Management Table of Contents:  Table of Contents Introduction Use case: Ordering Broadband Internet WSMX Overview WS-BPEL Overview Extending WSMX Conclusion and Future Work Introduction:  Introduction Web services. Semantic web. Semantic Web services. Slide4:  Introduction Use case: Ordering Broadband Internet WSMX Overview WS-BPEL Overview Extending WSMX Conclusion and Future Work Motivation:  Motivation For demonstrating the potential of WSMX we selected a use case from the telecommunications sector. Internet Service providers are extending their business with wholesaling of mobile and fixed line telephone services and unbundled data lines. Easy and flexible dynamic integration of suppliers that offer these services is needed. Description:  Description An ADSL line is a broadband Internet connection on top of a regular telephone line. Several suppliers of unbundled ADSL lines are available depending on region where the customer is located. Wholesalers need a flexible and dynamic integration of these suppliers in their back-end systems. Objectives:  Objectives ADSL line suppliers have different end point interfaces. Message mediation between wholesalers and ADSL supplier is needed. Line suppliers differ in capability to provide an ADSL line for given phone number (it depends on region). Least cost supplier which can provide ADSL line for given phone number must be dynamic found and bounded into a ordering process flow. Process Flow Steps:  Process Flow Steps Static wholesaler ordering ADSL line process is realized as a WS-BPEL complex process controlled by an BPEL execution engine. Web services for check of a bank card, availability of internet domain, billing etc. are invoked directly by the BPEL execution engine. ADSL suppliers have to register their services within the WSMX service repository where the capabilities and mapping rules should be stored. To find proper ADSL provider, BPEL process of wholesaler invokes WSMX engine sending him goal description and other needed information in form of a SOAP message. Use Case Process Flow Diagram:  Use Case Process Flow Diagram Slide11:  Introduction Use case: Ordering Broadband Internet WSMX Overview WS-BPEL Overview Extending WSMX Conclusion and Future Work Introduction:  Introduction Execution environment for Semantic Web Services. A reference implementation for WSMO. Service oriented and event-based architecture. Decouples service providers and requesters. Dynamic discovery based on Goal-Capability matching. Mediation. Data. Process. Protocol. WSMX Architecture:  WSMX Architecture WSMX Discovery Mechanism:  WSMX Discovery Mechanism Based on matching of logical goals with WS capabilities. Goals and capabilities have postconditions and effects. Capabilities additionally have preconditions and assumptions. Current WSMX Architecture:  Current WSMX Architecture Implementation:  Implementation Event based service oriented architecture. Current status: Code base established – available at SourceForge. Data mediation component implemented. Other component interfaces defined and partially implemented. Main technologies used: Apache Tomcat and Apache Axis. Database – mySQL. Eclipse IDE and Ant as build tool. Slide17:  Introduction Use case: Ordering Broadband Internet WSMX Overview WS-BPEL Overview Extending WSMX Conclusion and Future Work WS-BPEL Standard:  WS-BPEL Standard Process modelling language based on Web services. Widely used for automation of business processes. BPEL was originally developed by BEA, IBM, and Microsoft. Version 1.1 also includes input from SAP and Siebel.5. The OASIS TC “web services business execution language” now continues the standardization of BPEL. WS-BPEL Overview:  WS-BPEL Overview WS-BPEL defines business processes consisting of stateful long-running interactions in which each interaction has a beginning, a defined behavior and an end, modeled by a flow. Flow is composed by a sequence of activities. The behavior context for each activity is provided by a scope. A scope can provide fault handlers, event handlers, compensation handlers and a set of data variables and correlation sets. WS-BPEL Process Flow Scope 1:  WS-BPEL Process Flow Scope 1 WS-BPEL Process Flow Scope 2:  WS-BPEL Process Flow Scope 2 Events, for event driven flow execution. Variables, in WSDL schema defined messages for internal or external purposes. Correlations, definitions of message parts which identify particularly process instance (session ID). Fault handling, defines what happen if an exception has been thrown. Event handling, defines what happen if an event occurs. WS-BPEL Activities 1:  WS-BPEL Activities 1 Receive - do a blocking wait for a matching message to arrive. Reply - send a message in reply to a message which was sent by a <receive>. Invoke - invoke a one-way or request-response operation on a port type offered by a partner. Assign - update values in variables. Throw - generates a fault inside the business process. Wait - wait till a certain time has passed. Empty - insert a “no-op” instruction into a business process. WS-BPEL Activities 2:  WS-BPEL Activities 2 Sequence - define a collection of activities to be performed sequentially. Switch - select a branch of activities from a set of choices. While - repeat an activity till a certain condition of success has been met. Pick - block and wait for a suitable message to arrive. Flow - specify one or more activities to be performed concurrently. Scope - define a nested activity with its own associated variables, fault handlers and compensation handlers. Compensate - invoke compensation in an inner scope i.e. from a fault handler or a compensation handler. Disadvantages of WS-BPEL:  Disadvantages of WS-BPEL Static process composition. Process participants (partner‘s web services) must be defined and bound to the process flow at design time. BPEL standard is not about Semantic Web services: Partner discovery and bounding at run time not possible. Message mediation not possible. BPEL Engine Implementations:  BPEL Engine Implementations BPWS4J (Test engine from IBM Alphaworks) http://www.alphaworks.ibm.com/tech/bpws4j ActiveBPEL (First Open Source BPEL engine) http://www.activebpel.org/ Oracle BPEL Process manager http://www.oracle.com/technology/products/ias/bpel/index.html Slide26:  Introduction Use case: Ordering Broadband Internet WSMX Overview WS-BPEL Overview Extending WSMX Conclusion and Future Work BPEL & WSMX:  BPEL & WSMX Integration of WS-BPEL and WSMX. Static defined process flow provided by BPEL. Known services are invoked statically as described in the BPEL process flow. Dynamic services will be discovered and invoked through invocation of WSMX engine by BPEL process flow. Dynamic Service Invocation:  Dynamic Service Invocation BPEL static process invokes WSMX using its web service interface. Input message sent from BPEL has a goal and input parameters. WSMX finds suitable services based on an Input goal and handles with message mediation between BPEL message format and message format of a chosen web service. Extending WSMX:  Extending WSMX To implement our use case is needed an extension of current WSMX service discovery mechanism. In our use case a capabilities of a web services can not be described static, they can differ (ADSL line providers supports some telephone numbers, set of supported ones differs and can not be coded directly as a service capabilities). Current shortcomings in WSMX:  Current shortcomings in WSMX Assumption that providers are able to completely describe their Web Services in WSMX Capabilities Repositories at design time (static description) – providers need a mechanism to defer specification of their capabilities during runtime, Limited operational behavior – WSMX does not support complex goals consisting of several subgoals. Further step: WSMX understanding some process modeling language. Conditional WS Implementation:  Conditional WS Implementation Providers cannot store a range of number they can provide a ASDL line for in WS Capability since it is changing very frequently, Before ASDL line is purchased, its availability has to be checked for requested landline number, Assumption: There is list of Conditional WS, which must be executed before selected Web Service can be executed itself – in future this should be specified within logic expressions or in process modeling language. Conditional WS Implementation:  Conditional WS Implementation Based on matching of logical goals with WS capabilities. Goals and capabilities have postconditions and effects. Capabilities additionally have preconditions and assumptions. WSMX adds concept of conditional web service to capability. Conditional WS1 Conditional WS2 WSMX Matchmaker Possible Matches Goal Collection of WS Step 2 Step 3 Step 1 Step 4 Match requester Conditional WS Implementation:  Conditional WS Implementation Each of the Conditions creates a new Event in the system, all new Events return typed Values, which can be processed by initializing component, If all return results from intermediate Web Services indicate successful result, then WS conditions are fulfilled and execution of given WS can be performed, New component called Correlation Manager maintains the relationships between main event and conditional events; Correlation Manager puts main event into sleep and once all the conditional events are in state consumed, it wakes the main event up. Conditional WS Implementation:  Conditional WS Implementation Implementation started – not finished yet Business Process Engine in WSMX:  Business Process Engine in WSMX Process execution engine is able to understand the given specification of the ordering process and manages the runtime execution of this process, No decision has yet been made on a formalism for specifying complex goals. Solutions that are considered include YAWL or WS-BPEL, Two approaches to Complex Goal: Conditional WS within logic expressions or Conditional WS specified in modeling language, Slide36:  Introduction Use case: Ordering Broadband Internet WSMX Overview WS-BPEL Overview Extending WSMX Conclusion and Future Work Conclusion:  Conclusion We have shown how to integrate the WS-BPEL with WSMX to provide supporting for dynamic real integration use case. The general assumption of WSMX that providers should completely describe the functionality of their services at design time is unreasonable. Known Problems:  Known Problems Security. Transaction Management. Performances. Using of WS-BPEL can be seen as temporary solution, the WSMX should have service composition capabilities. Future Work:  Future Work Realization of the presented use case. Extending of WSMX functionality: Extend the logical language to include a built-in function that evaluates during run time to a web service call. Include the process modelling component in WSMX that is able to execute complex goals. The End:  The End

Related presentations


Other presentations created by Sevastian

ISPS
05. 11. 2007
0 views

ISPS

Love and Friendship
24. 12. 2007
0 views

Love and Friendship

The Meiji Restoration
27. 03. 2008
0 views

The Meiji Restoration

Passover Communion 2007
05. 03. 2008
0 views

Passover Communion 2007

frbr2
27. 02. 2008
0 views

frbr2

BB 3 06 presGC
07. 01. 2008
0 views

BB 3 06 presGC

Cambodia
07. 01. 2008
0 views

Cambodia

L14
05. 01. 2008
0 views

L14

GEGPresentation
04. 01. 2008
0 views

GEGPresentation

Week4b
27. 09. 2007
0 views

Week4b

The Persian Wars
07. 12. 2007
0 views

The Persian Wars

4TTExcav2
10. 12. 2007
0 views

4TTExcav2

Hooters ppt Recovered
12. 12. 2007
0 views

Hooters ppt Recovered

anzio
30. 10. 2007
0 views

anzio

Wright ppt
31. 10. 2007
0 views

Wright ppt

new sol vocab review mouse
01. 11. 2007
0 views

new sol vocab review mouse

aspects culturel sdela France
02. 11. 2007
0 views

aspects culturel sdela France

Proctor BAT Brief
05. 11. 2007
0 views

Proctor BAT Brief

Area Communication Systems
06. 11. 2007
0 views

Area Communication Systems

Chapter4
07. 11. 2007
0 views

Chapter4

laburinary 03
13. 11. 2007
0 views

laburinary 03

Volkswagen Aids Care Program
16. 11. 2007
0 views

Volkswagen Aids Care Program

eurotb slides balkans
21. 11. 2007
0 views

eurotb slides balkans

Baseline project Summer 2007
04. 12. 2007
0 views

Baseline project Summer 2007

PressPack
23. 11. 2007
0 views

PressPack

Kids Help Phone Presentation
23. 12. 2007
0 views

Kids Help Phone Presentation

drawinglessons
02. 01. 2008
0 views

drawinglessons

1 OpenPresentation
28. 09. 2007
0 views

1 OpenPresentation

Vasa
07. 11. 2007
0 views

Vasa

11 tg
04. 01. 2008
0 views

11 tg

Transits of Venus Pictures Only
26. 10. 2007
0 views

Transits of Venus Pictures Only

3 ModelagemEstatistica
28. 12. 2007
0 views

3 ModelagemEstatistica

Conway 2
24. 10. 2007
0 views

Conway 2

mln
18. 12. 2007
0 views

mln

JangWoo Son
09. 10. 2007
0 views

JangWoo Son

001
31. 10. 2007
0 views

001

sunum tasarim
14. 11. 2007
0 views

sunum tasarim

Spinoffs
25. 10. 2007
0 views

Spinoffs

Joao Castro
28. 11. 2007
0 views

Joao Castro

TS107 WEEK4 2 TRANSPORT
12. 11. 2007
0 views

TS107 WEEK4 2 TRANSPORT

7 Dividing Fractions
28. 12. 2007
0 views

7 Dividing Fractions

Module 2 VOCs
08. 11. 2007
0 views

Module 2 VOCs

Internet Detective LILAC2006
13. 12. 2007
0 views

Internet Detective LILAC2006

smn presentation
06. 11. 2007
0 views

smn presentation

ULSDDowngrading
06. 11. 2007
0 views

ULSDDowngrading

maslennikov2
01. 11. 2007
0 views

maslennikov2

mobicom1
31. 10. 2007
0 views

mobicom1

SACS WorkshopJuly2007
22. 11. 2007
0 views

SACS WorkshopJuly2007