Delivery Options

 

+
Search Tips   |   Advanced Search

 

There are four different methods available to deliver Web Content Management sites:

Local Rendering Portlet	Content delivered via a Web Content Viewer located on the same server as a WCM application.
Remote Rendering Portlet	Content delivered via a Remote Web Content Viewer located on a WebSphere Portal server. A WCM application is not required.
WCM servlet	Content delivered as a standard Web Site via the WCM servlet that is installed with the WCM application.
Pre-rendered Sites	Content delivered as a standard Web Site via a Pre-Rendered site.

 

Basic Delivery

Staging	The Staging application syndicates to a Delivery application. The Delivery application subscribes from the Staging application.	Delivery	WCM content can be delivered: via the WCM servlet. via a Local Rendering Portlet (Web Content Viewer) using the local WebSphere Portal server. via a Pre-rendered Site using the local WebSphere HTTP server.
		WebSphere Portal	WCM content can also be displayed in a Remote Rendering Portlet (Remote Web Content Viewer) located on a separate WebSphere Portal 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	The Staging application syndicates to all Delivery applications. All Delivery applications subscribe from the Staging application.	Delivery Cluster	A load balancer is used to spread the load between the Delivery applications in your cluster.	Internet / Intranet

Staging applications can Syndicate to more than one cluster of Delivery applications allowing separate Delivery clusters to be installed at different locations.

Staging	The Staging application syndicates to all Delivery applications in Cluster 1. All Delivery applications in Cluster 1 subscribe from the Staging application.	Delivery Cluster 1
	The Staging application syndicates to all Delivery applications in Cluster 2. All Delivery applications in Cluster 2 subscribe from the Staging application.	Delivery Cluster 2

 

Clustering

Refer to the Cluster Installation Process topic for information on installing Web Content Management in a clustered environment. Also refer to the WebSphere Portal Information Center.

 

Load Balancing

Refer to the documentation of your Load Balancer for information on how to enable load balancing.

 

The Web Content Authoring and Clustered Environments

A WCM application cannot be used as an "authoring application" in a clustered environment. It can only be used as a staging or delivery application. This means that although the Web Content Authoring is installed on WCM staging and delivery applications in a clustered environment, you cannot use the Web Content Authoring to author content. On staging and delivery applications, the Web Content Authoring is only used to manage syndication and caching.

 

Distributed Session Persistence

The WCM Authoring portlet and Local Rendering Portlet cannot be used in a clustered environment that has distributed session persistence enabled. To display WCM content in WebSphere Portal pages in a clustered environment that has distributed session persistence enabled use a Remote Rendering Portlet pointing to a WCM application located outside the clustered environment.

Question: Is this memory to memory or database persistence?

Parent topic: Architectures.

Parent topic: Content Delivery Guide.

---

IBM Workplace Web Content Management - V5.1.0.1 -

 

Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.