Archive for the ‘xCMIS’ Category

eXo Delivers Web Content to Enterprise Java

Wednesday, June 16th, 2010

eXo Web Content Management 2.0 now available as open source download

San Francisco, Calif. (June 15, 2010) – eXo (http://exoplatform.com) today released eXo Web Content Management (WCM) 2.0. Bundled with GateIn 3.0 and Tomcat 6.0 to run out of the box, eXo WCM is now available as a free download under the open source Affero Gnu Public License (AGPL). Commercial support for eXo WCM will be available as part of eXo Platform 3.0, expected later this year.

Why Use eXo WCM

Like all eXo services, such as eXo Social (announced just last month), eXo WCM is designed for IT organizations that want to be able to integrate web content with their existing enterprise Java systems. eXo WCM comes with tools and extensions already familiar to Java programmers, so they can starting developing from day one.

On its own, eXo WCM provides all the modern Web 2.0 capabilities needed to create, publish and manage web content. It runs with GateIn, the advanced new portal framework created by eXo and Red Hat, so users now have content management inside a portal. Users can integrate  applications in the portal and manage all the content from the same user interface.

With eXo WCM as a core piece of the eXo Platform, Java enterprises have a comprehensive user experience platform for integrating intranet, Web and transactional applications – similar to what SharePoint provides for .NET.

Highlights of eXo WCM

Visit the eXo site for a full list of eXo WCM features. Highlights include:

  • Scalable Content: eXo WCM is based on eXo JCR,  an open source implementation of the Java Content Repository specification. This implementation has been in production for several years within large productions environments with tens of thousands of users and millions of documents.
  • Ease of Use: eXo WCM makes it easy to create, approve and deploy content as part of an overall Java web application. Search, Favorites, Tagging, Voting, Cover Flows, Timelines, Versioning and Locking are all easily enabled for content users.
  • Customizability: eXo WCM can be customized to suit project needs. Users can change the content repository structure and use their own metadata, for example; choose from different content templates, or create new ones; and create specific views based on roles.
  • Extensibility: eXo WCM comes with ready extensions for adding document management and workflow. This package also includes a preview of a new authoring publication extension for more contextual and dynamic content life cycles. Users can create their own plugins and extensions to make eXo WCM work for them.
  • Flexibility: With eXo WCM, users can slice and dice their content in several ways and publish in multiple places with different workflows. Even if stored in just one repository, content can be classified in different hierarchies, tagged for public or private view and “favorited” so it can be quickly accessed from an individual’s private drive.

Supporting Quotes

Benjamin Mestrallet, founder and CEO of eXo: “With eXo WCM, Java enterprises have a complete portal and content management system in a single software package — eliminating the need to cobble together solutions from different vendors. Anyone can start using eXo WCM on its own today. But for those enterprises looking for an elegant, integrated way to modernize their Java applications, eXo WCM is a hint of what’s to come with the eXo Platform.”

Getting Started

Availability and Support

  • Download today
  • Commercial Production Support: eXo WCM 2.0 will be supported in the forthcoming eXo Platform 3.0, planned for later in 2010
  • Early Adopter Program includes one-year developer subscriptions and early access to other eXo offerings
Share this blog post with :
[Bloglines] [BlogMarks] [del.icio.us] [Digg] [dzone] [Facebook] [Furl] [Ma.gnolia] [Newsvine] [Reddit] [Slashdot] [StumbleUpon] [Technorati] [Twitter] [Email] More »

Tags: , , , , , , , ,
Posted in ECM, application, business, enterprise2, exo, jcr, open source, press, wcm, web2, xCMIS | No Comments »

Integrating a CMIS Server with Zoho Using the GateIn Portal

Thursday, March 4th, 2010

Last week we hosted a webinar to introduce the xCMIS, the new CMIS implementation from eXo.  During the webinar, Jeremi showed a live demo of xCMIS accessing and editing Zoho docs.  He has already converted this into a helpful step-by-step guide with screenshots.  But, if you missed the webinar, you can now check out a video of the demo as well:

Integrating a CMIS server with Zoho using the portal GateIn from jeremi joslin on Vimeo.

Share this blog post with :
[Bloglines] [BlogMarks] [del.icio.us] [Digg] [dzone] [Facebook] [Furl] [Ma.gnolia] [Newsvine] [Reddit] [Slashdot] [StumbleUpon] [Technorati] [Twitter] [Email] More »

Tags: , , , ,
Posted in GateIn, xCMIS | No Comments »

List of CMIS clients

Thursday, February 18th, 2010

If you want to develop an application that need to interact with a CMIS server, you might want to reuse an existing client library. We compiled for you a list of library and client. Most of them are Open Source.

Android:

  • android-cmis-browser: The Android CMIS Browser enables the user to browse and search a CMIS content repository.

Firefox plugin:

  • developing a CMIS client for firefox: This article presents an overview of a new proposed standard for accessing content, namely Content Management Interoperability Services (CMIS), and provides an example of how to use these services using Mozilla Firefox.

Flex/air:

  • CMIS spaces: CMIS Spaces RIA clients (Flex+AIR, Flex+Browser) are for ECM / CMS servers supporting the Content Management Interoperability Services standard.
  • cmis-explorer: An Adobe AIR application for browsing CMIS compliant repositories.

Java:

  • Apache Chemistry:Apache Chemistry is an effort to provide a Java implementation of the CMIS , consisting of a high-level API for developers wanting to manipulate documents, a low-level SPI close to the CMIS protocol for developers wanting to implement a client or a server, and default implementations for all of the above.
  • CMIS fileshare: CMIS FileShare comes with a simple CMIS Browser that is able to browse repositories with a CMIS AtomPub interface.

Javascript:

  • JQuery-cmis: A Javascript client for parsing response from a CMIS server using JQuery.

.Net:

  • NCMIS: Dotnet library that will implement the core of the Content Management Interoperability Services standards proposal (CMIS) along with a toolbox for building your own implementations of CMIS.
  • CMIS4Sharepoint: open source implementation of CMIS standards for SharePoint Platform (WSS3.0 & MOSS2007).

PHP:

  • CMIS API of drupal: The CMIS API project aims to provide a generic API for integrating with CMIS compliant Enterprise CMS systems.

Python:

  • CMIS lib: Provides a CMIS client library for Python that can be used to work with CMIS-compliant repositories

Shell:

  • CMIS shell: Command line client for CMIS (made in java)

Web UI:

  • Cara: web application that provides a single interface to Documentum, SharePoint and Alfresco.
  • WeWebU OpenWorkdesk: (CMIS not released yet, Q2) Suite of application on top of JSR170 and CMIS

If I forgot any library or client, ping me on twitter @jeremi or in the comments. I’m going to try to keep this list up to date.

Share this blog post with :
[Bloglines] [BlogMarks] [del.icio.us] [Digg] [dzone] [Facebook] [Furl] [Ma.gnolia] [Newsvine] [Reddit] [Slashdot] [StumbleUpon] [Technorati] [Twitter] [Email] More »

Posted in CMIS, development, xCMIS | No Comments »

Open Source CMIS implementation from eXo Platform released: xCMIS

Tuesday, February 16th, 2010

Last week we announced that eXo Platform has built an open source implementation of OASIS’s Content Management Interoperability Services CMIS specification.  We licensed this under the LGPL license, and released it officially as xCMIS 1.0 beta1.

This release includes CMIS server with all the services implemented according to Content Management Interoperability Services (CMIS) Version 1.0 Committee Draft 06 for REST AtomPub and Web Services (SOAP/WSDL) protocol bindings. The project is hosted on the Google Code forge, check it out on http://code.google.com/p/xcmis/.  I wanted to take a few minutes to answer some of the most common questions from developers about the new xCMIS project.

What is the xCMIS project, and what does it do?

  • xCMIS is an open source, server side Java CMIS implementation that is able to expose the content in existing content repositories according to the protocols defined in the CMIS spec
  • xCMIS will give developers a way to make their content repositories “pluggable” on the server side – thanks to an internal Storage Provider Interface and additional protocol on-demand bindings
  • xCMIS will provide (several) CMIS client frameworks for repository-application and repository-repository interactions. The programming language and supported protocol can be selected by the user.  (For example, the reasonable choice for use with web applications, gadgets, and/or mashups is JavaScript or GWT over REST AtomPub, while for inter-repository exchange it may be Java over Web Services, i.e. WSDL/SOAP.)
  • Both the server and client sides of xCMIS are easily integrated in the eXo Platform 3.0 infrastructure. In particular, xCMIS exposes the eXo JCR content repository and provides a framework for building web applications and gadgets for the GateIn portal

Enough talk already!  How do I download and start to play with xCMIS on my local workstation?

The xCMIS server is packaged as a J2EE Web archive xcmis.war, which you can download and install on any Java servlet container.  Or, you can build it on your own from the source code by following these simple instructions.  Finally, the easiest option might be to use the “download and go” version that we prepared – it’s basically Apache Tomcat bundled with an xCMIS server on /xcmis context path.

By default the xCMIS server includes both REST AtomPub and Web Services (SOAP/WSDL) protocol bindings.

The xCMIS bundle includes one CMIS repository with an empty eXo JCR and JCR WebDAV server inside.  The name of the JCR repository is “repository” :) and the name of JCR workspace is “cmis”. So, it is possible to obtain access to the same content using WebDAV URL
http://localhost:8080/xcmis/rest/jcr/repository/cmis/

If you want to save time, you can download the xCMIS server with a full-featured CMIS GWT UI gadget inside (loaded remotely from xcmis.org site). It can be run the same way as a bare server; then you can go to http://localhost:8080/xcmis/xcmis-demo-gadget/GadgetWrapper.html to check out the CMIS visually.  It should look like this:

The interface is pretty simple and intuitive, and includes a toolbar, right-button context menu, drag-and-drop features, etc.

How do I use xCMIS remotely?

We created the dedicated resource xcmix.org that has xCMIS deployed on the GateIn portal. Here you can find and use the CMIS Expert gadget, and a really cool CMIS Zoho gadget. This one demonstrates multiple CMIS implementations (xCMIS, Alfresco CMIS and Nuxeo CMIS) in action.  You can browse the different CMIS repositories, see the content stored within them, and most importantly – you can view and modify files in Zoho editor.

Feel free to build GateIn yourself and add a local xCMIS server as described in the wiki, or use a remote one (http://xcmis.org/rest/cmisatom – for REST AtomPub protocol).  However, you might want to note that xCMIS beta1 uses eXo JCR 1.12 CR1, so make sure you use an appropriate version of GateIn.  It should be at least as recent as GateIn 3.0 beta 5 (as of the Feb 11, 2010 release, only GateIn built using trunk is suitable!).

And, of course, it is possible to use third-party CMIS clients such as IBM CMIS Firefox Connector, CMIS Spaces Flex+AIR and (I am pretty sure) other clients that are compatible with CMIS 1.0, all in the same way described in the xCMIS wiki (just using a remote server).

What’s next for xCMIS?

  • The CMIS specification is close to the final state, so that means we’re close as well  - once CMIS is officially out, we’ll put out the final xCMIS release shortly after that :)
  • Open the source code for the GWT CMIS framework and move it to xCMIS project
  • Finalize the Storage Provider Interface architecture
  • Refactor the search engine, decoupling it from JCR storage
  • Refactor a CMIS configuration to make it more clear (trying different types of configurations for different IoC containers)
  • Add federated search between several types of CMIS repositories
  • Check out other types of clients
  • And other cool stuff… :)

We’d love to hear your feedback.  If you want to discuss the project, talk about new ideas, make suggestions for improving the documentation, or anything else, please get involved!

To learn more, check out the project Wiki: http://code.google.com/p/xcmis/w/list
To see the source code: http://code.google.com/p/xcmis/source/checkout
To download the binaries: http://code.google.com/p/xcmis/downloads/list
To play with the latest demos: http://xcmis.org/portal/public/classic/CMISExpert

Share this blog post with :
[Bloglines] [BlogMarks] [del.icio.us] [Digg] [dzone] [Facebook] [Furl] [Ma.gnolia] [Newsvine] [Reddit] [Slashdot] [StumbleUpon] [Technorati] [Twitter] [Email] More »

Tags: , , , , ,
Posted in CMIS, GateIn, REST, gadget, jcr, xCMIS | 2 Comments »