Pre-rendered sites

 

+

Search Tips   |   Advanced Search

 

We can pre-render a complete IWWCM site into HTML and save it to disk. The pre-rendered site can then be used as the live site and displayed to end users using either Web Content Management or a Web server.

Site security

Item security for read access for different users set in a Web Content Management 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 set in the pre-rendering configuration of the WCMConfigService.properties file.

Restrictions

• 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 path to the content item, including the directory path to which you are pre-rendering (for example, site/site area/content) cannot exceed the operating system's maximum path length:
  • 255 characters in Windows
  • 1024 characters in Linux

• The pre-rendering feature cannot be used to pre-render JSP components.

• Configure pre-rendering
  We can enable pre-rendering so that content can be viewed either through a IWWCM application or as a standalone site that is accessed through a Web server.

• Pre-render a site
  The CacherModule is used to pre-render a site. It can be configured to run automatically or manually.

• Access the pre-rendered site
  Pre-rendered sites are accessed either through IWWCM , or through a Web server.

 

Parent Topic

Configure a delivery server

 

Related concepts

Cache versus pre-rendering

 

---