Pre-rendered delivery
We can pre-render a complete Web Content Manager site into HTML and save it to disk. The pre-rendered site can then be used as your live site and displayed to end users using either Web Content Manager or a web server. You deploy a pre-rendered site when we are not using any WebSphere Portal features and your content is static and is only updated periodically.
- Restrictions
- Site areas and content item names cannot contain characters that are considered invalid in file names by the operating system on which we are pre-rendering. For example, on a machine running Windows, these characters are invalid: / \ : * ? " < > |.
- The path to the content item, including the directory path to which we are pre-rendering (for example, site area/content) cannot exceed the operating system's maximum path length:
- 255 characters in Windows
- 1024 characters in Linux
The Search component cannot be used in pre-rendered sites.
The Page navigation component cannot be used in pre-rendered sites.
Personalization elements can only be pre-rendered if the personalization rule is configured for anonymous access.
- Site security
- Item security for different users set in an Web Content Manager environment is not transferred to pre-rendered sites. The security for the entire pre-rendered site is based on the connect.moduleconfig.cacher.rendereruser property as specified in the WCM WCMConfigService service.
- Pre-rendering a website
Pre-rendering can be configured to run automatically, or we can manually pre-render a website using a URL.
- Access the pre-rendered site
Pre-rendered sites are accessed either through Web Content Manager, or through a web server.
Parent: Deliver web contentRelated:
Related: