Below is a feature comparison between Alfresco, Jahia, and Sharepoint
| Alfresco | Jahia | SharePoint |
| WEBDAV Support Collaboration happens via WEBDAV only
| WebDAV, virtual file system |
| Apache Lucene based Text Search Engine
| Open Search |
| Limited meta data extraction from files
| Automatic Meta data extraction |
| WebDAV Support
| WebDav, Web services, File system |
| Format conversion support | Format conversion service available also ability to use custom doc conversion service |
| Portal support (JSR 168),JSR 170 | WSRP port-lets consumer out of the box. Provider using customization/third party tools |
| n/a | n/a |
| n/a | Yes |
| n/a | yes |
| NO | User presence |
| ? | Email integration |
5 comments:
Hi interesting comparison. However, AFAIC, it seems to me that you are more comparing bananas and apples rather than real side-by-side competitors. Alfresco is more a true ECM/DMS system. Sharepoint is more a Portal/collaborative system (even if largely used as a way to store and share departemental documents) and Jahia is mainly a front-end WCM system.
The goal of back-end ECM system is to store and manage critical document assets. WCM systems are really another stories as the main goal is to focus on "(virtual) sites building and management". So Jahia competes more with WCM such as Drupal while Alfresco more with ECM such as Documentum. A key business value would be to connect both systems. And Jahia is currently working with it with a new "Unified Content But" mechanism. New emerging standards such as the incoming CMIS will also help go into that direction in the future. There are also integration of Alfresco and Drupal (Alfrescal: http://www.contenthere.net/2009/02/alfrescal.html ).
Interoperability will become soon key and this will perhaps tends to let the various actors focus on their core business (WCM on web content management; ECM on key company binary assets; Portals on collaboration;...).
Of course each of these actors will have to offer and support some "minors" in the other domains. But the all-in-one approach risks to become more and more difficult to implement rather than implementing some best-of-breed solutions and to play more with a "Lego" approach.
Best Regards,
Stephane
Thanks Stephane for your comments, let me give you a bit of back ground on why these packages were considered.
SharePoint was considered as a candidate as our company had the licences and the skill set, so using SharePoint would have been cost effective if it did the job.
Jahia was considered as we had bought the licence for our corporate site. Alfresco is de-facto open source document management system.
Yes interoperability is very important and that’s where I am not impressed with Jahia on integration front because of lack of web services. We are indeed using Lego in technical terms SOA approach using BPM, ESB and a document management system.
Since document management would be exposed as service on ESB the applications using document management features would not be aware of which document management systems is working behind the scenes
Hi,
I can understand considering the opportunity to use a product when you already own a license, but I fail to see the logic in using something that's not really a DMS as a DMS, losing the benefits of SOA in the process...
Still, when you say Jahia doesn't offer any Web Services, I'm pretty sure you can write your own Web Services for Jahia as it integrates Axis. Your need doesn't seem to involve WCM anyway, so I guess Jahia doesn't really fit into the picture.
Your SOA/ESB approach looks like the right thing to do, as it allows you to use the "best tool for the job" for each functional need. And it would allow you to replace whatever product you're going to use right now with the Next Big Thing that will hopefully come out in a year or two (as things seem to be moving pretty fast in the world of DMS / WCM / Portal these days).
Best regards,
Tarek
Its really informative ...thanks for sharing...
Regards,
Document management services
Jahia as a WCM is much better. It is easy to install, and in-context editor makes it very easy for end user to edit html files.
Post a Comment