Rapid Prototyping for Service- Oriented Architectures 2nd Workshop - PowerPoint PPT Presentation

Rapid Prototyping for Service- Oriented Architectures 2nd Workshop on Web Services Interoperability (WSI 2006) Bordeaux, France, March 21, 2006 Julien Vayssière 1 , Gorka Benguria 2 , Brian Elvesæter 3 , Klaus Fischer 4 , Ingo Zinnikus 4 1 SAP Research, Brisbane, Australia, julien.vayssiere@sap.com 2 European Software Institute (ESI), Bizkaia, Spain, gorka.benguria@esi.es 3 SINTEF ICT, Oslo, Norway, brian.elvesater@sintef.no 4 DFKI GmbH, Saarbrücken, Germany, {klaus.fischer, ingo.zinnikus}@dfki.de

Outline • Background and motivation • Framework overview – Model-driven development framework – Web services enactment framework – Agent-based execution platform • Prototyping case study • Conclusion 2 Bordeaux, France, March 21, 2006

Background • Service-Oriented • Web services architecture Architecture – technology most often used for implementing SOAs – architectural style – standards-based stack of – gaining momentum specifications – mainstream in enterprise – enable interoperable computing interactions between Web- • Four tenets of service- based applications orientation (Box 2004) – explicit boundaries – autonomy of services – declarative interfaces and data formats – policy-based service description 3 Bordeaux, France, March 21, 2006

Motivation • Prototyping SOAs – working implementation of an SOA that can be used for validating the initial design choices • Different compared to traditional application development – need to take into account existing services – developed by organisations over which we have no control – introduces constraints into the prototyping exercise • Current state of the art tools – assumes that we are starting with a blank page – merely extends the approach of regular software prototyping to the scale of SOAs – they make the implicit assumption that services will behave as expected • This is why we designed an approach that – from the start, takes into account the fact that parts of the SOA needs to be considered as a given; and – should be treated with a healthy dose of caution. 4 Bordeaux, France, March 21, 2006

Framework overview • The ATHENA baseline methodology for SOA provides guidelines for developing platform independent models for SOA (PIM4SOA). Modelling • Provides a set of modelling tools and services for mapping between PIM4SOA and platform specific models (Web services and BDI agents) • Johnson and Lyndon provide enactment of all the • The ATHENA baseline methodology • The Web service extensions to the JACK roles found in an SOA (consumer, provider, for SOA provides guidelines for PIM4SOA autonomous agents platform allow SOAs to External WSDL Documents intermediary) and flexible communication between developing platform independent WSDL Documents MDD Framework BDI Teams use agents for brokering, mediation and Web services through an intuitive user interface models for SOA (PIM4SOA). negotiation between Web services • The WSDL Analyzer tool detected syntactical • Provides a set of modelling tools and WSDL Analyzer Lyndon • BDI teams provide a flexible and composable mismatches between service descriptions and services for mapping between alternative to traditional approaches to Web Jack Johnson «invoke» provides a basis for runtime mediation of Web PIM4SOA and platform specific models «invoke» service composition service messages (Web services and BDI agents) Agents Services • The Web service extensions to the JACK • Johnson and Lyndon provide enactment of all the roles found autonomous agents platform allow SOAs to use in an SOA (consumer, provider, intermediary) and flexible agents for brokering, mediation and negotiation communication between Web services through an intuitive user between Web services interface • BDI teams provide a flexible and composable • The WSDL Analyzer tool detected syntactical mismatches alternative to traditional approaches to Web service between service descriptions and provides a basis for runtime composition mediation of Web service messages 5 Bordeaux, France, March 21, 2006

UML Profile for POP* • Process annotated with • Organisation Enterprise • Product Model • … Business Model to Model Requirements Reference Ontology Transformation Architecture Specification Analysis UML Profile for SOA • Information annotated with • Service Service-Oriented • Process Architecture Model • QoS Model to Model Transformation Model Transformation UML Profile for Web Services annotated with UML Profile for Agents UML Profile for BPEL Web Service Agent Specification BPEL Specification P2P Specification Specification Model Model Model Model UML Profile for P2P Model to Text Model Transformation Transformation annotated with Web Service OWL Agent BPEL P2P Execution Artefacts Ontology Execution Artefacts Execution Artefacts Execution Artefacts ATHENA Deployment baseline Service Wrappers Service Wrappers Public (Enterprise X) (Enterprise Y) Infrastructure Services Cross- methodology org. Registry Service Wrappers (Enterprise A) Repository Intra- ATHENA Integrated Evaluation & Negotiation of Available Functionality org. Goal-oriented Goal-oriented for SOA Process Active Active Composed Adaptive Adaptive Internal Execution Execution Execution Model Model WebService Infrastructure Services Platform Platform Platform Platform Platform Platform (BPEL) (AKMii) (AKMii) (WebServices) Execution Infrastructure (Agents) (Agents) Semantic Adaptive Distributed Resource Mgt Platform Enhanced Service Interconnection Bus (P2P) Legend (overview) Space Business Process/Agent Server-side Server-side Message- Message- Existing Enterprise Applications Component Component Oriented Oriented Active (Business) Model Platform Platform Platform Platform Web/Server Component (.NET, J2EE) (.NET, J2EE) (MQSeries) (MQSeries) Middleware Process/Agent Middleware Component 6 Bordeaux, France, March 21, 2006

Model-driven development framework UML Profile for PIM4SOA PIM4SOA Model • Information • Service Information Service Process QoS • Process View View View View • QoS 1 Model to Model Transformation 1..* UML Profile for XSD Platform Specific Model UML Profile for WSDL XML WSDL BDI BPEL UML Profile for BDI Agents Schema Description Teams Process UML Profile for BPEL 1 Model to Text Transformation 1 Execution Integrated Execution Artefacts Infrastructure for XSD WSDL JACK BPEL Web Services Document Document BDI Teams Document and BDI Agents • Follows the OMG Model Driven Architecture (MDA) – Defines a Platform Independent Model (PIM) for SOA (PIM4SOA) – Platform Specific Models (PSMs) for describing Web services (XML Schemas and WSDL), Jack BDI agents and BPEL (Business Process Execution Language) • PIM4SOA is a visual PIM which specifies services in a technology independent manner – Integrated view of the SOA in which different components can be deployed on different execution platforms. – The PIM4SOA model helps us to align relevant aspects of enterprise and technical IT models – Allows us to raise the abstraction level at which we can talk about and reason on the architecture we design. 7 Bordeaux, France, March 21, 2006

PIM4SOA → platform specific models PIM4SOA Symbols Metamodel Metamodel PIM Concept Relationship Correspondence PSMs Web Services Agent Metamodel P2P Grid Metamodel (AgentMM) Metamodel Metamodel 8 Bordeaux, France, March 21, 2006

PIM4SOA addresses four system aspects Metamodel for (software) services Metamodel for (automated software) processes Services are an abstraction and an encapsulation of the functionality provided by Processes describe sequencing of work in an autonomous entity. Service architectures terms of actions, control flows, information are composed of functions provided by a flows, interactions, protocols, etc. system or a set of systems to achieve a Business Process Definition Metamodel shared goal. (BPDM) (IBM et al. 2004) Web Services Architecture as proposed by UML Profile for Enterprise Distributed Object W3C (W3C 2004) Computing (OMG 2002) UML Profile for Enterprise Distributed Object Computing (OMG 2002) Metamodel for information Metamodel for quality of service (QoS) Information is related to the messages or Extra-functional qualities that can be applied structures exchanged, processed and stored to services, information and processes. by software systems or software components. UML Profile for Modeling Quality of Service and Structural constructs for class modelling in Fault Tolerance Characteristics and UML 2.0 (OMG 2003) Mechanisms (OMG 2004) UML Profile for Enterprise Distributed Object Computing (OMG 2002) 9 Bordeaux, France, March 21, 2006