Home

News: Opinion: Choosing an open source portal server

  1. There is a lot of interest in the Portlet specification, and many people are in the position of choosing a portal server. There are quite a few open source solutions, and more that use open source and add some value on top. Punit Pandey asks the question, and some people have responded. What are your thoughts?

    Read: Which Open Source Portal Server to Choose?

    Which Portal? Apache Jetspeed, of course!

    It will be interesting to see how the portal space grows as more and more JSR 168 portlets are created

    Threaded Messages (34)

  2. portlets community?[ Go to top ]

    as author pointed, "the portlet and portal technology is now here for quite a while". there are many free and commercial implementations of portlet container.
    surprisingly, there is still no open-source portlets base, even for typical use cases (mail readers, forums, cms, etc...). commercial support for portlet specification (from portlet vendors point of view) is lacking, too.

    it seems that the portal/portlet technology has it's hard time starting...
  3. portlets community?[ Go to top ]

    There has been an attempt: http://sourceforge.net/projects/portlet-opensrc. However, there are no updates for over 6 months now.
  4. How can you say that, the portal community is hudge, you have blogs, many projects about portal and portlets.

    In our future RC 1 release, you can already have a look to what the code in CVS is at www.exoplatform.com we provide a large list of portlets including :
        - enhanced wiki (an integration with the xWiki project has been done),
        - forum,
        - SMS portlet (to send SMS through a gateaway)
        - mail,
        - CMS (to view a JCR repository - JSR 170 - and modify content from it),
        - workflow,
        - i18n portlet (properties file online edition)
        - Log portlet
        - and many more...

    Liferay has also an impressive list of portlets...

    So I totally disagree with you, this market is just starting and according to all the feedbacks we get : it is BIG!
  5. it's great there are many portlets in exo or liferay. however, i'm not sure if they are generic enough (don't rely on vendor-specific services) to be run on any portal container... and that's what i meant when i started topic on portlet providers shortage.
  6. portlets community?[ Go to top ]

    eXo's SOA stack is real cool.
    I also found that eXo has an eXo-JSF framework to integrate JSF into their portal implementation. That's good news.

    I would, however, like to see JetSpeed(2) really speed up and catch-up with the rest of them.


    Murali K
    http://www.findonnet.com
  7. portlets-jsf[ Go to top ]

    eXo's SOA stack is real cool.I also found that eXo has an eXo-JSF framework to integrate JSF into their portal implementation. That's good news. </a>
    From recently (latest weekly build of jsf-ri), portlet-jsf integration is also available from sun.
  8. portlets-jsf[ Go to top ]

    eXo's SOA stack is real cool.I also found that eXo has an eXo-JSF framework to integrate JSF into their portal implementation. That's good news. </a>
    From recently (latest weekly build of jsf-ri), portlet-jsf integration is also available from sun.
    Does Sun release the src with that version. I go there few days ago and only src for version 1.0 is avaliable. I will look into it soon to make sure exo-jfs framework is compatible with with sun portlet-jsf

    Tuan Nguyen
    www.exoplatform.com
  9. portlets-jsf[ Go to top ]

    Does Sun release the src with that version. I go there few days ago and only src for version 1.0 is avaliable.
    As of Monday's announcement at JavaOne, the source code for the reference implementation of JavaServer Faces is available, under the Java Resource License, at java.net:

    http://javaserverfaces.dev.java.net/

    The weekly build source bundle includes the Portlet API (JSR-168) integration library needed to use the JSF RI in a portlet environment.

    Craig McClanahan
  10. How is the open source CMS portlet market ?
    I didn't see something very mature in product like Exo, liferay,...

    Eg. Exo announces a JSR170 support but I don't see something in the code source.
    Same for Liferay, there is just a document browser portlet - That's all. No content workflow, notification, portlet editor, ...

    Compare to other plateform like Zope/plone, it is really unmature.
  11. CMS portlet community[ Go to top ]

    How is the open source CMS portlet market ?I didn't see something very mature in product like Exo, liferay,... Eg. Exo announces a JSR170 support but I don't see something in the code source.Same for Liferay, there is just a document browser portlet - That's all. No content workflow, notification, portlet editor, ... Compare to other plateform like Zope/plone, it is really unmature.
    We does implement JSR 170 , you can find the source code at http://cvs.sourceforge.net/viewcvs.py/exo/exoplatform/exo-services/jcr-service/. Hope we can include a demo by the time we release RC1 version and we will focus more on jsr 170 after the release.
  12. portlets community?[ Go to top ]

    The open-source portlets base is starting.. There was a need for good containers in order to write applications. XWiki is portlet compatible (tested with eXo). So you have a full features wiki integrating with a portal server using the portlet API.

    Concerning which portlet container to use, I like eXo because of it's SOA service stack. It was very easy to bridge the wiki authentication to the authentication service of eXo. It is even possible to allow access to eXo services using an API in the wiki pages. And this is a key need for portlets. The portlet API is not necessatly enough to integrate an application in a portal server.
  13. services community?[ Go to top ]

    It seems harder to sell exo or Jetspeed as a solution to an enterprise because of the underlying service implementations rather than the presentation implementations. I think JSR-168 and WSRP will catch on as presentation tier technologies just like Struts caught on. Struts was nicely decoupled from underlying tiers so the SLA could be tied to the servlet engine running it. This is not the case with portal frameworks which to some extent tightly couple home-grown services such as content management and personalization. Your mission-critical SLA depends the integrated framework. No one seems to question Struts with and Oracle back-end. Jetspeed or exo out-of-the-box integration with an enterprise quality CMS would go a long way to beef-up the backend.

    exo seems to be headed in the right direction as a service based approach. These definitely need to be plugable.
  14. after :

    - using jetspeed 1,
    - waiting for the jsr 168
    - trying to use pluto
    - compiling jetspeed 2
    - using liferay

    we choose eXo Platform for our web site RS2i.

    Everything in the page is portlet : navigation portlets (horizontal menu, vertical menu, breadcrumbs), content portlet.

    Also the business model are really interesting, so, we decide to use an OEM version of eXo for our customers.
  15. Punit had several requirements with the most important being :

        *Support of JSR 168 and WSRP standard

    In his answer , Jeff simply forget that parameter which is IMO the most important.
  16. Punit had several requirements with the most important being : *Support of JSR 168 and WSRP standardIn his answer , Jeff simply forget that parameter which is IMO the most important.
    Benjamin, I very much appreciate your response both here and on my site. Having just returned from vacation I was happily surprised to see so much response from my blog, and doubly surprised to see coverage on theserverside.com. I will post a follow-up on my blog shortly.

    To answer your one statement here... I should have mentioned more clearly from the beginning of my commentary that my results were purely based on my own requirements. I briefly mentioned at the end that:
    I should do another entry on JSR 168 and why that is not important to us, yet. Jetspeed essentially shelters us from the current hype.
    And I still intend to do this. In a nutshell, Jetspeed allows us to write actions and jsp's using their built-in MVC Portlet and thus not have to write portlets of our own (thus making JSR 168 negligible). Using Jetspeed as an "Application Portal" and not as an "Enterprise Portal" allows leverage for us that others are unable to achieve.
  17. Market trends[ Go to top ]

    <quote>It will be interesting to see how the portal space grows as more and more JSR 168 portlets are created </quote>

    As J2EE is now becoming a commodity, Portal Server is (or will soon) also becomes a commodity. Portal Vendors are then no more offering a portal architecture only but a full web application platform suite (according to the Gartner wording ;-)) which includes CMS, Business Processing Server, Search, Integrated Collaborative components (IM; Forums; WebMail;...), Doc Management...

    Of course there is now the opportunity for new incoming software vendors to leverage the new JSR 168 standard in order to develop generic and portable portlets (which was quite complex before as you had to modify your suite of portlets for each portal vendors - cf: http://www.compoze.com) and to become "portlet providers". Certainly smaller vendors such as Atlassian or Jive Software will also soon integrate JSR 168 compliant views on top of their respective web applications.

    Cheers
    Stéphane
    - http://www.jahia.org -
  18. No need for 168[ Go to top ]

    I did a large site (10 mm users for ZD) with CMS and "Portal" using Struts Tiles, ex:
    http://www.basicportal.com/bp/download/cms.PNG

    No problems if you just tone down technology just a notch and focus on the solution.

    .V
  19. No need for 168[ Go to top ]

    You can always work without standards. But it is nice to have standards, to make your work reusable for future. I don't think there is any need to tell importance of API standardization. We have lost much of our development efforts due to lack of portlet API standardization. Now we are strictly following JSR 168 in order to avoid problems in future. Due to above experience, JSR 168 was one of the primary criteria for my portal server selection.

    Punit Pandey
  20. Easier to follow the standard[ Go to top ]

    The JSR 168 portlet API is not that difficult to learn, especially if you already know servlets. I agree with Punit, if you are starting a portal development project, pick a portal (open source or commercial) that supports JSR 168. If you stick to the standard, you can migrate to another compatible portal later.

    Jeff Linwood
    co-author, Building Portlets with the Java Portlet API (coming out in August)
  21. +1 Liferay

    some problems with the localization, but overall is a very good product

    Dmitry Namiot
    Coldbeans
  22. liferay[ Go to top ]

    My first experience with a portal server was with liferay. I used it to create a website with an extranet, and a "logged in" area. I created a portlet to allow logged in users to accept a software license and download stuff. I looked at jetspeed and Jboss' nukes. Nukes was by far the worst. I recall that you couldn't even change the banner without writing code. That was 3 months ago or so. Anyway, for my very low volume site, liferay has been running quite nicely on JBoss with HSQLDB. I installed Apache James mailserver in order to get the "mail me my password" functionality up and running.

    -geoff
  23. My 2 cents:

    Check out http://www.lglifeisgood.com

    It's a beautiful portal site running on top of Liferay. It has thousands of college users a day posting pictures that the community can vote on. Winners get TVs, phones, trips, etc. The site shows the scalability and extensibility of Liferay.

    Another good site is http://www.educa.madrid.org/portal/

    The Madrid, Spain school system built a portal for its 1600 schools with 500,000 users all on top of Liferay. The guys who extended Liferay added lots of community portlets (chatrooms, extended the calendar, etc) to provide the best user experience.

    Liferay also has a very business friendly MIT license (very similar to Apache and BSD). You can resell it without ever paying Liferay. But if your business needs support, you can buy that too from Liferay.

    Liferay already has a large bundled set of portlets that have been in production use for over 2 years now: Mail, Calendar, Document Library, Wiki, etc.

    Liferay is JSR-168 compatible. WSRP support is in the works. Liferay supports WebLogic, WebSphere, JoNAS, JBoss, Orion, Oracle9i, and Sun app servers.

    It's db agnostic. Use MySQL, Oracle, PostgreSQL, DB2, MS SQL, or whatever else you like.

    You can check out a demo by going to http://demo.liferay.net.

    Have fun, and I hope Liferay can be of service to you.

    You can customize the portal:

    http://www.liferay.com/documentation/development_customizing.jsp

    or hot deploy your own portlets:

    http://www.liferay.com/documentation/development_hot_deploy.jsp

    Brian Chan
    Chief Software Architect
    Liferay, LLC "professional open souce solutions"
  24. Liferay - Experience[ Go to top ]

    We have deployed Liferay as the internal portal system for our 5000+ employee restaurant chain.

    We're mainly using the calendar, email, message boards, and document library portlets (all of which are role-based) to great effect. Its been fast and stable even on relatively basic hardware. The deployment was very straight forward and the product continues to improve. Liferay made our small IT staff of 3 people look like heroes.

    Summary: Definitely check out Liferay before you settle on an FOSS JSR 168 Portal solution.
  25. Websphere support for Liferay[ Go to top ]

    Brian - we have tried to deploy Liferay on Websphere 5.1 without success (around 6 months ago). Sounds like it has been resolved from your post, please can you point us to some info on how to do this (it is not available on the Liferay site). <BR>Thanks!
    <BR>James Tsao
  26. WebSphere with Liferay[ Go to top ]

    yes, the second largest savings bank in Germany is now using Liferay.

    Check it out here: http://www.computerwoche.de/index.cfm?pageid=254&type=detail&artid=61477

    They were able to save in the six digit range by going with Liferay.

    they've sent me a bunch of the xml descriptors. we had to modify some library structure plus JAAS stuff which is in the latest CVS. We'll have the docs up and ready asap so you can try it out.
  27. WebSphere with Liferay[ Go to top ]

    Excellent.

    Brian, when you get a chance could you add these links to the Liferay website? And any others than you can (allowed to)?

    Thanks.
  28. Strating[ Go to top ]

    Hello, I'm interested in the Liferay portal to be used as a small comunity site where the members can put their experiences including (pictures, blog, maybe videos from youtube and so on) for this i'm thinking about getting the site hosted and I have couple questions: 1. which version do I download? I dont get the difference between Geronimo, Tomcat, and glassfish? 2. what kind of hosting? (Linux, windows, space needed? 3. do I need to consider other parameters? Thanks again for taking time to read this.
  29. Liferay company background[ Go to top ]

    Does anyone know anything more about the company background of Liferay than is stated on their Web site? Now, the "Company" link just provides a list of its contributors. In the past (at least a year ago, if not more), it talked about its mission in very evangelically spiritual terms.

    I just want to avoid any conflict of interest that may arise from the use of a product whose company has a specific agenda beyond the standard one of growth and profits. ;-)

    Thanks,
    Mike
  30. Tipically self likeing answer[ Go to top ]

    Wow, so this is what author says about it's own product. Really unbiased oppinion. Is the sales polite and support efficient as one might expect from this description ? I don't believe so.
  31. JSR 168 support?[ Go to top ]

    I was unable to get any of the reference jsr 168 portlets from Sun's site to run under Liferay. So I'm looking at Gridsphere now, but it doesn't run correctly under JBoss, so you have to be happy with Tomcat only deployment. It's hard enough to get these projects converted into a format which allows hot class replace/debug from Eclipse. I think the portal builders need to create projects which are geared for easy development and jsr 168 portlet integration. Saying you have 168 support and having it actually work seem to be elusive...
  32. I have posted an update to my first entry:
    http://uncommentedbytes.blogspot.com/2004/07/open-source-portals-and-apache.html
  33. I18N certified portlet server[ Go to top ]

    I would like to know which all portal servers are I18N Certified.

    I'd be specifically interested in LifeRay Enterprise and Weblogic portal server

    Thanks
  34. Has anybody compared IBM's Websphere Portal product against the open source alternatives? Apache Jetspeed 2 http://portals.apache.org/jetspeed-2/ Apache Pluto http://portals.apache.org/pluto/ Websphere Portal Server http://www-306.ibm.com/software/genservers/portal/server/index.html JBoss Portal http://www.jboss.org/products/jbossportal eXo Portal http://www.exoplatform.org/ Sun Portal Server http://www.sun.com/software/products/portal_srvr/index.xml BEA Weblogic Portal http://edocs.bea.com/wlp/docs81/overview/overview_wlp.html Oracle Portal http://www.oracle.com/technology/products/ias/portal/index.html Portal Server https://portal.dev.java.net/ Liferay Portal http://www.liferay.com/
  35. Portal resources[ Go to top ]

    I compiled a list of links in the Javapedia: http://wiki.java.net/bin/view/Javapedia/Portlet http://wiki.java.net/bin/view/Javapedia/Portal