Connecting SOA Artefacts in Eclipse:  The  Mangrove  SOA Modeling Framework Adrian  Mos & Fy Ravoajanahary Tuvalu Team htt...
Presentation Outline <ul><li>Context </li></ul><ul><li>Functional Description </li></ul><ul><li>Functional Areas </li></ul...
Mangrove  Overview <ul><li>Mangrove is an integration project for uniting existing and future Eclipse SOA projects </li></...
Mangrove: Functional Description <ul><li>Keeps SOA workspace artifacts in sync automatically and continuously </li></ul><u...
Mangrove: Functional Areas <ul><li>Core  - EMF-based meta-model and API </li></ul><ul><li>Branches -  Transformation Plug-...
DEMO
 
Current Status: Core <ul><li>MATURE </li></ul><ul><li>Existing EMF meta-model has undergone several improvements </li></ul...
Current Status: Branches <ul><li>ADVANCED </li></ul><ul><li>Existing Transformations: </li></ul><ul><ul><li>BPMN to Core <...
Current Status: Leaves <ul><li>INCIPIENT </li></ul><ul><li>BPMN Editor Extension </li></ul><ul><li>adding extended transfo...
Current Status: Builder <ul><li>INCIPIENT </li></ul><ul><li>Current functionalities </li></ul><ul><ul><li>Model consolidat...
Current Status: Roots <ul><li>NOT STARTED </li></ul><ul><li>Initial prototype (not public) for extracting monitoring infor...
Thank You! [email_address] [email_address] http://www.eclipse.org/proposals/mangrove/ http://www.eclipse.org/forums/eclips...
Upcoming SlideShare
Loading in …5
×

Connecting SOA Artefacts in Eclipse: The Mangrove SOA Modeling Framework

3,112 views

Published on

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 as

synchronizing various SOA artifacts using an automatic builder
updating model information in SOA editors with runtime data from monitoring
feeding model information to deployment tools
connecting with model and service repositories
The 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.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,112
On SlideShare
0
From Embeds
0
Number of Embeds
141
Actions
Shares
0
Downloads
69
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Connecting SOA Artefacts in Eclipse: The Mangrove SOA Modeling Framework

  1. 1. 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 EPL v1.0
  2. 2. Presentation Outline <ul><li>Context </li></ul><ul><li>Functional Description </li></ul><ul><li>Functional Areas </li></ul><ul><li>DEMO Video </li></ul><ul><li>Current Status </li></ul>
  3. 3. Mangrove Overview <ul><li>Mangrove is an integration project for uniting existing and future Eclipse SOA projects </li></ul><ul><li>It is an evolution of the existing STP Intermediate Model (IM) component (available in the Eclipse Release Train) </li></ul><ul><li>The IM focused on integrating several editors (such as BPMN, SCA, BPEL) </li></ul><ul><li>Mangrove extends the IM scope to cover the entire SOA TLP: </li></ul><ul><ul><li>Editors </li></ul></ul><ul><ul><li>Runtime </li></ul></ul><ul><ul><li>Deployment tools </li></ul></ul><ul><ul><li>Monitoring </li></ul></ul><ul><li>Mangrove’s Creation Review successfully passed last week! </li></ul>
  4. 4. Mangrove: Functional Description <ul><li>Keeps SOA workspace artifacts in sync automatically and continuously </li></ul><ul><li>Updates model information in Editors with runtime data from monitoring </li></ul><ul><li>Feeds model information to deployment tools and runtime tools </li></ul><ul><li>Connects to SOA repositories to sync service information </li></ul>11 sec 4.7 sec 0.4 sec 24 ms. ! 4.7 sec 85 ms. Runtime Monitoring Builder
  5. 5. Mangrove: Functional Areas <ul><li>Core - EMF-based meta-model and API </li></ul><ul><li>Branches - Transformation Plug-ins </li></ul><ul><li>Builder - Builder Plug-ins ensuring continuous updates between the Core, Tools and Editors </li></ul><ul><li>Leaves - Editor Extensions adding Mangrove-specific functionality to SOA editors (enrichment of SOA elements or configuration properties) </li></ul><ul><li>Roots - Runtime Connections to and from runtime, monitoring and deployment to keep the “living” Core instance up-to-date with execution data </li></ul>
  6. 6. DEMO
  7. 8. Current Status: Core <ul><li>MATURE </li></ul><ul><li>Existing EMF meta-model has undergone several improvements </li></ul><ul><li>It may be extended to account for new functionality in SOA TLP </li></ul>
  8. 9. Current Status: Branches <ul><li>ADVANCED </li></ul><ul><li>Existing Transformations: </li></ul><ul><ul><li>BPMN to Core </li></ul></ul><ul><ul><li>SCA to Core (basic functionality) </li></ul></ul><ul><ul><li>Core to SCA (basic functionality) </li></ul></ul><ul><ul><li>Core to BPEL (immediate release) </li></ul></ul><ul><li>Upcoming Transformations: </li></ul><ul><ul><li>Core to BPMN </li></ul></ul><ul><ul><li>Eclipse JWT  Core </li></ul></ul><ul><ul><li>Core  Runtime </li></ul></ul><ul><ul><li>Core  Monitoring (prototypes exist in preliminary stages) </li></ul></ul>
  9. 10. Current Status: Leaves <ul><li>INCIPIENT </li></ul><ul><li>BPMN Editor Extension </li></ul><ul><li>adding extended transformation support for BPEL / JBI </li></ul><ul><li>SCA Editor Extension (not public yet): </li></ul><ul><li>adding performance measurements from monitoring </li></ul>
  10. 11. Current Status: Builder <ul><li>INCIPIENT </li></ul><ul><li>Current functionalities </li></ul><ul><ul><li>Model consolidation : Single Core instance </li></ul></ul><ul><ul><li>Model update : Model modification and creation reflected in the IM core instance </li></ul></ul><ul><li>Limitation </li></ul><ul><ul><li>One way consolidation only: external changes propagated into Core </li></ul></ul><ul><ul><li>Basic consolidation only, more advanced consolidation is required </li></ul></ul><ul><li>Upcoming work </li></ul><ul><ul><li>Two-way modification propagation </li></ul></ul><ul><ul><li>Core instance file to be hidden from user </li></ul></ul>
  11. 12. Current Status: Roots <ul><li>NOT STARTED </li></ul><ul><li>Initial prototype (not public) for extracting monitoring information </li></ul><ul><li>The Core is augmented with performance information </li></ul>
  12. 13. Thank You! [email_address] [email_address] http://www.eclipse.org/proposals/mangrove/ http://www.eclipse.org/forums/eclipse.mangrove http://eclipse.org/stp/im/ (the precursor to Mangrove)

×