This chapter provides you the basic knowledge of eXo CMIS, working principles and how to configure it via the following topics:
{docbook}
<abstract>
<itemizedlist>
<listitem>
<para>
<link linkend="Adm_CMIS.Introduction.CMIS_specification">CMIS Specification</link>
</para>
</listitem>
<listitem>
<para>
<link linkend="Adm_CMIS.Introduction.xCMIS_project">xCMIS project</link>
</para>
</listitem>
<listitem>
<para>
<link linkend="Adm_CMIS.Introduction.eXo_CMIS">eXo CMIS</link>
</para>
</listitem>
</itemizedlist>
</abstract>
{docbook}
h1. CMIS Specification {anchor:id=Adm_CMIS.Introduction.CMIS_specification}

{info}
Content Management Interoperability Services (CMIS) Version 1.0
OASIS Standard 
1 May 2010

[http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services]
{info}

The Content Management Interoperability Services (CMIS) standard defines a domain model and Web Services and Restful AtomPub bindings that can be used by applications to work with one or more Content Management repositories/systems.
The CMIS interface is designed to be layered on the top of existing Content Management systems and their existing programmatic interfaces.
It is not intended to prescribe how specific features should be implemented within those CM systems, nor to exhaustively expose all of the CM systems capabilities through the CMIS interfaces. It is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities.

The CMIS specification provides a Web service interface that:
* Is designed to work over existing repositories, enabling customers to build and leverage applications against multiple repositories.
* Decouples Web services and content from the content management repository, enabling customers to manage content independently.
* Provides common Web services and Web 2.0 interfaces to dramatically simplify the application development.
* Is a development platform and language agnostic.
* Supports the composite application development and mash-up by the business or IT analysts.


h1. xCMIS project {anchor:id=Adm_CMIS.Introduction.xCMIS_project}

The xCMIS project [http://xcmis.org/], initially contributed to the Open Source community by [http://www.exoplatform.com|eXo Platform], is an implementation of the full stack of Java-based CMIS services. 
xCMIS also includes the client side frameworks for integrating content from different enterprise repositories, according to the [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis|CMIS standard]. 

The project is distributed under the LGPL license. 
You can download sources at [http://code.google.com/p/xcmis/source/checkout|Google code],
or visit [http://code.google.com/p/xcmis/w/list|Community Wiki] for more information. 

h1. eXo CMIS {anchor:id=Adm_CMIS.Introduction.eXo_CMIS}

eXo CMIS is one eXo Platform service exposing eXo Content via CMIS.
eXo CMIS offers the way to access the eXo ECMS content from the CMIS 1.0 compatible Web client using the REST Atom protocol.

{note}
WS-SOAP/WSDL binding is also supported, but it is not delivered in the standard eXo Platform 3.5 bundle.
{note}

eXo CMIS is built on the top of xCMIS embedded in eXo Platform to expose the WCM drives as the CMIS repositories.
The CMIS features are implemented as a set of components deployed on the eXo Container using XML files to describe the service configuration.

!images/exo-cmis-wcm.png|align="center", width="70mm", fo:scalefit="1",html:scalefit="0"!


WCM drives exposure is implemented as WCM storage provider to xCMIS SPI. 
The storage provider uses mappings from WCM's _ManageDriveService_ to actual JCR nodes, and the _AtomPub_ bindings makes WCM structure available via CMIS standard API.
