Custom Installation Process

In a standard installation there is no need to perform the steps outlined in this topic. You will only need to perform a Custom Web Content Management installation if:

 

Mandatory Custom Installation tasks:

Edit wpconfig.properties By default, Web Content Management will be installed using a Cloudscape database as the data repository. If you would like to use this as your data repository you can skip this step.

If you would like to use a different data repository edit the Web Content Management section of the wpconfig.properties file. This is located under /PortalServer/config

Run create-wcm-tables

This step is not required if you are using the default Cloudscape data repository or installing on z/OS.

For other data repositories, run the create-wcm-tables configuration task to create the necessary Web Content Management tables based on the settings in wpconfig.properties

Run configure-wcm configuration Run the configure-wcm configuration task will:

  • Update the Web Content Management configuration files based on the settings in wpconfig.properties
  • Enable the Data Repository specified in wpconfig.properties
Run configure-wcm-authoring This task is used to create a Web Content Management portal page and install the Authoring Portlet (Web Content Authoring) on that page.

Note that the WebSphere Portal Administrators group is not automatically added to the wcmadmins group. If you would like WebSphere Portal Administrators to have Administration access to Web Content Management and the Authoring Portlet (Web Content Authoring), manually add the WebSphere Portal Administrators group to the wcmadmins group in Member Manager.

 

Optional Tasks:

The following tasks are optional and should only be run after completing the default or advanced installation tasks:

Run config-wcm-repository To change your Web Content Management data repository run this configuration task.
Run update-wcm-wmm This task should be run whenever a WebSphere Member Manager registry type is changed after the initial WebSphere Portal installation. E.g. - if the WebSphere Member Manager registry type is changed from the default database to LDAP. This task will re-configure the custom Web Content Management attributes within Member Manager.

 

Migrating Data from previous versions of Web Content Management

See the Upgrading Web Content Management topic for information on migrating Data from previous versions of Web Content Management.

 

Install on z/OS

These instructions are based on an installation using the WebSphere Portal InstallShield Installer.

The Customization Dialog of WebSphere Portal for z/OS is used to install and configure your portal installation. Refer to the z/OS Installation Process topic for an overview of installing Web Content Management applications on z/OS.

Detailed information on using the Customization Dialog and defining variables can be found in the WebSphere Portal for z/OS Information Center under...

Installing | Customization Dialog tasks - Worksheets and Definitions | Configure IBM Workplace Web Content Management

Install on i5/OS

When installing WebSphere Portal and IBM Workplace Web Content Management on i5/OS, the JVM Maximum Heap Size setting must remain at 0. A value of 0 specifies that there is no maximum value.

Parent topic: Installation Scenarios.


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.