From Eclipse to Document      management A case study for JWT & EasySOA   Eclipse DemoCamp Juno – June 13th, 2012         ...
Speakers• Marc Dutoo    – Head of R&D at Open Wide    – EasySOA project leader• Yoann Rodière    – Intern at Open Wide    ...
AgendaI. Problem   I. Documenting & Modeling   II. Export from an editor   III. The Eclipse caseII. Solution   I.     Docu...
Problem: why is documenting important to                                     modeling?        Internal                    ...
Problem: Does it ring a bell?• Do you have such problems ?    – How do you handle it right now ?    – (already asked at JU...
Problem: what to export?• The simplest: editor files, image files    – For archive, for reference, for description• More a...
Problem: documenting from Eclipse                               PNG                              PNG                      ...
Solution: Document Management Systems (DMS)• A software brick for Enterprise Content Management  (ECM)• No loss of informa...
Solution: We need a bridge!             Eclipse                    Document Management System        Editor model         ...
Solution: Previous attempt                                             Seen here last year !Eclipse                       ...
Solution: Generic Eclipse/DMS bridge                                 requirements• One-way synchronization    – Export the...
Solution: our two cents                    Eclipse                            CMIS metamodel  Editormetamodel             ...
Solution: overall architectureEditor to CMIS                                      = to be  model ATL                      ...
Case study: Demo13/06/2012
Case study: EasySOA  EasySOA : SOA registry & management solution   – Built on the Nuxeo DM document management solution  ...
More to come...• EMF - ECM integration   – Gather community & interested people (you ?)   – Improve the prototype:      • ...
What about you, now?       www.easysoa.org      github.com/easysoa    easysoa-dev@googlegroups.com13/06/2012
Upcoming SlideShare
Loading in …5
×

From Eclipse to Document Management - Eclipse DemoCamp Grenoble 2012

1,565 views
1,467 views

Published on

Why ? To publish and share beyond Eclipse your SOA documents e.g. JWT workflows.
How ? Let's dip in issues, concepts and technologies.
What is it like ? Here comes demo time !

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

  • Be the first to like this

No Downloads
Views
Total views
1,565
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

From Eclipse to Document Management - Eclipse DemoCamp Grenoble 2012

  1. 1. From Eclipse to Document management A case study for JWT & EasySOA Eclipse DemoCamp Juno – June 13th, 2012 1
  2. 2. Speakers• Marc Dutoo – Head of R&D at Open Wide – EasySOA project leader• Yoann Rodière – Intern at Open Wide – Works on EasySOA integration to Eclipse & BPM (JWT)13/06/2012
  3. 3. AgendaI. Problem I. Documenting & Modeling II. Export from an editor III. The Eclipse caseII. Solution I. Document Management Systems II. We need a bridge! III. Bridge requirements IV. Our solution V. Overall architectureIII.Case study I. EasySOA II. Demo III. JWT Blackbox13/06/2012
  4. 4. Problem: why is documenting important to modeling? Internal Communication communication with customerHow to communicate aroundyour model ? ReferenceHow to go from design Data … all the more wheninformation (model) about (Models) youre modelingyour system, to documenting Service Orientedthe developed, operated,usable system ? Architectures (SOA)!How to keep a referencealong the life of your Assessmentsystem ? (Testing, monitoring, ...) 13/06/2012
  5. 5. Problem: Does it ring a bell?• Do you have such problems ? – How do you handle it right now ? – (already asked at JUG Grenoble)• or...• Do you find this interesting for you ? – What, how, who – (talking with Obeo, Xerox, Talend / Eclipse SOA)13/06/2012
  6. 6. Problem: what to export?• The simplest: editor files, image files – For archive, for reference, for description• More advanced: a refined, componentized model extracted from the editor model – Example: an SOA “System” entity • with references to “Systems” it depends on, actors involved, target business requirements... • Each of them may carry – attached documents (editor files, image files, text documents) – meta-data (commercial name, current endpoints, source location, ...) • Browsing a tree of Systems allows for easier, business-focused13/06/2012access to data
  7. 7. Problem: documenting from Eclipse PNG PNG PNG Eclipse editor model Informal *.doc knowledge *.odt *.html ... P:projectssaveTheWorldv123models_bak2export0023_v2_tmp.rtf Problems : local, classification, (tree) versioning, metadata13/06/2012
  8. 8. Solution: Document Management Systems (DMS)• A software brick for Enterprise Content Management (ECM)• No loss of information – Rich structure: metadata, relationships, multiple views• Consistency – Automatic versioning – Workflows – Customized model• Online: sharing, collaborative editing, discussion13/06/2012
  9. 9. Solution: We need a bridge! Eclipse Document Management System Editor model Business model Eclipse/DMS bridge Eclipse/Filesystem bridge • Consistency ! • Eclipse Resources : not enough XML, ...13/06/2012
  10. 10. Solution: Previous attempt Seen here last year !Eclipse (courtesy EasiFab) Editor model Editor DMS: Business metamodel metamodel Nuxeo Business modelMangrove model Mangrove metamodel DMS-specific API DMS-specific Eclipse plug-in DMS plug-in protocol Bridge13/06/2012
  11. 11. Solution: Generic Eclipse/DMS bridge requirements• One-way synchronization – Export the editor model to the DMS – But do not perform dummy overwrites • Content can be generated on the DMS from other sources• DMS-agnostic• Business model-agnostic – It should adapt to any business model on the DMS side13/06/2012
  12. 12. Solution: our two cents Eclipse CMIS metamodel Editormetamodel DMS DMS model DMS modelEditor model Business-aware Synchronization transformation (generic)• CMIS : DMS standard interface – client : Apache Chemistry, (almost) already in Eclipse• Transformation : ATL for EMF to EMF transformation. – With several editors, an exponential number of them required => intermediate model (who said Mangrove ?)13/06/2012
  13. 13. Solution: overall architectureEditor to CMIS = to be model ATL developedtransformation according to Input ATL VM editor & DMS business Editor models model CMIS EMF model Matching strategy Input Synchronizer CMIS DMS Sync filtering strategy 13/06/2012
  14. 14. Case study: Demo13/06/2012
  15. 15. Case study: EasySOA EasySOA : SOA registry & management solution – Built on the Nuxeo DM document management solution • contributed to Eclipse RT as Eclipse Content Repository “Apricot” – Documents classified along a “light” SOA model • Views, search, collaborative edition & publishing ; upcoming : wiki • Comments, annotated preview, social activity, dashboard • Extracted & manual service documentation – Allows to answer to : • how to use this service ? which is the right WSDL ? • Where is my endpoint / all endpoints for a specific test ? Is it up ? • How does it all contribute to the target business requirements ? Is it as expected ?13/06/2012
  16. 16. More to come...• EMF - ECM integration – Gather community & interested people (you ?) – Improve the prototype: • UX : When to trigger sync? – Automatically on save, File > Export, … ? • Business Integration : What to customize in the Synchronizer? – The other way round: extract information from the DMS – EFS CMIS “driver” : Store editor files directly in a DMS• More (Easy) SOA repository-specific features – Advanced query, tracking changes, validation, links (to online documentation, tools, SOA dashboard...) – JWT13/06/2012 subprocesses as SOA Systems
  17. 17. What about you, now? www.easysoa.org github.com/easysoa easysoa-dev@googlegroups.com13/06/2012

×