Archive for category General
Documentum’s APIs vs CMIS
Posted by Nico in General, Presentation on 9. March 2010
I just found an interesting PowerPoint presentation from EMC that describes the difference between the Documentum API and CMIS.
See how Documentum’s web services pulls together CMIS for standards based interoperability and integrations, DFS for building and extending your client applications, and RESTful services for Rich Internet Application mash-ups.
Based on the presentation there are four main Use Cases of CMIS:
- Multi-Repository
- Application + ECM Integration
- Build Once, Use Often
- Migration
The slides offer a general guideline of usage only, as there are no hard and fast rules on which technology should be used when. The PowerPoint presentation can be downloaded here.
CMIS experience at CeBIT 2010
This year I’ve been at the CeBIT with my company ARITHNEA. CeBIT is the world’s largest trade fair showcasing digital IT and telecommunications solutions for home and work environments.
We’ve presented our new CMIS module for the Web Content Management System FirstSpirit.
This module is called “DMS connect” and is responsible for the connection to the repositories of Sharepoint and Alfresco using CMIS. The module helps to easily publish documents to websites.
I showed this module to several people. Almost all of them thought that this will bring a big benefit to their publication process.
Since the CeBIT I am really sure that CMIS will become a big success!
Microsoft has just joined the 2010 AIIM CMIS Demo
I just read it on Twitter by Laurence Hart.
#Microsoft has now joined #EMC, #Alfresco, #Nuxeo, & #IBM in supporting the #AIIM #CMIS demo for #aiim10. #ECM
If you like to know more about the 22010 AIIM CMIS demo or if you like to participate check the following blog post for more details.
Fundamental use cases for CMIS
Thomas Pole and Laurence Hart mentioned three fundamental use cases for CMIS:
- Repository to Repository: This is the direct communication between repositories. This most often occurs when content needs to be managed from a central, “master”, repository.
- Application to Repository: This is when an application that uses content stores that content in an external repository. Through the use of CMIS, the application can focus on providing its core business solution without managing the content or integrating with different repositories that may each have their own API.
- Federated Repository: This is the presentation of a collection of repositories to a user or application as a single repository. This model occurs frequently when users need to combine the services and information available from multiple systems to satisfy searches for content across a scope larger than any individual department.
Thomas Pole is the chair of the iECM committee and Laurence Hart is a member of the iECM committee
Source: The AIIM iECM CMIS Demo
What CMIS Will Do for Content Integration
Andrew Conry-Murray wrote an interesting article about Content Integration with CMIS. Andrew is business editor at InformationWeek and Network Computing.
Will unstructured content be the next frontier for BI? There’s hope that Content Management Integration Services (CMIS) will do for content what SQL did for databases.
After reading the whole article you can download an interesting report:
Silo to Gold Mine: What CMIS Can (and Can’t) Do for ECM Integration.
The full article can be read here.
8 reasons why CMIS will transform the ECM industry
Stefan Waldhauser posted in the AIIM blog 8 reasons why CMIS will transform the ECM industry
These 8 reasons are:
- CMIS is the SQL for Content Management.
- CMIS is not just another standard.
- CMIS is already well accepted by the customers.
- No more lock-in to one ECM-vendor because of CMIS.
- With CMIS the ECM infrastructure will become commodity.
- CMIS-based applications will become the differentiator.
- CMIS will help to create a 360° view on your customers.
- CMIS 1.0 is just the beginning.
If you want to read the full story click here.
Three reasons to list CMIS in your Document Management RFP
Alan Pelz-Sharpe, Principal at CMS Watch, just posted three reasons why CMIS should be listed within your Document Management RFP.
- If you have legacy document repositories, add CMIS to your list of requirements.
- If the system you buy has a CMIS API, then you go some way to avoiding vendor lock-in at a future point.
- You demonstrate to the vendors on your shortlist your intentions and industry savvy.
If you like to read the full text follow the following link.
Overview picture on CMIS, JSR and OSGi
CMIS / JCR by Jon On Tech
I just found an amazing overview on the blog “Jon on Tech”.
He drew a picture regarding the coherence of CMIS, JSR and OSGi.
Check his post “CMIS, JCR and OSGi for Idiots” for further details.
There you can get the full size of the picture and a PDF download.
MOSS 2010 and CMIS
According to the post of Ethan Gur-esh in the msdn blog Microsoft will support CMIS with SharePoint 2010. But Microsoft will wait until CMIS 1.0 is officially released.
An interesting quote from Ethan regarding CMIS:
At this point, pretty much every vendor in the ECM space is really motivated to start supporting CMIS in their respective products. We’ve all seen the excitement from customers about CMIS — for example, a recent AIIM survey showed that 15% of organizations are already interested in using CMIS. (This is an unbelievable number for a standard that isn’t even final yet!)
Alfresco offers CMIS Webinar
Alfresco is hosting the first CMIS virtual training session designed to explore the specification and share CMIS expertise.
Click here to register for the event at the Alfresco homepage and to get further details.
When: November 24 2009
Where: Online Webinar 11am EST
Last Comments