WPS Portal project

Sunday, February 24, 2008

Quickr components definition

This WE, I spent some times to browse and read the Quickr Wiki.
There are a lot of useful information to start understanding this new product. However, it is sometimes difficult to understand the meaning of each technical term, and the role of each component. So I have tried to define in this post, some of the main concepts on which Quickr is built.

What is the Quickr Content Service layer ?

Basically, the Content Service is the interface which exposes features for manipulating content in Lotus Quickr.
The Content Service provides diverse set of clients and programming models (such as REST- or SOAP-based protocols) to manage the Quickr data.
Using this layer, you can launch action to create, manage, update, search, query, and delete Lotus Quickr content, simply by lauching a web service call (with the proper input parameters).

As a result, with a basic Client (like a browser) you can launch an http request (formatted as a REST URL), to trigger an operation in the Quickr Content Repository (ex: WPS Portal JCR 170 Database). For instance, using a simple REST request, you can create a new "folder" in Quickr, or you can delete a document.

An other type of Client can be a Quickr Connector (see definition below). For instance, a Connector installed on the MS Outlook Client can interact with the Content Service layer to publish a mail attachment in Quickr.

What is the difference between the Content Service definition and implementation ?

Lotus Quickr uses a services oriented architecture to access content. Quickr defines a set of open services, that makes it possible to access content remotely for manipulating content in Lotus Quickr.

The Content Service stays on top of a repository (or a back-end) which can be implemented using different kind of technologies (Java, Domino, etc).

Whatever the type of the repository, the Quickr Content Service layer should present a unified user interface.
So the Service definition is the common way to define this interface, and the features that are exposed.
The Service implementation is built on the concrete "back-end side", and corresponds to the core of the features and methods which run within the back-end application and interact with the back-end data model.

Currently, only 2 Services implementation have been provided by IBM: the first is Lotus Quickr Services for Lotus Domino and the other one is for WebSphere Portal.
When using the Websphere Portal implementation, the Quickr repository relies on the WPS JCR 170 Database, and the Quickr API use the java portal runtime to execute.

What is a Quickr Connector ?
A Quickr Connector can be considered as a Client plug-in, which is designed to interact with the Quickr Content Services layer.

For instance, the Microsoft Exchange connector should be installed on the end-user computer, in the Microsoft Outlook Client.

Using this connector, the user will be able to see the list of his/her Quickr Places (directly from the Outlook window), and the user will be able to publish or retrieve mail attachment documents directly in the Quickr repository.

The list of Lotus Quickr Connectors (provided with the Content Integrator tool), at publication time is as follows:

• IBM Lotus Notes/Domino
• Microsoft SharePoint (supports WSS 2003/2007, SPS 2003, and MOSS)
• IBM Lotus Quickr services for Lotus Domino
• Microsoft Exchange
• IBM Lotus QuickPlace
• IBM Lotus Domino.Doc


Post a Comment

<< Home