We’ve seen a lot of interest in Adobe CQ5 lately. One question that comes up a lot is about CQ5’s portal capabilities. Michael Porter blogged last year about the trend of Web Content Management systems to become more portal-like (see Web Content Management’s Trend Towards Portals).
It is true that overall CQ5 has lots of traditional portal features. However, unlike many other WCM systems, CQ5 has gone the extra step to include a portal server within its stack so you can run real portlets in the system. So CQ5 can play dual roles of traditional content management and portal, just like traditional portal vendors IBM, Liferay, and SharePoint.
So the question is: can CQ5 offer the same level of portal capabilities as these other vendors? From a pure portal point of view, I don’t think CQ5 is quite at the level of the major portal vendors. I refer to CQ5 as more portal-lite because it does offer the ability to run standard portlets, but it lacks many of the features that the other systems provide. Here is a small list of additional services that IBM’s portal offers that are not in CQ5:
- Credential Vault – when integrating with external sites, you sometimes need to store each user’s ID and password to pass along. IBM provides a very secure implementation of a credential vault out of the box.
- Personalization engine access from within a portlet. CQ5 offers personalization of content, but what if you have a custom portlet that needs to pull in personalized content. IBM offers this service so portlets can define a content spot on the output of a portlet and that spot runs the rules engine to get personalized content.
- JSF or Struts frameworks. Both frameworks are included in the IBM tooling for Portlets and are available in the server runtimes. For CQ5 you will have to implement these frameworks yourself.
- Interportlet communications. CQ5 runs JSR 286 portlets which now offer the ability to communicate with each other through portlet events. But if you have older JSR 168 portlets that can’t do events, you have to come up with your own portlet communication system. IBM has provided a strong portlet wiring service for a long time.
- Virtual portals in the IBM Portal provide the ability to distribute administration of portals without having to purchase separate hardware and software. This feature allows for addressing multiple user directories when you want to keep your suppliers separate from your customers.
If you don’t plan to use these extra features, then Adobe’s CQ5 product may fit your portal needs just fine. If these features are important, then you need to evaluate whether CQ5 should be your sole portal platform.
We often see the scenario where you have a content-heavy site for your public web presence, but you have an application-heavy secure site for customer self service. In this case, its perfectly feasible to combine CQ5 for its great content management and digital marketing platform with a more traditional portal platform for the heavy application lifting.
For this scenario, content is managed in CQ5 for both marketing and secure sites. Your application-heavy portal, say IBM Portal, can use the out of the box CQ5 content portlet to deliver content to the secure site.
Don’t get me wrong, I like what Adobe CQ5 offers from a WCM and Portal perspective. Many of our clients love it. But as we see so many vendors trying to blur the lines between the technologies to offer a complete solution, I just see that the evolution is still under way.
