This session describes the architecture and implementation of an embeddable, extensible enterprise content management core for Java EE and simpler platforms. The presentation starts by describing the general architectural concepts used as building blocks:
• A schema and document model, reusing XML schemas and making good use of XML namespaces, where document types are built with several facets
• A repository model, using hierarchy and versioning, with the Content Repository API for Java (JSR 170) being one of the possible back ends
• A query model, based on the Java Persistence query language (JSR 220) and reusing the path-based concepts from Java Content Repositories (JCR)
• A fine-grained security model, compatible with WebDAV concepts and designed to provide flexible security policies
• An event model using synchronous and asynchronous events, allowing bridging through Java Message Service (JMS) or other systems to other event-enabled frameworks
• A directory model, representing access to external data sources using the same concepts as for documents but taking advantage of the specificities of the data back ends
Suitable abstraction layers are put in place to provide the required level of flexibility. One of the main architectural tasks is to find commonalities in all the systems used (or whose use is planned in the future) so framework users need to learn and use a minimal number of concepts. The result is a set of concepts that are fundamental to enterprise document management and are usable through direct Java technology-based APIs, Java EE APIs, or SOA. The presentation shows, for each of the main components, which challenges have been met and overcome when building a framework in which all components are designed to be improved and replaced by different implementations without sacrificing backward compatibility with existing ones.
The described implementation, Nuxeo Core, can be embedded in a basic Java technology-based framework based on OSGi (such as Eclipse) or in one based on Java EE, according to the needs of the application using it. This means that the core has to function without relying on Java EE services but also has to take advantage of them when they are available (providing clustering, messaging, caching, remoting, and advanced deployment).
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Nuxeo JavaOne 2007
1. Building an Embeddable
Enterprise Content Management
Core With the Latest Java
Technologies
Florent Guillaume
JavaOne 2007 (TS-4532)
2. Goal Of This Talk
Learn about the design and use of Nuxeo™ 5,
an embeddable, extensible
Enterprise Content Management framework
for Java™ EE and other platforms
3. Agenda
What is Enterprise Content Management
What do we want to achieve
Core Framework
Core and High-Level Services
UI Layers
Extensible and Pluggable
Using the Framework
5. What is
Enterprise Content Management?
2000–20...
Documents (Records, E-Mail, Media)
●
Imaging
●
Search Engine
●
Archiving
●
Unification ECM
Collaboration
●
Web Publishing
●
Access Control
●
Compliance
●
6. What is
Enterprise Content Management?
The technologies used to
capture
●
create
●
manage
●
store
●
preserve
●
reuse
●
deliver
●
content within the
enterprise
7. Agenda
What is Enterprise Content Management
What do we want to achieve
Core Framework
Core and High-Level Services
UI Layers
Extensible and Pluggable
Using the Framework
8. What do we want to achieve?
Create a Framework
●
Make it Extensible
●
Make it Multi-Platform
●
Use the Latest Technologies
●
Open Source
●
9. What do we want to achieve?
Create a Framework
●
Set of Services
●
Software Bundles
●
Set of APIs
●
Open to other systems
●
Configuration
●
XML rather than code
●
10. What do we want to achieve?
Create a Framework
●
Make it Extensible
●
New services
●
New backends to existing services
●
11. What do we want to achieve?
Create a Framework
●
Make it Extensible
●
Make it Multi-Platform
●
POJOs
●
Java EE
●
Clusterable, distributable
●
Eclipse
●
Rich Client Platform (RCP)
●
Mix of those
●
RCP client, Java EE server
●
12. What do we want to achieve?
Create a Framework
●
Make it Extensible
●
Make it Multi-Platform
●
Use the Latest Technologies
●
Java 5, Java EE 5
●
OSGi
●
JCR (JSR-170, JSR-283), W3C XML Schemas
●
JSF, Facelets
●
BPEL, WfMC
●
SOAP, WSDL
●
13. What do we want to achieve?
Create a Framework
●
Make it Extensible
●
Make it Multi-Platform
●
Use the Latest Technologies
●
Open Source
●
LGPL, EPL
●
http://www.nuxeo.org
●
14. Agenda
What is Enterprise Content Management
What do we want to achieve
Core Framework
Core and High-Level Services
UI Layers
Extensible and Pluggable
Using the Framework
28. Core Framework: Security ACLs
Basic Access Control Entry (ACE)
●
DENY Read to Anonymous
●
GRANT Write to group:Developers
●
Ordered List
●
Manipulated by different services
●
User assignment
●
Workflow
●
Record management locks
●
Placeful and Inherited
●
29. Agenda
What is Enterprise Content Management
What do we want to achieve
Core Framework
Core and High-Level Services
UI Layers
Extensible and Pluggable
Using the Framework
30. Core Services
Event System
●
Directories
●
User Manager
●
Query
●
34. Core Services
Event System
●
Directories
●
User Manager
●
Bridge directories and user authentication
●
Interfaces with the application server
●
Global defaults
●
36. Core Services: Query
SELECT * FROM Documents WHERE
dc:title LIKE 'JavaOne%'
SELECT * FROM Documents WHERE
dc:modified >= TIMESTAMP '2007-01-01T00:00:00'
SELECT * FROM Documents WHERE
ecm:path STARTSWITH '/customers/proposals'
40. Layered Framework: Workflow
EJB
Seam WF Client
WF Facade Doc Facade
Workflow API WF Doc API Nuxeo Core API
WF Core
Doc Core Nuxeo Core
jBPM
41. Agenda
What is Enterprise Content Management
What do we want to achieve
Core Framework
Core and High-Level Services
UI Layers
Extensible and Pluggable
Using the Framework
45. Agenda
What is Enterprise Content Management
What do we want to achieve
Core Framework
Core and High-Level Services
UI Layers
Extensible and Pluggable
Using the Framework
46. NXRuntime: Extension Points
Nuxeo Core Blog Module
Comment Service Blog Extensions
Type Service
Storage Module
Storage Service Jackrabbit Storage
49. Services are Pluggable
Internal Service Provider Interfaces (SPI)
●
Repository Backend
●
Directory Backend
●
Workflow Service
●
Indexing Service
●
Relation Service
●
Transformation Service
●
50. Plug into Different Platforms
POJO Bundles
●
OSGi Dependencies
●
Extension Points
●
Generic Lookup Service
●
Java EE Deployment
●
JBoss
●
GlassFish
●
...
●
51. Plug into OSGi
OSGi as Basic Format
●
JAR
●
Meta-Information
●
NXRuntime
●
Extension points
●
Definition
●
Contributions
●
Specialized Deployment
●
52. Plug into Java EE: Problems
Modules hard to reuse on other platforms
●
XML module descriptors don't allow fragmentation
●
Hardcoded package names in code or XML
●
Cannot add functionality without redeploying the entire
●
application
No extension model (plugins)
●
54. Agenda
What is Enterprise Content Management
What do we want to achieve
Core Framework
Core and High-Level Services
UI Layers
Extensible and Pluggable
Using the Framework