From Eclipse to Document management

A case study for JWT & EasySOA

Eclipse DemoCamp Juno – June 13th, 2012

1

13/06/2012

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

Agenda

I. ProblemI. Documenting & Modeling

II. Export from an editor

III. The Eclipse case

II. SolutionI. Document Management Systems

II. We need a bridge!

III. Bridge requirements

IV. Our solution

V. Overall architecture

III.Case studyI. EasySOA

II. Demo

III. JWT Blackbox

13/06/2012

Problem: why is documenting important to modeling?

Assessment(Testing, monitoring, ...)

Communicationwith customer

Internalcommunication

ReferenceData

(Models)

… all the more when you're modeling Service Oriented Architectures (SOA)!

How to communicate around your model ?

How to go from design information (model) about your system, to documenting the developed, operated, usable system ?

How to keep a reference along the life of your system ?

13/06/2012

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

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-focused access to data

13/06/2012

Problem: documenting from Eclipse

*.doc*.odt*.html

...

Eclipse editormodel

P:\projects\saveTheWorld\v123\models_bak2\export0023_v2_tmp.rtf

PNGPNGPNG

Informalknowledge

Problems : local, classification, (tree) versioning, metadata

13/06/2012

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, discussion

13/06/2012

Solution: We need a bridge!

Eclipse Document Management System

Eclipse/DMSbridge

Editor model Business model

Eclipse/Filesystembridge

XML,...

• Consistency !• Eclipse Resources : not enough

13/06/2012

Solution: Previous attempt

Eclipse

DMS:Nuxeo

Editor model

Business model

Editormetamodel

Business metamodel

Bridge

DMS-specificprotocol

DMS-specificAPI

Mangrove modelMangrovemetamodel

Eclipse plug-in DMS plug-in

Seen here last year !(courtesy EasiFab)

13/06/2012

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 side

13/06/2012

Solution: our two cents

Eclipse

DMS

Editor modelDMS modelDMS model

Synchronization(generic)

Business-awaretransformation

CMIS metamodel

Editormetamodel

• 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

Solution: overall architecture

DMSInput Synchronizer CMIS

Matchingstrategy

Syncfilteringstrategy

Editor to CMISmodel ATL

transformationInput

Editormodel

ATL VM

CMISEMF model

= to be developed according to editor & DMS business models

13/06/2012

Case study: Demo

13/06/2012

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

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...)– JWT subprocesses as SOA Systems

13/06/2012

What about you, now?

www.easysoa.org

github.com/easysoa

easysoa-dev@googlegroups.com