Transcript Towards an Integration of SWS into existing WS Infrastructures

Towards an Integration
of SWS into existing
WS Infrastructures
Christian Drumm
SAP AG
Outline
State-of-the-art
SWS in business applications
Abstract SWS environment
 Usage scenarios
 Integration into existing infrastructures
Evaluation/Outlook
 SAP AG 2004, Towards an integration of SWS into existing infrastructures / Christian Drumm / 2
State-of-the-art
Enterprise application platforms
 Support the development/deployment of WS
 SOAP, UDDI, WSDL
 Workflow engines to support complex scenarios
 BPEL4WS
Semantic Web Services
 Next evolutionary step for WS
 Several different architecture proposals
 WSM*
 OWL-S
 No integration in business applications yet
 SAP AG 2004, Towards an integration of SWS into existing infrastructures / Christian Drumm / 3
SWS in business applications
Two scenarios possible
 Replacement of existing environments
 Augmentation of existing environments
Second scenario much more likely as
 Significant investments in current environments
 Transition will take place gradually
Define SWS architecture capable of
coping with this requirements
 SAP AG 2004, Towards an integration of SWS into existing infrastructures / Christian Drumm / 4
Abstract SWS environment
Semantics
Composition
(design-time)
Execution
(run-time)
Discovery
Mediation
Discover SWS
Query ontologies
Reasoning
Deployment
Important features
 Separation of design-time and run-time
 Semantic discovery
 Data and process mediation
 SAP AG 2004, Towards an integration of SWS into existing infrastructures / Christian Drumm / 5
Perform mediation
SWS usage scenarios
NO dynamic goal decomposition
Static usage scenario
 Discovery only during design-time
 Execution of static process script during run-time
Dynamic usage scenario
 Goal-based discover during run-time
Mixed usage scenario
 Somewhere between the two extremes
 SAP AG 2004, Towards an integration of SWS into existing infrastructures / Christian Drumm / 6
Mixed usage scenarios with existing environments
Execution Environment
Semantics
 Simple WF engine
 No “knowledge” of
semantics
Execution
(BPEL4WS)
Proxy
WS
 SAP AG 2004, Towards an integration of SWS into existing infrastructures / Christian Drumm / 7
Discovery
Mediation
Composition
(design-time)
Proxy
 Specific for one goal
 Template based
manual creation
 Offers standard WS
interface to execution
environment
Evaluation/Outlook
Advantages
 Proxy enables SWS integration in existing environments
 Only extensions of existing infrastructures necessary
Disadvantages
 Proxy needs manual coding
 SWS developed using proxy approach can’t be easily moved to a full
SWS environment
Next Steps
 Implementation of ideas in a real system
 SAP AG 2004, Towards an integration of SWS into existing infrastructures / Christian Drumm / 8