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.
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
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:
Deploy the published content on another Web server.
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.
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:
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:
Set up the virtual host:
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
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>
In the “openhttp:LoadBalancedHost0” setting, replace <hostname0> with the host name you want to use to access published content.
In the "openhttp:LoadBalancedIPs0" setting, replace <IP1> and <IP2> with the IP addresses of the Publisher full installation and Published Content Configuration machines.
Restart the Portal servers.
Update the Published Content Web service portlet URL:
Log in to the portal.
Click Administration.
In the Admin Objects Directory, open the folder in which the Publisher Web services were created.
Edit the Published Content Web service.
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.
The URL prefix is ignored if the value in the text box begins with “http://” or https://.
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.