Difference between revisions of "Summer of Code 2013/CMIS UCP"

Revision as of 14:16, 5 June 2013

• Student: Rajath S.
• Mentor: Juergen Schmidt (jsc)

Project Description

Before I describe my project plan I would like to write a bit about CMIS and UCP:

CMIS is an acronym for Content Management Interoperability Services. CMIS establishes a standard for all the Enterprise Content Management systems just like what SQL did for the relational databases. CMIS is an abstract layer used for controlling various web repositories and document management systems. Advantages of CMIS is that it is platform independent and available for a wide-range of programming languages. (For more information, links have been provided in the references section). OpenCMIS/Apache CheMISitry is a collection of libraries/tools/frameworks for CMIS client and server development. It is available as Java, Python , PHP , .NET , Objective-C libraries/modules.

UCP is Universal Content Provider. Apache OpenOffice connects to various data sources using Universal Content Broker(UCB) which has a core module and a set of UCP’s for each source. UCB provides generalized access to data sources and a set of functions for querying, modifying, creating, access to folder tree, meta content of documents, permissions,etc. The advantage of UCB is that it provides a common perspective for developer irrespective of the data source. UCPs mask the difference between access protocols for various sources by providing interfaces for access to that particular data source. Currently, UCPs exist for FILE(file-system), WebDAV-HTTP(web-based file-systems and HTTP), FTP(file transfer protocol), Hierarchy(Virtual file hierarchy), ZIP/JAR, Help files(OpenOffice Help files) and Extension Package Content(access to openoffice extensions).

Now, my project is to create a UCP for access to CMIS compliant repositories. Various functionalities include: access to folder tree, changing document properties, version control, creation/deletion documents, setting access permissions, moving files, etc. A sidebar will also be created which will provide access to all these features.

My work can be broken down into these components:

1. Familiarising myself with APIs This includes both OpenCMIS and OpenOffice API. -- JAVA

2. Designing the UI for sidebar

3. Module: Authentication to repositories using a standard authorization protocol. (One that already exists in OpenOffice API).

4. Module: Browser for file hierarchy of the repository. --viewing the folder tree, copying, moving, deleting files.

5. Module: File Properties Editor. -- Changing Permissions, meta data, etc.

6. Module: Version Control.

7. Changes in OpenOffice: Save/Saveas in repository. Recent files accessed from CMIS in recent documents list,etc.

8. UCP: Using all the modules built to create a UCP for CMIS. Integrating the UCP with the UCB.

References:

1. http://wiki.openoffice.org/wiki/Documentation/DevGuide/UCB/

2. http://chemistry.apache.org/project/cmis.html

3. http://www.oldschooltechie.com/blog/2009/11/23/introduction-cmis

4. CMIS and Apache Chemistry in action - Book.

5. http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services

Programming language: Java. Platform: Linux - Ubuntu 12.10

Project Plan

My project plan is marked by milestones. Each milestone is alloted a particular time for completion. But, the time taken to achieve a milestone may vary slightly due to unexpected situations or difficulties faced.

Milestones:

1. Setup Apache OpenOffice Java SDK. Also, setup OpenOffice build environment.

 Status: DONE

1. Get acquainted with OpenCMIS Java Client Libraries. Setting up the development environment. Also, to setup a local inmemory chemistry server for testing. Code an own client to upload and retrieve a .odt document. Then, manually open the .odt from the OpenOffice.

 Status: DONE

1. Code to be able to browse the contents of a repository through the internal file open dialog box.

 Status: In Progress

1. To be able to open and save files.

 Status:

1. Creating, deleting, copying and moving content.

 Status:

1. To develop an options page to configure the repository connection. Also manage the user and several repositories. To use the internal password container.

 Status: 

1. Support for https connection. Using internal certificate store and use the interaction handler.

 Status:  

Setting up OpenCMIS JAVA Client Libraries

Platform: Linux - Ubuntu 12.10

Setup involves:

1. Java Client Libraries
2. Testing Components:

   # OpenCMIS workbench
   # OpenCMIS In-memory repository

Steps involved:

1. Download OpenCMIS JAVA Client Libraries with Dependencies from [1]. Extract it to a folder. The .jar files inside this folder are the libraries which can be imported into a project in your IDE.
2. To Setup Workbench:

   # Download OpenCMIS Workbench from [1]. Extract it to a folder.
   # "cd" to that folder and give permission to the shell script by "chmod +x ./workbench.sh".
   # Run "./workbench.sh" to start the workbench.

1. To Setup In-memory Repository:

   # Download OpenCMIS Server Webapps from [1]. Extract it to obtain chemistry-opencmis-server-inmemory-<version>.war
   # Any servlet deployer can be used to deploy the .war file. I chose Eclipse Jetty. Alternatively, Apache Tomcat can be used. Download Eclipse Jetty from [2]. Extract it.
   # Copy the .war file to <jetty-installation-folder>/webapps folder. Rename the .war file to "inmemory.war" to obtain shorter URL. In the same folder create inmemory.xml configuration file with the following lines:
   <Configure class="org.eclipse.jetty.webapp.WebAppContext">
       <Set name="contextPath">/inmemory</Set>
       <Set name="war"><jetty-installation-path>/webapps/inmemory.war</Set> 
   </Configure>
   # Run "java -jar start.jar" in <jetty-installation-folder> to start the inmemory repository.

Links: [1]. http://chemistry.apache.org/java/download [2]. http://download.eclipse.org/jetty/stable-9/dist/