Configure a Web content authoring environment
Set up the authoring server by installing the authoring portlet and enabling other features required to support the authoring environment.
The following illustration highlights the server that you will setup during this portion of the installation process.
- Installing the authoring portlet
Pages that include the Web Content Management authoring portlet and the local rendering portlet are created when you first install WebSphere Portal. You only run the authoring portlet configuration task if you have previously uninstalled your authoring or local rendering portlets. The authoring portlet configuration task will automatically create Web Content Management pages and install the authoring portlet and local rendering portlets.
- Configure the Authoring Portlet
An authoring portlet is used to create and manage Web content.
- Additional authoring portlet configuration options
Additional authoring portlet configuration options can be specified using the portlet administration view.
- Web content authoring options
Define the following authoring server options in WCMConfigService.properties.
- Configure authoring portlet search
You can change the configuration of the authoring portlet to change how search works.
- Import large files and images
Because importing large files into IBM Lotus Web Content Management can have a negative impact on performance, you can adjust several settings to ensure better performance when importing files.
- Increase time-outs
If users are experiencing timeout errors when saving items, you can increase the total transaction lifetime timeout setting of your WebSphere Portal server.
- Configure remote server access for links
Before you can add links to files and documents stored in remote content management systems into Web content elements, configure your server with information about the remote system and the settings used to handle communication with the system.
- Set up the Missed Absolute Path Cache
To improve the performance of contextual linking you can enable a Missed Absolute Path Cache. The Missed Absolute Path Cache functionality requires a dynamic object cache to be setup in WAS before it can be utilized. This cache should be installed by default, but if you need to create this, follow these instructions:
- Set up support for federated documents
Before you can access metadata from federated documents, configure the federated documents feature. You can also tune the cache settings that are used with the federated documents feature.
Parent topic:
Configure Web Content Management