Pre Rendering WCM site

Pre Rendering WCM sites in your portal environment will improve performance drastically.
Recently I just did pre rendering of WCM content for our portal environment and performance improved a lot.

I will briefly talk about Concepts, Limitations/Restrictions.
For further information and detailed configuration, I would strongly recommend to go through the info center and perform configuration as per your business needs.

Pre rendering allows you to cache your wcm content as static html files and save it to disk.
The pre rendered sites or static html can then be moved to web server and delivered to end users from web server.
It generates a static Web site as a set of HTML pages. Users requesting a page will get the pre-generated HTML page rather than a dynamic page from the Web Content Management connect servlet.
Web Content Management Caching, Servlet Caching (DynaCache), and pre-rendering are used to improve the performance of Workplace Web Content Management Web sites.
Although pre-rendering is the fastest option, its various limitations mean that most users will choose Web Content Management Caching or Servlet Caching over pre-rendering.


Sites, site areas, and content items cannot contain characters that are considered invalid in file names by the operating system on which you are pre-rendering. For example, on a machine running Windows, these characters are invalid: / \ : * ? " < > |.

The pre-rendering feature cannot be used to pre-render JSP components and few more....

Here are the info center article for the same,


Brian said...

Hi. This looks like a great feature in websphere. Do you know if any other WCM (pref. free and opensource, like Liferay) has this feature too?

Neeraj Sidhaye said...

Hi Brian,
I am sorry but I didn't come across about this feature with any open source, but I believe there should exist some other mechanism. I will share as soon as I find anything for open source portals.