Tuesday, December 16, 2008

JBOSS Portal vs Liferay Portal

Feature Comparison

Feature Liferay(5.1+) JBoss Portal(2.7)
Out of the box Tools Has rich set of out of the box portlets Not too much out of the box portlets
Single Click configuration (altering a page layout, adding new applications and content, and changing look and feel can all be done in a couple of clicks) Supported Supported
Dynamic Drag and Drop(move different elements around in the portal by) Supported Supported
SSO Supported Supported
Role Based Authorization support Supported Supported
Communities and Organizations Liferay users can be intuitively grouped into a hierarchy of "organizations" or cross-organizational "communities," providing flexibility and ease of administration. Not Supported
Personal User Pages All users get a personal space that can be made public (published as a website with a unique friendly URL) or kept private. You can customize how the space looks, what tools and applications are included Not provided
Internationalization support Out of the box internationalization support provided for 22 languages. No out of the box internationalization support available
Wikis Provides robust wiki support Provided
Activity tracking Display most recent activity Not provided
Message Boards Supported (Can be very easily created) Supported
Instant Message Support A friends list automatically displays the names of all other logged-in portal users. If you have something to say, just IM them. Not provided
Alerts and Announcements Broadcast messages to different group of users whether they are simple announcements or "newsletter"-like in purpose Not provided
Blog Support Provided Not Provided
Calendar Rich calendar support(Can add events) Support
Password Policies Liferay provides flexible password policy through Enterprise Admin Portlet. you can apply different rule sets to different sets of portal users. Not Provided

Similarities

•Both are JSR-168 compliant.
•Both are open source.

Differences
•JBoss Portal can only be installed on Jboss application server whereas Liferay works in any J2EE container or servlet container.
•Liferay has been around longer than JBoss Portal.
•The CMS features are very minimal in JBoss Portal because all that one can do is create html pages using a rich text editor and do some file manipulation activities (create directory, move and copy files and so on.
•The CMS portlet in Liferay is more feature rich than that of JBoss in the sense that one can create custom content types and own templates. This helps separate content form its presentation. It is also very easy to create new pages and add them automatically to the navigation bar.
•Liferay has a larger portal community.
•Liferay has more enterprise clients that have run the portal for many years with hundreds of thousands of users.
•Liferay comes with many useful portlets so you don't have to configure much. But, it also has many external portlets and themes available. JBoss has fewer portlets.
•Though Liferay works with almost any application server, I have found users complaining about setup with any other AS take longer time. Whereas setting up JBoss Portal is a straightforward, three-step process of editing some configuration files, creating the database, and starting the portal. Reference
•Also people felt Liferay portal to be bit slow but stable.
•Liferay is under the MIT (similar to Apache/BSD) style license. JBoss is LGPL.

References
Liferay Vs JBoss
Portal Polls Survey
JBoss to Liferay Migration Reason
Liferay User Experience Customization
Liferay Technical Spec

Glossary:
•Out of the box: A ready-made software, hardware, or combination package that meets a need that would otherwise require a special development effort.

3 Java Junction comments:

Thomas Heute said...

You compare a portal framework (JBoss Portal) with a portal solution (Liferay).
Plus your facts are wrong. JBoss Portal product doesn't provide a forum nor a calendar. (Even though you can find Forums or Wiki portlet on jboss.org).

Also you'll have to argument: "Liferay has more enterprise clients that have run the portal for many years with hundreds of thousands of users.". Unless you work for sales at Red Hat you can't know JBoss Portal customers (same for Liferay).

So here you are taking Liferay's applications and see if they are in JBoss Portal. Another approach would be to see JBoss Portal framework feature and compare to Liferay (such as scalability, architecture, API, customization)

JBoss Portal focus on the *framework* to let our customers build *their* portal to fit 100% if their requirements in a robust manner and that scales. Liferay focus on *applications* to help build a portal.

I just wanted to put your blog in the context, because here it doesn't do justice to JBoss Portal

Sandy said...

Thanks for providing feedback. Actually these are the comparisons we gathered from most of the available blog comparisons about the two. And we had to select a suitable and easy development platform to develop portlets. Sorry it hurt you.

Rose said...

really very nice information sharing and i am looking for such type of informative news and i get through this blog so i am very much thankful to you.
- liferay customization