Connecting SOA Artefacts in Eclipse: The Mangrove SOA Modeling Framework
13
Connecting SOA Artefacts in Eclipse: The Mangrove SOA Modeling Framework Adrian Mos & Fy Ravoajanahary Tuvalu Team http://tuvalu.inrialpes.fr Santa Clara, 22 March 2010 © 2010 by Adrian Mos & Fy Ravoajanahary; made available under the EP
-
Upload
adrian-mos -
Category
Technology
-
view
2.178 -
download
1
description
This talk will present and demonstrate the new SOA-related Eclipse project, Mangrove - SOA Modeling Framework, part of the new Eclipse SOA top level project. Mangrove is an evolution from the Eclipse STP Intermediate Model (STP-IM), a component that served as the basis for interconnecting different editors in the SOA Tools Platform project and which has itself evolved to become the Eclipse SOA project.Mangrove has a larger scope than STP-IM as well as exciting new features such assynchronizing various SOA artifacts using an automatic builderupdating model information in SOA editors with runtime data from monitoringfeeding model information to deployment toolsconnecting with model and service repositoriesThe Mangrove SOA Modeling Framework comprises the following components that support the above-mentioned features. Not all components are fully implemented and the degree of maturity varies among them. The presentation will specify the status of each component so that attendees can leave with a clear understanding of what can be used today and what is work in progress.Core - the Core Metamodel and API: contains the SOA elements and their inter-relations, enabling the storing of distilled SOA elements used by different editors and tools.Branches - the Transformation Plug-ins: contain the logic required to move and convert information between editors, tools and the core metamodel instance.Phloem - the Builder: ensures the constant updating of SOA artifacts in the core as well as in the corresponding editors and tools (e.g. when saving a diagram, update the appropriate artifacts in the core while also enabling the update of the corresponding artifact in related editors or tools).Leaves - the Editor Extensions, extensions and improvements to editors and tools for adding Mangrove-specific functionality at design time (e.g. views allowing the enrichment of certain SOA elements in the core or configuration menus for customizing the amount of information to be moved to/from the core).Roots - the Runtime Connections: for moving information to and from runtime tools and repositories when needed in order to have a “living” core, providing a good reality snapshot. This can be useful when diagrams are out of sync or when aggregated monitoring information is required to update graphical elements. Also for generating deployment information in a common format. The talk will present the new project focusing on parts that haven't been presented before in the context of STP-IM. It will also demonstrate using a basic SOA example how information can be transported between BPMN and SCA editors, how the builder works behind the scenes to automatically save artefacts and finally how monitoring information can be transported and presented in the SCA editor.
Transcript of Connecting SOA Artefacts in Eclipse: The Mangrove SOA Modeling Framework
Connecting SOA Artefacts in Eclipse:
The Mangrove SOA Modeling Framework
Adrian Mos & Fy RavoajanaharyTuvalu Teamhttp://tuvalu.inrialpes.fr
Santa Clara, 22 March 2010
© 2010 by Adrian Mos & Fy Ravoajanahary; made available under the EPL v1.0
Presentation Outline
Context
Functional Description
Functional Areas
DEMO Video
Current Status
Mangrove Overview
Mangrove is an integration project for uniting existing and future Eclipse SOA projects
It is an evolution of the existing STP Intermediate Model (IM) component (available in the Eclipse Release Train)
The IM focused on integrating several editors (such as BPMN, SCA, BPEL)
Mangrove extends the IM scope to cover the entire SOA TLP:•Editors
•Runtime
•Deployment tools
•Monitoring
Mangrove’s Creation Review successfully passed last week!
Mangrove: Functional Description
Keeps SOA workspace artifacts in sync automatically and continuously
Updates model information in Editors with runtime data from monitoring
Feeds model information to deployment tools and runtime tools
Connects to SOA repositories to sync service information
11 sec11 sec 4.7 sec4.7 sec 0.4 sec0.4 sec
24 ms.24 ms.
!
4.7 sec4.7 sec
85 ms.85 ms.
BuilderRuntime Monitoring
Mangrove: Functional Areas
Core - EMF-based meta-model and API
Branches - Transformation Plug-ins
Builder - Builder Plug-ins ensuring continuous updates between the Core, Tools and Editors
Leaves - Editor Extensions adding Mangrove-specific functionality to SOA editors (enrichment of SOA elements or configuration properties)
Roots - Runtime Connections to and from runtime, monitoring and deployment to keep the “living” Core instance up-to-date with execution data
DEMO
Current Status: Core
MATURE
Existing EMF meta-model has undergone several improvements
It may be extended to account for new functionality in SOA TLP
Current Status: Branches
ADVANCED
Existing Transformations:• BPMN to Core
• SCA to Core (basic functionality)
• Core to SCA (basic functionality)
• Core to BPEL (immediate release)
Upcoming Transformations:• Core to BPMN
• Eclipse JWT Core
• Core Runtime
• Core Monitoring (prototypes exist in preliminary stages)
Current Status: Leaves
INCIPIENT
BPMN Editor Extension
adding extended transformation support for BPEL / JBI
SCA Editor Extension (not public yet):
adding performance measurements from monitoring
Current Status: Builder
INCIPIENT
Current functionalities• Model consolidation : Single Core instance
• Model update : Model modification and creation reflected in the IM core instance
Limitation• One way consolidation only: external changes propagated into Core
• Basic consolidation only, more advanced consolidation is required
Upcoming work• Two-way modification propagation
• Core instance file to be hidden from user
Current Status: Roots
NOT STARTED
Initial prototype (not public) for extracting monitoring information
The Core is augmented with performance information
Thank You!
[email protected]@inrialpes.fr
http://www.eclipse.org/proposals/mangrove/http://www.eclipse.org/forums/eclipse.mangrove
http://eclipse.org/stp/im/ (the precursor to Mangrove)
