> Installation and Upgrade Guide > Clustering

Installation and Upgrade Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Clustering

This appendix describes how Publisher supports limited clustering in order to provide high availability of published content.

Note: If you do not currently have any Publisher published content, create a Publisher portlet using your full Publisher installation, add it to a page, and verify that the portlet is displayed correctly. After setting up the Published Content Redirector, use this portlet to verify that published content can still be accessed.

To install a clustered configuration:

  1. Undeploy your published content from the default location. For details, see Undeploying Published Content.
  2. Install the Published Content Configuration instance of Publisher. For details, see Installing the Published Content Configuration.
  3. Start and verify the Published Content Configuration installation. For details, see Starting and Verifying the Published Content Configuration.
  4. Configure the Published Content Redirector. For details, see Configuring the Publisher Redirector.

 

High-Availability Overview

Figure B-1 gives an overview of the highly available published content configuration. This configuration uses clustering, which involves mapping of multiple IP addresses to a single machine domain name, sometimes referred to as the ‘virtual host’ (see ‘pcr.publisher.host’ in Figure B-1).

Figure B-1 High-Availability Published Content Configuration

High-Availability Published Content Configuration

 

Undeploying Published Content

This section describes how to undeploy your published content from the default location. If your published content is deployed to another Web server, you can skip this step.

To undeploy published content from the default location:

  1. Delete <PT_HOME>/ptcs/6.4/container/conf/jboss.web/localhost/publishedcontent.xml.
  2. Deploy the published content on another Web server.
  3. Update the publishing targets in Publisher Explorer to reflect the new published content location. For more information on changing updating targets, see Updating Publishing Targets.

    4. Republish your existing content to the new location and verify that published content portlets display properly.

 

Installing the Published Content Configuration

To perform a second installation on a different machine:

  1. Run the Publisher installer. For details on running the installer, see Installing the Publisher Components.
  2. On the Choose Components page in the installation wizard, select Publisher.
  3. On the Configuration page in the installation wizard, select Published Content Configuration.
  4. Complete the remaining wizard pages using the same information you entered for the full Publisher installation.

 

Starting and Verifying the Published Content Configuration

After installing the Published Content Configuration, start and verify the installation.

To start the Published Content Configuration:

To verify the Published Content Configuration:

Browse to the Publisher diagnostics page:

http://<published_content_host>:<port>/ptcs/console/index.jsp

Enter the authentication ID and password you created during installation in the authentication challenge box. All values should display either “NOT ENABLED” or “OK” status.

 

Configuring the Publisher Redirector

To configure the Publisher Redirector for high availability:

  1. Set up the virtual host:
    1. For each Portal server in your deployment, edit the file serverconfig.xml, found in the following location:
      • On Unix: /opt/bea/alui/settings/common
      • On Windows: C:\bea\alui\settings\common
    2. Add the following settings under the section <component name="openhttp" type="http://www.plumtree.com/config/component/types/openhttp">:
Note: <setting name="openhttp:LoadBalancedHost0">
Note: <value xsi:type="xsd:string"><hostname0></value>
Note: </setting>
Note: <setting name="openhttp:LoadBalancedIPs0">
Note: <value xsi:type="xsd:string"><IP1>;<IP2></value>
Note: </setting>
Note: <setting name="openhttp:FailuresTimeToClear">
Note: <value xsi:type="xsd:integer">30</value>
Note: </setting>
    1. In the “openhttp:LoadBalancedHost0” setting, replace <hostname0> with the host name you want to use to access published content.
    2. In the "openhttp:LoadBalancedIPs0" setting, replace <IP1> and <IP2> with the IP addresses of the Publisher full installation and Published Content Configuration machines.
    3. Restart the Portal servers.
  1. Update the Published Content Web service portlet URL:
    1. Log in to the portal.
    2. Click Administration.
    3. In the Admin Objects Directory, open the folder in which the Publisher Web services were created.
    4. Edit the Published Content Web service.
    5. On the Main Settings page, under HTTP Settings, type the full URL to the virtual host in the Portlet URL text box. <virtual_host_name> is the value you entered for <hostname0> when configuring serverconfig.xml.

      6. Example: http://<virtual_host_name>:<virtual_host_port>/ptcs/published_content_noredirect.jsp

      Note: The URL prefix is ignored if the value in the text box begins with “http://” or https://.
  2. Verify that you can still access your published content portlets by shutting down your Publisher full configuration instance. Your published content portlets should still display properly.

  Back to Top       Previous  Next