1. © 2005-2006 The ATHENA Consortium. 6-3. From PIM4SOA to Web Services,

2. 2 © 2005-2006 The ATHENA Consortium. PIM4SOA Metamodel Web Services Metamodel Agent Metamodel (AgentMM) P2P Metamodel Grid Metamodel PIM PSMs Symbols Metamodel Concept Relationship Correspondence PIM4SOA → platform specific models

3. 3 © 2005-2006 The ATHENA Consortium. PIM4SOA → platform specific models PIM4SOA source metamodel Web services target metamodels Mapping model

4. 4 © 2005-2006 The ATHENA Consortium. Web services architecture metamodel

5. 5 © 2005-2006 The ATHENA Consortium. WSDL 1.1 metamodel A collection of related endpoints A single endpoint defined as a combination of a binding and a network address A concrete protocol and data format specification for a particular port type An abstract set of operations supported by one or more endpoints An abstract, typed definition of the data being communicated An abstract, description of an action supported by the service A container for data type definitions

6. 6 © 2005-2006 The ATHENA Consortium. PIM4SOA model (.uml2) WS-* model (.uml2) UML profile for Web services Web service artefacts EMFEcore Metamodels/Models RSM UML Models and Profiles XSD WSDL BPEL XSD WSDL BPEL M2M UML profile for PIM4SOA PIM4SOA model (.ecore) WS-* models (.ecore) M2M M2T M2M 1 2 3 4 X Eclipse/RSM modelling environment 1.Build your PIM4SOA (.uml2) model in RSM using the UML profile for PIM4SOA and transform it to a PIM4SOA (.ecore) model in EMF. 2.Transform the PIM4SOA (.ecore) model to Web service (.ecore) models. 3.Transform the Web service (.ecore) models to Web service artefacts. 4.Model transformation for UML profiles for Web services Eclipse Modelling Framework (EMF) Rational Software Modeler (RSM)

7. 7 © 2005-2006 The ATHENA Consortium. Transformation to XSD The XSD artefacts are generated from the Information part of the PIM4SOA model. The starting point for the transformation is a PIM4SOA document. The strategy is to convert one PIM4SOA Document into one XML schema. The mappings between the most relevant PIM4SOA elements and XSD are listed next.

8. 8 © 2005-2006 The ATHENA Consortium. PIM4SOA main mappings to XSD PIM4SOA element XSD equivalentNotes DocumentSchema EntityComplexType AssociationElement An association between entities is transformed into an element in the containing type with a reference to the complex type generated for the target Entity Attribute Attributes having simple types are mapped to Attributes in complex types. Attributes with complex types in the PIM4SOA model are mapped in the same way as Associations. ElementSimpleTypeIf the ItemType from the PIM4SOA model is not an entity (meaning it is a simple type) a SimpleType definition is created in the schema.

9. 9 © 2005-2006 The ATHENA Consortium. Transformation to WSDL The WSDL artefacts are generated from the Service part of the PIM4SOA model. While the mapping of the PIM4SOA to XSD was quite straight forward, the mapping to WSDL is a bit more complex. The WSDL generated has links to the XML schema, as the messages in the PIM4SOA model get their structural information from the Information part of the PIM4SOA models.

10. 10 © 2005-2006 The ATHENA Consortium. PIM4SOA main mappings to WSDL PIM4SOA element WSDL equivalent Notes PackageDefinitionThe transformation takes a complete PIM4SOA model as input and creates on WSDL artefact per model. Message If the PIM4SOA Message has a type assigned to it, the WSDL message is created with one Part corresponding to hat type. If not one Part is created for each of the Items contained by the PIM4SOA Message. RoleBindingPortTypeA role binding within a CollaborationUse is a potential PortType. It is transformed into a PortType if the role it is bound to is part of a binary Collaboration without any CollaborationUses (a leaf collaboration) CollaborationOperationA binary Collaboration (only two roles) that does not contain any CollaborationUses (leaf Collaboration) is transformed into an operation. If only one of the Roles in the Collaboration have Messages an asynchronous pattern is generated meaning that two operations are created, each in different PortTypes; one for the provider and one for the consumer.

11. 11 © 2005-2006 The ATHENA Consortium. Transformation to BPEL Starting point for a BPEL transformation –PIM4SOA ServiceProvider participating in at least one Collaboration and implementing a Behaviour as a PIM4SOA Process. The transformation from PIM4SOA to BPEL are closely tied to the generation of the WSDL interfaces The WSDL transformation allows –collaborations in which a ServiceProvider participates to be converted to Services and Porttypes, and Partnerlink types to be referenced in the BPEL.

12. 12 © 2005-2006 The ATHENA Consortium. PIM4SOA main mappings to BPEL PIM4SOA elementBPEL equivalent Notes ServiceProvider Process Process Task (i) (participating in collaboration) Receive, Invoke, ReplyThe type of communication with other service providers must be deduced from parameters passed to or from the task in question. Task (ii) (no collaboration use) EmptyThis might be a task requiring further implementation or human interaction beyond the scope of the PIM4SOA. FlowSequence, Flow, (…)The structure of flows between Steps must be analysed to deduce the applicable BPEL structure. Interaction, PinAssignInteractions have a role to play both in determining collaboration type (see Task (ii) above), and passing particular parts of messages between tasks (data flow, a BPEL assign). MessageVariableAll messages sent and received must have appropriate variables defined within the BPEL CollaborationUse RoleBinding PartnerLinkThe CollaborationUses defined for the ServiceProvider tell us what PartnerLinks we will need. See CollaborationUsePath. CollaborationUsePathPartnerLink, Role(…)This defines a specific use of a PartnerLink, alongside what role we are playing, and even the PortType being used. See links to the WSDL transformation described below.

13. 13 © 2005-2006 The ATHENA Consortium. Model transformations overview

14. 14 © 2005-2006 The ATHENA Consortium. References

15. 15 © 2005-2006 The ATHENA Consortium. References (ATHENA deliverables) [ATHENA] ATHENA, "ATHENA Public Web Site", ATHENA Integrated Project (IST-507849). http://www.athena-ip.org/ http://www.athena-ip.org/ [ATHENA A5 2005] ATHENA A5, "D.A5.1: Perspectives on Service-Oriented Architectures and there application in environments that require solutions to be planned and customisable", ATHENA IP, Deliverable D.A5.1, 2005. [ATHENA A5 2005] ATHENA A5, "D.A5.2: Model and Specification of Service Descriptions and Usage as well as Advanced Concepts", ATHENA IP, Deliverable D.A5.2, 2005. [ATHENA A5 2006] ATHENA A5, "D.A5.3: Architecture of SOA Platforms", ATHENA IP, Deliverable D.A5.3, 2006. [ATHENA A5 2006] ATHENA A5, "D.A5.4: Execution Framework(s) for Planned and Customisable Service-Oriented Architectures", ATHENA IP, Deliverable D.A5.4, 2006. [ATHENA A5 2006] ATHENA A5, "D.A5.5: Validation of Research Results", ATHENA IP, Deliverable D.A5.5, 2006. [ATHENA A6 2005] ATHENA A6, "D.A6.1: Specification of a Basic Architecture Reference Model", ATHENA IP, Deliverable D.A6.1, 2005. [ATHENA A6 2006] ATHENA A6, "D.A6.2: Enhanced Registry/Repository Infrastructure", ATHENA IP, Deliverable D.A6.2, 2006. [ATHENA A6 2006] ATHENA A6, "D.A6.3: Model-driven and Adaptable Interoperability Framework", ATHENA IP, Deliverable D.A6.3, 2006. [ATHENA A6 2006] ATHENA A6, "D.A6.4: Model-driven and Adaptable Interoperability Infrastructure", ATHENA IP, Deliverable D.A6.4, 2006.

16. 16 © 2005-2006 The ATHENA Consortium. References (Papers) [Benguria, et al. 2006] G. Benguria, X. Larrucea, B. Elvesæter, T. Neple, A. Beardsmore, and M. Friess, ”A Platform Independent Model for Service Oriented Architectures”, to be presented at the 2nd International Conference on Interoperability of Enterprise Software and Applications (I-ESA 2006), Bordeaux, France, 2006. [Elvesæter, et al. 2005] B. Elvesæter, A. Hahn, A.-J. Berre, and T. Neple, "Towards an Interoperability Framework for Model-Driven Development of Software Systems", in Proc. of the 1st International Conference on Interoperability of Enterprise Software and Applications (INTEROP-ESA 2005), Geneva, Switzerland, 2005. [Elvesæter, et al. 2005] B. Elvesæter, R. K. Rolfsen, F. Lillehagen, and D. Karlsen, "Integrated Enterprise Service Architecture", in Proc. of the 12th ISPE International Conference on Concurrent Engineering (CE 2005), Fort Worth, Texas, USA, 2005, M. Sobolewski and P. Ghodous (Eds.), International Society for Productivity Enhancement, Inc., NY, USA, pp. 129-134. [Lillehagen, et al. 2005] F. Lillehagen, D. Karlsen, H. G. Solheim, H. D. Jørgensen, H. Smith-Meyer, B. Elvesæter, and R. K. Rolfsen, "Enterprise Architecture - from Blueprints to Design Services", in Proc. of the 12th ISPE International Conference on Concurrent Engineering (CE 2005), Fort Worth, Texas, USA, 2005, M. Sobolewski and P. Ghodous (Eds.), International Society for Productivity Enhancement, Inc., NY, USA, pp. 121-128. [Fischer, et al. 2006] K. Fischer, B. Elvesæter, A.-J. Berre, C. Hahn, C. Madrigal-Mora, and I. Zinnikus, ”Model-Driven Design of Interoperable Agents”, to be presented at the 2nd Workshop on Web Services Interoperability (WSI 2006), Bordeaux, France, 2006. [Vayssière, et al. 2006] J. Vayssière, G. Benguria, B. Elvesæter, K. Fischer, and I. Zinnikus, "Rapid Prototyping for Service-Oriented Architectures", to be presented at the 2nd Workshop on Web Services Interoperability (WSI 2006), Bordeaux, France, 2006.

17. 17 © 2005-2006 The ATHENA Consortium. This course has been developed under the funding of the EC with the support of the EC ATHENA-IP Project. Disclaimer and Copyright Notice: Permission is granted without fee for personal or educational (non-profit) use, previous notification is needed. For notification purposes, please, address to the ATHENA Training Programme Chair at rg@uninova.pt. In other cases please, contact at the same e-mail address for use conditions. Some of the figures presented in this course are freely inspired by others reported in referenced works/sources. For such figures copyright and all rights therein are maintained by the original authors or by other copyright holders. It is understood that all persons copying these figures will adhere to the terms and constraints invoked by each copyright holder.rg@uninova.pt