Web Content Management - Delivery options
There are several different ways we can choose to deliver IWWCM content to users, including rendering portlets, a specialized servlet, and pre-rendered sites. There are four different methods available to deliver WCM sites.
Local Rendering Portlet
(Web Content Viewer)Content is delivered via a Local Rendering Portlet located on the same server as a WCM application. Remote Rendering Portlet
(Remote Web Content Viewer)Content is delivered via a Remote Rendering Portlet located on a IBM WebSphere Portal server. A WCM application is not required. WCM servlet Content is delivered as a standard Web Site via the WCM servlet that is installed with the WCM application. Pre-rendered sites Content is delivered as a standard web site via a pre-rendered site.
Basic delivery
WCM content can be delivered:
- Through the WCM servlet.
- Through a local rendering portlet using the local portal server.
- Through a remote rendering portlet located on a separate portal server.
- Through a pre-rendered site using the local Web server.
Syndication
Syndication is used as the transport layer that replicates data from one WCM application to another.
Clustered delivery
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.
- Syndication
- Clustering
- Load balancing
Parent topic:
Configure a delivery server
Parent topic:
Stage Web content to production
