# Installation and Upgrade Guide

# Clustering

This chapter describes how Publisher supports limited clustering in order to provide high availability of published content. To install a clustered configuration you should set up an additional Publisher installation on a second machine. Then you should set up a virtual host so that the portal will attempt to access multiple machines for the Published Content web service.

Figure A-1 gives an overview of the highly available published content configuration. Clustering involves the mapping of multiple IP addresses to a single machine domain name, sometimes referred to as the `virtual host' (see `pcr.publisher.host' in Figure A-1).

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

Figure A-1 High-Availability Published Content Configuration

## Deploying Published Content Separately from the Publisher in the Full Configuration

##### Undeploying Published Content from the Default Location

To undeploy published content from the default location:

1. Delete <install_root>/ptcs/6.3/container/conf/jboss.web/localhost/publishedcontent.xml.
2. Deploy published content in any other Web server.
3. Change the publishing targets in the Publisher Explorer.

##### Installing the Second Publisher

To perform a second installation on a different machine:

1. Run the Publisher installer.
2. On the Configuration page in the installation wizard, select Published Content Configuration.
3. On the Publisher Database and Portal Database pages, use the same Publisher and Portal Database information that you entered for the full Publisher installation.
4. For the Authentication Information, use the same authentication information you entered for the full Publisher installation.

##### Configuring AquaLogic Interaction

1. Set up your virtual host.

This virtual host should map to your full Publisher as well as the Published Content Configuration installation. You can either use a DNS Server or the Registry. Refer to the Deployment Guide for BEA AquaLogic User Interaction G6 and Knowledge Base Article #10613: INFO: MPPE Load Balancing: Frequently Asked Questions (FAQ).

2. Change 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. On the Administration page, select the Published Content web service.
5. In the Web Service Editor, under HTTP Settings, change the portlet URL by entering the full URL to the virtual host.

It should look something like this: http://<virtual_host_name>:<virtual_host_port>/ptcs/published_content_redirect.jsp.

Note: | The URL prefix is ignored if the value in the text box begins with "http://" or https://.

3. Start the Published Content Configuration.

Windows: From the Services control panel, select and start the BEA AquaLogic Publisher Redirector service. Or, from the command line, run $<install_root>\ptcs\6.3\bin\service.bat start.

UNIX: From the command line, run $<install_base>/ptcs/6.3/bin/service.bat start.

Note: | To verify your Published Content Configuration, first look at the diagnostic page, http://<host_name>:<port>/ptcs/console/index.jsp. All values should either display a "NOT ENABLED" or "OK" status. Secondly, verify that you can still access your published content portlets. If you shut down your Publisher Full Configuration, you should still see your published content portlets.