Alfresco Share “DocLib” Portlet for Liferay and JSR168 Portal

 

Our company (www.alfstore.com) is about to release a new Portlet for the Alfresco Document Management software (next week).

Our new component will especially be tested and supported with IBM WebSphere Portal (and of course Liferay), and will be JSR286 compliant.
The v1.0 open source version will be delivered next week in the Alfresco forge, and the supported (commercial) release is scheduled end of October.

I will describe our Portlet for IBM WPS soon in a next blog post, but before that I would like to present the “Share Portlet” recently published by the Alfresco team: Alfresco Share Portlets for Liferay and JSR-168 Portal

The “Share DocLib Portlet” is already well documented by Alfresco (see all links at the bottom of this article), so I will only give you the main principles:

Functionnaly the purpose of this “DocLib Portlet” is to expose the Share interface into a Portal.
As per the webinar presentation, it seems that almost all the rich document repository browser capabilities of Share have been “portal enabled” so far.

So the Share Portlet is a good choice if you want to fully expose the Share features and look & feel into a portal page (full window view).

Please note that some Share features are not “portal enabled” for the moment, like blog, wiki, etc. Also, as far as I know there is no search feature exposed.

Technically the Alfresco Share Document Library (and surf webscripts) have been “portletized” and can be deployed as a Portlet (.war file) into the Portal runtime.

The Share Portlet is not based on CMIS, but uses the existing Share webscript, because with CMIS it is still not possible to manage advanced feature like versionning, preview, etc (which are exposed in Share UI and in the Share Portlet).

The “DocLib” Portlet will be available for the following Alfresco version:
– Alfresco server components installable against Alfresco Enterprise 3.3.1 (already available).
– Alfresco Community 3.4.x (I think it will be included only in 3.4.c ?).

Initial Supported Stack:
– It will be supported by Alfresco only for Liferay Portal CE & EE 5.2.3 (Others TBD),
– As per the webinar it is not tested on other Portal (like IBM WebSphere), but it seems to mostly works on Weblogic.

SSO:
The current version use use the standard Liferay ability to pass the portal UserID to Alfresco, and a special authenticator on Alfresco side accepts the credential passed by Liferay.

The webinar demo of the DocLib Portlet was really impressive, and the Alfresco team has done a great work ! Hope you will like it (more info below in the Useful links section).

==============================
Useful links:
Alfresco Share Portlets for Liferay and JSR-168 Portal
http://www.alfresco.com/products/integrations/liferay/

Read wiki documentation
http://wiki.alfresco.com/wiki/Portlets

Watch video, Portlet Installation and Configuration
http://www.youtube.com/watch?v=ypw7oCjUPKo&rel=0&hd=1

Webinar recording:
http://www2.alfresco.com/l/1234/2010-09-21/O1ZM3

New Portlet Development Options for Alfresco!
http://blogs.alfresco.com/wp/luissala/2010/02/24/new-portlet-development-options-for-alfresco/

Advertisements

2 Responses to Alfresco Share “DocLib” Portlet for Liferay and JSR168 Portal

  1. Anonymous says:

    I want to implement this solution with sso enabled.
    Can you please tell me what steps I need to follow?

  2. Enguerrand SPINDLER says:

    Actually, the Portlet provided by Alfresco is already provided with a basic SSO mechanism.
    As far as I understand, the Portlet does send the Portal user credential to a dedicated webscript on the Alfresco side.

    So if you simply follow the Portlet installation guide:
    http://wiki.alfresco.com/wiki/Doclib_Portlet

    …the SSO should work….Of course you will need to share the same login/pw between Liferay and Alfresco.

    Note: the only limitation with this basic SSO mechanism provided by Alfresco is that the login and pw are not encrypted, and by default the login webscript is not protected as well. So what Alfresco recommends is to carefully configure the firewall inside your company to make sure nobody will be able to hack the corresponding webscript.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: