Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Configure Web Content Management
All the files required to configure and use IBM® Workplace Web Content Management™ are installed with IBM WebSphere® Portal Express by default. The section describes how to enable and configure the Web Content Management module for Web content authoring and delivery.
Before installing and configuring WebSphere Portal Express for use as a Web Content Management server, you should read the entire Installing section to determine the best overall configuration for your WebSphere Portal Express server.
A Cloudscape database must not be used in a production environment or for authoring Web content. Cloudscape does not support vertical cloning, clustered environments, or enabling security in a database-only mode. You must use one of the other supported databases in a production environment or when authoring Web content, as they are better able to handle large amounts of data and can be tuned for performance.
You should also download the Web Content Management Best Practices Guide. This article covers a wide variety of topics that product experts have found critical to a successful implementation and useful environment. For example, you learn about such topics as migration considerations, content creation, search, taxonomies, syndication, access control, globalization, custom authoring interfaces, and performance tuning of various components.
- Configuration scenarios
There are three basic configuration scenarios for IBM Workplace Web Content Management; authoring, staging and delivery.
- Enabling e-mail for Web Content Management
To use the e-mail workflow action configure Web Content Management to use your SMTP server.
- Configuring Web Content Management search options
You can edit the following search options to manage how the search service works with Web Content Management search forms
- Federated content data source configuration
To use the federated content component, first configure your Web Content Management Server to link to a federated data source. Only one federated data source can be used per IBM Workplace Web Content Management server.
- Increasing the inbound buffer size
Because importing large files into IBM Workplace Web Content Management can have a negative impact on performance, you can set a limit on the size of the inbound buffer used when importing files.
- Increasing server time-outs
If users are experiencing timeout errors when saving items, you can increase the total transaction lifetime timeout setting of your WebSphere Portal Express server.
- Creating Web sites for different localities
Although Web sites that automatically display content for different localities or languages are not directly supported by Web Content Management, it is possible to maintain separate libraries and sites within IBM Workplace Web Content Management for different localities.
- Controlling access to hosts specified in connect tags
By default, connect tags can specify any host name. However, you can restrict access to a specified list of host names by modifying the WCMConfigService.properties file.
- Substitution variables used with IBM Workplace Web Content Management
IBM Workplace Web Content Management uses several substitution variables defined in the configuration for IBM WebSphere Application Server.
- Remove authoring configuration task
The remove authoring configuration task will uninstall the Web Content Management Authoring Portlet, Local Rendering Portlet and IBM Workplace Web Content Management Portal pages.
- Manually installing Web Content Management
In special circumstances you can manually install IBM Workplace Web Content Management after installing IBM WebSphere Portal Express.