Alfresco Software’s CMIS-compliant Enterprise CMS, Alfresco Enterprise 3.3

What's CMIS?
Now that CMIS (Content Management Interoperability Services) is an authorized OASIS standard, life should become simpler for people making an attempt to access their content repositories through multiple tools. An extension of the current SOAP requirement, CMIS makes it feasible to store documents in a CMIS-compliant repository and then access them from any CMIS-compliant application.

The advantage here is that there isn’t any need to grasp which repository you are talking to. Naturally, no standard is really worth the bits it's recorded on if people don't go along with it. It is fortunate that CMIS is backed by major players in the Enterprise Content Management industry, including Adobe Systems Incorporated, AIIM, Alfresco Software, IBM and Microsoft.

CMIS and Drupal
Content services tools for IBM Lotus, Microsoft Outlook, Drupal and Google Docs is a part of Alfresco Enterprise Edition 3.3. An example of how dynamic CMIS is enabling you to access your content from a spread of tools.

According to Chris Fuller of Optaros, during the past, to integrate and have interaction with an Alfresco repository, you had to use their Web Scripts. But your same code was not then conveyable enough to use with repositories from other sellers, making you copy your work if you used solutions from more than one seller.

CMIS permits you to abstract this process so that you can write your code once and use it with any repository. When referring to Drupal, Fuller says that while the open-source CMS's strength is in a forceful, flexible show framework, there are good reasons some would like a CMIS-compliant repository on the back end in place of utilizing Drupal's file management tools:

1. The File Framework module can do file format transformations and basic workflow jobs, but a specialized product like Alfresco offers a much more complex and sophisticated workflow system.
2. There’s truly no file security in Drupal for your documents.
3.An establishment with ECM already in place will not wish to move all of their documents into Drupal, there isn't any sound excuse to scrap all the work they have already done, integrate the ECM backend with Drupal.

The Drupal CMIS assimilation module set implements the CMIS API for Drupal, with no further software needed on the other side of things. With this set of modules installed, you can:
*Get basic information about the repository and guarantee access is working
*View contents of the repository and their properties
*Drill down into folders inside the repository
*Create folders and content in the repository
*Upload content to the repository and up till now have it exist in a Drupal node where you can rate, comment and carry out anything else that can be done with a Drupal node
*Search the repository, limited by your access authorizations
*Kick off workflows and transforms you made inside Alfresco (so for example, when you drop a Word document into a selected folder, Alfresco creates a PDF of that document immediately