Liferay’s Enterprise Portal 6.1 Supports CMIS, Integrates Enterprise CMS Document Repositories
After announcing in a blog post last February that it was looking at introducing full compatibility with CMIS standards in its Portal EE 6.1 release, Liferay (news,site) has confirmed that the upcoming release will, in fact, come with that compatibility.

It hasn’t said when exactly that release will be, but given today’s announcement, it should be soon, as, it appears that it has achieved those standards, as described in February.

This means that Portal EE 6.1 will be able to integrate a lot easier with the document repositories of third-party enterprise content management systems, and in this regard it has specifically mentioned SharePoint and Documentum.

Liferay and CMIS: Adding repositories      
Liferay and CMIS: Adding repositories

This gives our Enterprise users easy access to data no matter what repository the documents are stored in. As Liferay itself becomes a strategic platform throughout their enterprise, we are committed to making access to data as seamless as possible,” said Alexander Chow, Senior Software Engineer at Liferay, who implemented the CMIS standard.

CMIS v1.0

CMIS stands for Content Management Interoperability Services and provides a common language and vendor-neutral formats for enterprise content management and other information management systems to interact. CMIS v1.0 being ratified as an OASIS standard in April 2010.

This was the result of a cross-industry effort from companies such as Alfresco, Day Software (now Adobe), EMC, IBM, Nuxeo, Microsoft, Open Text, Oracle and others.

CMIS commonly enables document exchange between more internally focused Enterprise CMS systems and more publicly oriented Web CMS solutions, though there are many use cases found in practice.

Liferay, CMIS

Liferay has been working on the CMIS standards since they were finalized, with a view to incorporating them into its document repositories.

While the Java Content Repository (JCR) standard has been around for considerably longer, CMIS has a major advantage over it because it is not Java-bound so it covers libraries for Python, PHP and .NET, among others.

With Liferay 6.0 then, Liferay added a CMISHook, but, Chow says, the CMISHook was just a first step. The next step was to redesign the Document Library to support multiple repositories mounted for each document library portlet.

And in v6.1 Liferay says, it has done just that. There is no indication of when v6.1 will be released, but it should be soon, given that Liferay has announced that the integration is now completed.