Vertical Cluster Installation Process

 

Overview

Web Content Management applications cannot be clustered vertically themselves, but they can be installed in a vertical cluster environment.

A Web Content Management application cannot be used as an "authoring application" in a clustered environment. It can only be used as a staging or delivery application. This means that although the Authoring Portlet (Web Content Authoring) is installed on Web Content Management staging and delivery applications in a clustered environment, you cannot use the Authoring Portlet (Web Content Authoring) to author content. On staging and delivery applications, the Authoring Portlet (Web Content Authoring) is only used to manage syndication and caching.

Each Web Content Management application installed in a clustered environment must use a separate data repository.

Syndication must be used to keep each Web Content Management application synchronized.

 

Primary Node

When installing Web Content Management on a primary node, :

  1. Install Web Content Management as specified in either the Standard Installation Process or the Custom Installation Process topics.

  2. Once Web Content Management has been successfully installed and configured, then configure WebSphere Portal as a primary node.

 

Secondary Nodes

When a Web Content Management application is installed on a primary node, it is installed under...

/PortalServer/wcm/

To create secondary Web Content Management applications do the following:

  1. Copy and rename the...

    /PortalServer/wcm/

    ...directory for each additional Web Content Management application you would like to install. For example:

    cp -r /PortalServer/wcm/ /PortalServer/wcm2/

  2. Edit the following files under the new "wcm" directory:
    /PortalServer/wcm2/config/connect.cfg
    /PortalServer/wcm2/config/aptrixsearch.properties

    Change all references to the original "wcm" directory to the new directory. For example, change...

    /PortalServer/wcm

    ..to...

    /PortalServer/wcm2

    Do NOT change any other references to "wcm". For example, do not change...

    http://host:9081/wps/wcm

    ...to...

    http://host:9081/wps/wcm2

  3. Update the following settings in...

    /PortalServer/wcm2/config/aptrixjpe.properties

    ...to point to a new schema in your data repository:

    Note that in i5/OS installations, Web Content Management files are located in the "wp_user_root" directory, not "/PortalServer/wcm/". For example in a WAS 5.1.1.3 system...

    /QIBM/UserData/WEBAS51/Base/instance_name/PortalServer51

    ...and in a WAS 6 system...

    /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/instance_name/PortalServer51

  4. Open the WebSphere Administration console and go to:

    Servers | Application Servers | secondary Portal server node | Process Definition | Java Virtual Machine

    Under the Generic JVM arguments add the following argument to the end (separated from the rest by a space)

    -DAptrixConnect.ConfigFileLocation=portal_dir/wcm2/config/connect.cfg

    Replace portal_dir with the absolute file location of the portal install.

  5. Restart all clustered WebSphere Portal nodes.

 

Enable Syndication Between Nodes

Syndication is used as the transport layer that replicates data from one Web Content Management application to another. Perform the following steps to enable Syndication between Nodes

  1. Configure a Virtual Host within the Deployment manager to allow access to the individual Web Content Management nodes within the cluster:

    • Open the WebSphere Administrative Console and go to...

      Environment | Virtual Hosts | default_host | Host Aliases | New

    • Add the hostname and port that correspond to the Web Container HTTP Transport. For example, wpwcm21.ibm.com, port 9081.

    • Save these settings.

  2. Use Web Content Management Syndication to populate each Web Content Management repository in the cluster.

 

Removing a Web Content Management Application from a Cluster

If at any stage you remove a Web Content Management Application from a Cluster do the following:

 

Standard Cluster Installation Process

These instructions detail how to install Web Content Management applications in a vertically clustered environment. To install Web Content Management applications in a standard clustered environment, see the Cluster Installation Process topic.

 

z/OS Cluster Installation Procedures

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

 

Distributed Session Persistence

The Web Content Management Authoring portlet and Local Rendering Portlet cannot be used in a clustered environment that has distributed session persistence enabled. To display Web Content Management content in WebSphere Portal pages in a clustered environment that has distributed session persistence enabled use a Remote Rendering Portlet pointing to a Web Content Management application located outside the clustered environment.

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.