Delivery architecture
Your technical architect and information architect need to define what delivery methods are most appropriate for the website we are delivering.
The delivery architecture describes which delivery methods are required for the web content system.
Pre-rendered delivery
We can pre-render a complete website into HTML and save it to disk. The pre-rendered site can then be used as the live site and displayed to 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, such as portlets, and the content is static and is updated only periodically.
Servlet delivery
Users can access content displayed via the Web Content Manager servlet. A servlet-delivered website should be used when you don't need to use any WebSphere Portal based features such as authoring tools.
Local web content viewer delivery
Web content viewers are portlets that display content from a web content library as part of a portal page. If the presentation is simple, a single web content viewer can be sufficient, but we can also use multiple web content viewers to aggregate content from different libraries and provide a richer experience for the users. A local web content view portlet is used to display content within the web content delivery environment.
Remote web content viewer delivery
A remote web content view portlet is used to display content on a remote WebSphere Portal server or cluster.
Parent: Create a design documentRelated: