Monday, February 6, 2012

Content Repository vs. Web Content Management system

Web content management system (WCM) is often defined as "a software system that provides website authoring, collaboration, and administration tools designed to allow users with little knowledge of web programming languages or markup languages to create and manage website content with relative ease".

Modern web content management systems offer many advanced features for managing and publishing digital content (text, images, documents, multi-media, etc.) to websites, and for many scenarios a WCM product or system will meet the needs of content publishers.

But the traditional web content management system, focused on presenting web pages to a browser, is no longer necessarily the right choice for managing and delivering content in a multi-device, multi-channel, content-syndicated world.

Especially when :
  • digital content needs to be shared between disparate websites,
  • content needs to be delivered to the different kinds of devices or channels (mobile phones, tablets, kiosks, Facebook, Google+, etc.), or syndicated via an API,
  • exist a real need for integration of distributed resources of informations and documents
a WCM system focused on serving HTML pages is often not sufficient.


In different approach the organization can introduce Enterprise Content Management system, with the Content Repository as a heart of this system. In this approach the content is stored and managed in repository, served from central point to external applications, and additional built in services like:
  • full text search with document content search (indexing content of PDFs, DOCs and so on)
  • optical character reckognition
  • versioning
  • format conversion
  • identity (authorization, authentication, accountability)
  • built in workflow processing
can be provided. More generally, you would also need to buy or develop a Content Platform around the Content Repository to provide the features and services meeting your demands.


Why to choose Java Content Repository?

The Content Repository for Java Technology specification, developed under the Java Community Process as JSR-170 (for the first version, JCR 1) and JSR-283 (for JCR 2), aims to meet all industry needs of modern Content Repository system. What more: this is approved industry standard - cause of this customer can choose from range of vendor specific but compliant(and therefore interchangeable) implementations. Additional advantage of JSR-170/283 is that it is not tied to any particular underlying architecture, but still client applications can cooperate with each implementation.

Summing up the benefits of choose of JCR technology we can point:
  • JCR is an open industrial standard, well suited for document management and content management
  • JCR is wide adopted by potentates of software market like IBM, Oracle, Adobe and by most important opensource providers like Apache Software Foundation. Cause of this we can consider this technology as solution with stable and long term support
  • Cause of wide adoption there are available products suitable for middle size companies as well as high end products for big enterprises
  • Implementing JCR repository customer is not necessarily linked to a single supplier
  • There are available free and commerial useful utilities and tools (eg. for administration purposes)
  • Java Content Repositories are the perfect solutions designed to act as a central storage of documents of each company.
  • JCR repositories delivers wide range unique document oriented services. Even open source referential implementation Jackrabbit delivers many functionalities not available for any WCM system.

The most advanced commercial JCR are:
  • Adobe CRX
  • Oracle UCM
  • IBM Content Management
  • Magnolia CMS
  • Alfresco CMS
  • eXo platrofm repository
  • and so on

and the most important opensource implementation is
  • Apache Jackrabbit
As shown before, the typical user of a Content Repository is another software application rather than a user directly. In modern enterprise content delivery systems content repository becomes role simillar to database server in database driven applications.

Enterprise content management

As defined in Wikipedia: ECM is an umbrella term covering document management, web content management, search, collaboration, records management, digital asset management (DAM), work-flow management, capture and scanning. ECM is primarily aimed at managing the life-cycle of information from initial publication or creation all the way through archival and eventually disposal. ECM applications are delivered in three ways: on-premise software (installed on the organization’s own network), Software as a Service (SaaS) (web access to information that is stored on the software manufacturer’s system), or a hybrid solution composed of both on-premise and SaaS components.

ECM aims to make the management of corporate information easier through simplifying storage, security, version control, process routing, and retention. The benefits to an organization include improved efficiency, better control, and reduced costs.

4 comments:

  1. just linked this article on my facebook account. it’s a very interesting article for all.


    Document Management Software

    ReplyDelete
    Replies
    1. Hi, Great.. Tutorial is just awesome..It is really helpful for a newbie like me.. I am a regular follower of your blog. Really very informative post you shared here. Kindly keep blogging. If anyone wants to become a Java developer learn from Java Training in Chennai. or learn thru Java EE Online Training from India . Nowadays Java has tons of job opportunities on various vertical industry.

      Delete
  2. Wonderful blog & good post.Its really helpful for me, awaiting for more new post. Keep Blogging!


    Document Management Systems

    ReplyDelete
  3. Thanks for this fresh look at WCM/ECM/JCR topic Mariusz!
    Today eXo exposes its WCM in cloud also (as SaaS) under Cloud Workspaces service http://cloud-workspaces.com/. Don't hesitate to try it online.

    ReplyDelete