WCM Planning

WCM Planning

+
Search Tips | Advanced Search

Overview

Before installing IBM Workplace Web Content Management (IWWCM), become familiar with the following:

WebSphere Application Server
WebSphere Portal IWWCM portlets are installed to the WebSphere Portal appserver running in WAS.
Installation Process

Data Repositories IWWCM data and sesources can be stored in IBM Content Manager, or in JDBC databases such as Cloudscape or DB2.
Refer to the documentation of each data repository product (IBM Content Manager, Cloudscape, DB2 etcetera.) to determine which data repository will be best suited to the IWWCM installation.
Architectures IWWCM installations usually involve more than one installation of an IWWCM application and IWWCM portlets. These multiple installations are used to separate authoring from delivery, load-balance a IWWCM environment, and to provide redundancy.
Delivery Options There are three methods available to deliver IWWCM content:

Via the IWWCM servlet.
Via a Rendering portlet.
Via a Pre-rendered site.

See the Content Delivery Guide for further information.
Caching Caching can provide significant performance increases and be implemented very simply in an IWWCM environment. IWWCM technology also provides a caching alternative for sites that aggregate information from multiple sources, and can cache on a per-user or per-site basis.
Refer to the Caching sections in the Installation Guide for more info.
Access and Security Access to the IWWCM Authoring Portlet (Web Content Authoring), and to rendered Web Sites, can be restricted to different users and groups.
See the Access and Security chapter for further information.

Parent topic: Installation Overview.
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.

WebSphere Application Server WebSphere Portal	IWWCM portlets are installed to the WebSphere Portal appserver running in WAS.
Installation Process
Data Repositories	IWWCM data and sesources can be stored in IBM Content Manager, or in JDBC databases such as Cloudscape or DB2. Refer to the documentation of each data repository product (IBM Content Manager, Cloudscape, DB2 etcetera.) to determine which data repository will be best suited to the IWWCM installation.
Architectures	IWWCM installations usually involve more than one installation of an IWWCM application and IWWCM portlets. These multiple installations are used to separate authoring from delivery, load-balance a IWWCM environment, and to provide redundancy.
Delivery Options	There are three methods available to deliver IWWCM content: Via the IWWCM servlet. Via a Rendering portlet. Via a Pre-rendered site. See the Content Delivery Guide for further information.
Caching	Caching can provide significant performance increases and be implemented very simply in an IWWCM environment. IWWCM technology also provides a caching alternative for sites that aggregate information from multiple sources, and can cache on a per-user or per-site basis. Refer to the Caching sections in the Installation Guide for more info.
Access and Security	Access to the IWWCM Authoring Portlet (Web Content Authoring), and to rendered Web Sites, can be restricted to different users and groups. See the Access and Security chapter for further information.