eXo Platform Technical Documentation

This wiki includes the documentation for all the eXo Platform products as well as the one for the kernel and core of the Platform.

You can also look at the eXo Blog for less technical news and information as well as the Overview page. We have also recently published a new article on InfoQ, please check it.

To quickly download and install the product, please read Quickstart

This home page introduces all the existing eXo components from a high level point of view. For a more technical and architectural definition please refer to Overall architecture.

The roadmap for all those components is also available and regularly updated by eXo product managers.

You can also refer to the service full index that describes all the service available in the platform.

eXo Developers will find useful information here

For commercial information please contact us at "sales@exoplatform.com", read our Business Model section or browse our web site

eXo Products

Portal

eXo Portal 2.x is a new generation of portals that leverages AJAX technology to push the ergonomics much further.

It also mixes into a coherent workspace portlets (JSR 168 and 286) and gadgets allowing you to easily and securely deploy your applications

That version is based on the Kernel and Core foundations as well as the eXo PC and the eXo JCR that is used to store user/groups preferences such as their own dashboard configurations.

Read the documentation

WebOS

The eXo WebOS product in its new version comes with a revolutionary user interface. The ergonomics have been pushed forward to provide a unique experience inside a browser. We reproduces the usual desktop multi windows behavior within the browser.

Check the Introduction, if you need a high level introduction of the eXo WebOS goals.

For more details on it please check the WebOS page

Enterprise Content Management (ECM)

The eXo ECM product provides advanced Content Management features and is built on top of eXo JCR and eXo Portal.

Document Management with workflow capabilities, Records Management, Versionning, Metadata extractions and advanced search are natively supported.

Thanks to the new user interface of eXo Portal 2.x and web 2.0 technologies the eXo ECM also comes with a true revolutionary interface that was never seen in any ECM system today. By providing a File System environment very close to what people are used to in usual Operating System we allow anyone in the company to feel comfortable with ECM functionality.

Read the documentation

Collaboration Suite (CS)

The eXo Collaboration suite provides a set of collaborative applications such as Shared Calendars, WebMail or Contact List.

The idea of those is to leverage all the AJAX advantages such as an efficient user interface and a powerful eXo JCR storage.

Read the documentation

Knowledge Suite (KS)

eXo Knowledge Suite focuses on knowledge sharing in the enterprise.

So far, KS is made of 2 applications:

• Forum: The forum management application
• FAQ: The Frequently Asked Question application

Both have an independent service, respectively Forum Service and FAQ Service. Both use the JCR API as their storage facility.

Read the documentation

Liveroom (LR)

Liveroom is made of 3 applications:

• Chat: is an instant messaging client
• Whiteboard: allows realtime whiteboarding
• Video: is a video conferencing application

Chat application is a webui portlet decoupled from its Chat Service. Cometd Service is a server push technology to provide realtime updating of the chat client. Whiteboard and Video both use the same Liveroom Service. JCR is used for persistent storage such as chat conversations and whiteboard charts. All applications use a REST binding of the Organization API.

Read the documentation

eXo Core Fundations

Kernel

This section contains all the information about eXo Kernel which is an IoC container with advanced capabilities like plugins, listeners or init paramaters all though a powerful XML configuration syntax.

Read the documentation

Core

The Core project includes all the default services that can be reused in many context such as the Organisation and Authentication services as well as the LDAP service and several others.

Read the documentation

Java Content Repository (JCR)

The eXo JCR product is an optimized implementation of the JSR 170 specification. It supports all the features of the spec including all the optional ones like SQL search, versionning, observation or transactions.

It also comes with many extensions such as REST, WebDAV, DeltaV, DASL, FTP or CIFS protocols support as well as many plugins such as Kofax (for OCR and scanning) or Office ones (OpenOffice and Microsoft Office plugins are available to remotely create and collaborate on documents). Features like clustering, dynamic registration of storage repositories and workspaces, advanced security, dublin code support, auditing or optimization for large files storage are also supported.

That product can be easily embedded in many environments, it is the optimal product for ISV and OEM vendors.

Read the documentation

Portlet Container (PC)

eXo Portlet Container is the implementation of two Specifications, the Portlet API and the Web Service for Remote Portals (WSRP) one all integrated in an optimized package.

The current stable version is the implementation of Portlet API 1.0 (JSR 168) and WSRP 1.0.

eXo PC 2.0 beta also supports the incoming Portlet 2.0 (JSR 286 release candidat 1) specification and the WSRP 2.0 one.

This implementaion is used by several OEM vendors that wish to rely on an powerfull light porlet container with a clean Service Provider Interface (SPI).

Read the documentation

REST and Web Service layer

All web services components live in eXo Container. The main component is REST Core which is eXo implementation of JAX-RS (JSR311) standard. It allows virtually any eXo Container service to offer REST API. A JSON Framework (JavaScript Object Notation) allows transforming java objects into json to be easily consumed by javascript client applications. It is very convenient for widgets. The XFire Connector brings SOAP webservices to the platform. It allows virtually any JSR181 annotated service running inside the eXo Container to be exposed as a SOAP web service. The Cometd service is a server to client push service that eXo platform uses mainly for notification directly to the client (reverse-ajax).

Read the documentation