Apogée Project
The Rich Client Framework for ECM
Eclipse Project > Proposal > Creation Review
27 April 2006
Éric Barroca
eb@nuxeo.com
Enterprise Content Management ?
· ECM ?
· Convergence of all non-accountable data management softwares in an organization
· See: http://en.wikipedia.org/wiki/Enterprise_content_management
· Some ECM vendors: ECM/Documentum, Intervowen, Nuxeo, OpenText
· Why a rich client when there is the browser?
· For document-oriented work, the browser is not enough
· Deep integration with the desktop required
· O ine work and synchronization
· Responsive and rich interface -> keep the user in a known environment
· The browser is not a window manager neither HTML is a UI toolkit...
· ...at least not for users!
· Why a framework ?
· ECM-oriented application are very di erent
· Need a lot of customization when deploying solutions for customers
· Share a lot a common infrastructure
Project Goals
· ECM, the Eclipse way!
· Build a core infrastructure and a family of components targeted to ECM-
oriented desktop applications.
· Components should be independent enough to be used separately
· Leverage industry standard and existing open source components
· Vendor-neutral -> any ECM platform should be able to use and create
connectors for Apogée
· O er user-friendly tools
· No bloat-ware -> think user experience and e ciency
Functional Scope
Applicative components
Mail Client
Calendar
Whiteboard
BPM
(Eclipse BPEL)
Content
Collaborative
IM
etc.
Editors
Workspaces
(ECF)
Core Infratructure
Remote
Content Type
Sync
Search
Interface
(SyncML)
Service
Content
Indexing
Cache
XForms Engine
Model
(Apache Lucene)
Storage
Security
Relations
Content
Service
(ETF)
Engine
Schemas
JCR
RDF DB
(Apache Jackrabbit)
(Jena)
Standards and tools
· Java Content Repository (JSR-170) as storage engine
· Apache Jackrabbit
· XForms
· Eclipse Forms generation from XForms
· Enable form sharing between Apogée and the server
· XMLSchemas
· Content schemas
· JCR NodeTypeDe nitions generation
· XForms validaiton
· SyncML
· Enable o ine work
· RDF
· Relation Storage
· Jena based
Eclipse touch points
· RCP for framework infrastructure
· ECF for communication and synchronous collaboration (IM, shared
whiteboard)
· ETF for security and authentication
· WST for web-service support
· BIRT for activity audit and reporting
· XXX add diagram
Project's team and supporters
· Proposed Project Manager -> Eric Barroca (Nuxeo)
· Proposed Technical Lead -> Bogdan Stefanescu (Nuxeo)
· Commiters
· Cédric Bosdonnat (Nuxeo): content editors and synchronization
· Eugen Ionica (Nuxeo): relation and search services
· Carl Rosenberger (db4objects): storage
· Interested parties
· AFP (French Press Agency) (consumer)
· AREVA NC (consumer)
· French Institute of Statutory Auditors (consumer)
· db4objects (commiter)
Project Status
· Design
· Overall architecture -> Done
· Content storage and model -> Done
· XForms engine and XMLSchemas validator -> Done
· Relation engine -> Done
· Security -> To do
· Development
· Currently takes place at svn.nuxeo.org/pub/Apogee
· Global infrastructure -> Done
· Jackrabbit integration, content model -> Done
· XForms engine and XMLSchemas validaiton -> Done
· Synchronization -> work on the way
· Content Editor (MSO ce, OpenO ce and Mozilla Composer) -> Done
· Community
· 70+ subscription to the mailing-list
· Website online at apogee.nuxeo.org
1.0 Timeline
· M1 - April 2006
· M3 - August 2006
· [CP] Technical speci cations of the core
· [CP] Security model and service
platform (60% done)
· [CP] Form service (XForm full support)
· [CP] Resource model [done]
· [CP] Client / Server synchronization -> online/
· [CP] Relation service / RDF [done]
o ine mode
· [CP] Indexing and Search service / Lucene
[done]
· M4 - September 2006
· [CP] Rich Content editors (MSWord,
· [CP] Communication framework (SOAP
OpenO ce, XHTML) [done]
·
support)
[CP] Eclipse Forms generation service (XForms
based, alpha support, done)
· [AP] Instant Messaging (XMPP based)
· [CP] On-the- y validation of a SWT form with a
· [AP] Mail client (alpha)
XML Schema (XSD) [done]
· [AP] Calendar client (alpha)
· M2 - June 2006
· RC - October 2006
· [CP] Communication service
·
· Final - December 2006
[CP] Content type service
· [AP] Collaborative workspaces
· [AP] Rich Text Editor [done]