TIMETOWEB CMS and WebSphere Portal - a perfect duo

With a portal organizations can create web based, centralized contact points for employees, business partners and clients. A portal offers added value in comparison to a standard web presence. The benefit on the user side is compromised by the operating expense to fill the portal with content and applications. With the new developed "WebAppPortalizer"-Portlets content published via TIMETOWEB CMS and established collaborative applications can be integrated fast and cost effective.

The integration of existing web applications into a portal is a nontrivial issue. Apart from making sure that clicks on links within a website doesn't leave the portal, more extensive tasks such as maintaining interactive functions of a website are necessary. TIMETOACT has developed a framework and style guide for such a integration scenario. Among other things the TIMETOWEB CMS has been integrated into the portal and is already effectively used by our clients. TIMETOACT's conference session discussion the "integration of legacy web applications in portals" at this years WebSphere Community Conference was followed with great interest.


For the integration TIMETOACT provides two "WebAppPortalizer" portlets: a content portlet for the content area and a navigation portlet, which can be configured to display the top and/or left navigation. Additional configuration can be used to build a combined CMS and portal navigation. So, a portal user can easily provided with rich content from the TIMETOWEB based CMS.
 TIMETOWEB CMS and WebSphere Portal


The provided portlets have a caching mechanism, that supports local as well as a "distributive" caching (over several cluster server). Advanced configuration can be done to outsource the cache content to a database.

Correct links

If the HTML content has to be accessed via a proxy server, the "WebAppPortalizer" portlets can be configured accordingly. The portlets also differentiate if links within HTML-content are URLs or source links for e.g. pictures or other resources. For the latter, organizations typically deploy a so called reverse proxy server as an additional security filter. The "WebAppPortalizer" portlets store the according links with the correct URL in order to support this reverse proxy functionality. All configuration can be made via the web interface in so called configuration mode of the portlets.

For the often complex handling of JavaScript in such a integration scenario, TIMETOACT has developed a style guide. When complying with the style guide, all JavaScript queries will proceed within a portal without any problems. e.g. for complex user interaction and plausibility.


  • Several interaction navigations and content portlets
  • Caching of content is possible
  • Portal-navigation controlled by the CMS
  • Seamless integration of the portal and CMS navigation
  • Even interactive functions (submit etc.) work
  • Java script is proceed accordingly