Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows |
There are several different ways you can choose to deliver IBM® Lotus Web Content Management™ content to users, including rendering portlets, a specialized servlet, and pre-rendered sites.
There are four different methods available to deliver Web Content Management sites.Local Rendering Portlet (Web Content Viewer) | Web Content Management content can be delivered via a Local Rendering Portlet located on the same server as a Web Content Management application. See Displaying content in a rendering portlet for further information. |
Remote Rendering Portlet (Remote Web Content Viewer) | Web Content Management content can be delivered via a Remote Rendering Portlet located on a IBM WebSphere® Portal Express server. A Web Content Management application is not required. See Displaying content in a rendering portlet for further information. |
Web Content Management servlet | Web Content Management content can be delivered as a standard Web Site via the Web Content Management servlet that is installed with the Web Content Management application. See Accessing Web content via a servlet for further information. |
Pre-rendered sites | Web Content Management content can also be delivered as a standard web site via a pre-rendered site. See Installing a pre-rendered delivery server for further information. |
Syndication is used as the transport layer that replicates data from one Web Content Management application to another. Further information can be found in the Syndication chapter later in this guide.
A set of delivery applications can be installed as a cluster. This provides in-built redundancy. A load-balancer can be used in-front of a clustered set of delivery applications. Syndication is enabled between the staging application and all delivery applications.
Staging applications can Syndicate to more than one cluster of delivery applications allowing separate delivery clusters to be installed at different locations.
Note: