# Installation and Upgrade Guide

# Upgrading Publisher

This chapter discusses how to upgrade from previous versions of Publisher or Content Server. The following table summarizes possible upgrade paths and upgrade documentation:

Table 6-1 Upgrade Paths
Upgrade Path | Upgrade References
--- | ---
5.x - 6.3 6.x - 6.3 | Follow the procedures in Upgrade Steps If you are upgrading from 5.x, you will need to update the Web service UUIDs in the portal database. See Upgrade The Web Services UUIDs in the Portal Database If you are upgrading from 5.x or 6.0, see Additional Information for Content Server 5.x and 6.0 Upgrades
4.x to 6.3 | You must first upgrade to Content Server 5.0.2 or higher, then upgrade to Publisher 6.3. Refer to the Installation and Upgrade Guide for Plumtree Content Server for version 5.0.4. Follow the instructions in that guide for upgrading to 5.0.4, including all of the 4.x post-upgrade instructions. Validate that you can bring up portlets in the 5.0.4 state before starting the 6.3 upgrade.

## Upgrade Steps

To upgrade to Publisher 6.3:

1. Read the release notes for a summary of features introduced or changed in this and all previous releases.
2. Complete all pre-installation steps. For details, see Pre-Installation Steps.
3. Log onto the machine on which you will be doing the install as a local administrator. It is assumed that this is the application server that hosts the preexisting version of Content Server/Publisher.
4. Uninstall the old version of Content Server/Publisher. Ensure that the application is removed from the application server after uninstall.

Note: | This is recommended; however, in a development environment, the old version of Content Server/Publisher can coexist with Publisher 6.3 if they are configured to listen to different ports.

5. Stop the Workflow service.
6. Back up your existing AquaLogic Interaction Portal, Content Server/Publisher, and Workflow databases. Restore only if you abort the installation.
7. Install Publisher software as described in Installing Publisher. When the installer prompts you, reboot the machine.

If you do not reboot, certain PATH environment variable changes might not take effect, and you will get errors when you try to deploy and start the applications.

You do not need to reboot a UNIX machine.

Note: | Although you will enter information about the default published content location and URL in a Publisher installer panel, Publisher 6.3 does not change your publish and preview targets upon upgrade. If you want to change your publish targets, including changing the port number, you can do this with Publisher Explorer after you complete the upgrade. Changing the publish targets also requires republishing your existing content.

8. Upgrade the Workflow database. Locate your current configuration in the table below and follow the appropriate instructions:.

   Table 6-2 Workflow Database Upgrade Instructions
   Content Server Configuration | Workflow Database Upgrade Instructions
   --- | ---
   Content Server 5.x, 6.0, or 6.1; no existing Workflow database. | Create a Workflow database and user with the information you entered in the installer. Refer to Creating Databases and Database Users for Publisher for full details on database and user creation for the database you are using. Log into SQL Query Analyzer or SQL Plus as the Workflow database user. For SQL Server: Run the script <install_root>\ptworkflow\6.3\sql\mssql\create_schema.sql. For Oracle: Run the script <install_root>\ptworkflow\6.3\sql\oracle9.2\create_schema.sql. or <install_root>\ptworkflow\6.3\sql\oracle10\create_schema.sql depending on your version of Oracle.
   Content Server 5.x; existing Workflow database. | Run the create_schema.sql script for your database. Run the dbupgrade.bat script: Windows: Run the script <install_root>\ptworkflow\6.3\bin\dbupgrade.bat. UNIX: Run the script <install_root>/ptworkflow/6.3/bin/dbupgrade.sh.
   Content Server 6.0, existing Workflow database | Oracle: Run the script for your version of Oracle: <install_root>\ptworkflow\6.3\sql\oracle9.2\upgrade_schema6.1.sql <install_root>\ptworkflow\6.3\sql\oracle10\upgrade_schema6.1.sql
   Note: | There is no upgrade_schema6.1.sql script for SQL Server.
   Content Server 6.1; existing Workflow database | Oracle and SQL Server: Run the script appropriate to your database server: <install_root>\ptworkflow\6.3\sql\oracle9.2\upgrade_schema6.2.sql <install_root>\ptworkflow\6.3\sql\oracle10\upgrade_schema6.2.sql <install_root>\ptworkflow\6.3\sql\mssql\upgrade_schema6.2.sql
   Publisher 6.2 | No upgrade scripts are necessary.

9. If applicable, modify the configuration files in <installation_folder>\ptcs\6.3\settings\config to configure your customized settings.
10. If applicable, restore SSL certificates to <installation_folder>\ common\jre\1.4.2\lib\security.
11. Register the Content Server /Publisher objects with the portal. For details, see Import the Publisher Migration Package.
12. After importing the publisher.pte file, ensure that the Document Repository Service and Search Service are started. Then start Publisher.
13. Import the published_content_portlets.pte file. For details, see Import the Published Content Portlets Migration Package.
14. If you are upgrading from 5.0.x, upgrade the Web Services UUIDs in the portal database. For details, see Upgrade The Web Services UUIDs in the Portal Database.

Note: | If your previous 5.0.x installation included a Branding Remote Server, this object can be safely deleted after upgrading to 6.3 because it is no longer used. To do so, go to your portal administration hierarchy, browse to the Branding folder and then delete the Branding Remote Server.

15. If your published content is on a remote server, you are done. If your published content is located on the same host as Publisher, copy or move your published content from the old location to the new install directory structure. If you have accepted all defaults, copy or move all files from

\plumtree\ptcs\publishedcontent

to

\bea\alui\ptcs\publishedcontent

16. Point Publisher to the new published content location. From Publisher Explorer, right click on the root (plumtree) node and choose Publishing Targets.
17. Update the Transfer Path to point to the new published content location (see step 15).
18. If your Publisher port has changed, update the Browser Path to reflect the new port number.

## Upgrade The Web Services UUIDs in the Portal Database

If you have a preexisting 5.0.x portal and Content Server installation, it contains different Web services objects for the published content portlet templates (like the News Portlet Template) and branding portlet templates (like the Header, Footer, or Canvas template). Publisher 6.3 replaces these five distinct Web services with a single Web service.

As the final step of an upgrade from 5.0.x, you must run a script against the portal database that updates the Web service UUIDs for existing portlets to point to the newer Publisher Web service for published content. This script affects only the portal objects that relate directly to Publisher and Workflow portlets and portlet template integration.

To upgrade your Web Services UUIDs, execute one of the following scripts:

- For a MS SQL Server portal database, log into SQL Query Analyzer as the portal database user and run the SQL script
  <install_root>\ptcs\6.3\sql\mssql\portal_upgrade_5.0_to_6.0.sql.
- For an Oracle portal database, log into Oracle Enterprise Manager as the portal database user. Then open SQL*Plus and run the SQL script
  <install_root>\ptcs\6.3\sql\oracle9.2\portal_upgrade_5.0_to_6.0.sql.

## Additional Information for Content Server 5.x and 6.0 Upgrades

The following are important differences between Publisher 6.3 and versions of Content Server prior to Content Server 6.1:

- Simplified Deployment: Publisher 6.3 contains a significant change in the deployment configuration for the product. Instead of installing the product, installing a separate Application Server, and deploying a WAR file to the Application Server, Publisher 6.3 is self-contained. It includes the runtime components needed for HTTP/HTTPS processing, and it no longer requires a separate application server. This change makes the product easier to install and maintain.
- BEA AquaLogic Publisher Service: After you install or upgrade to 6.3, there is a single service (or daemon on UNIX) that starts and stops both the Publisher and Workflow applications. The service is controlled from the Services control panel on Windows and from the command line on UNIX. In previous versions, Content Server was deployed to a separate application server, and Workflow was a standalone service. For more information on starting and stopping the Publisher Service, see Start Publisher and Workflow
- Single port number: The BEA AquaLogic Publisher Service runs on a single port number. In previous versions, the Content Server Web application ran on one port number, and the Workflow Server ran on a different port number. We recommend the use of port 7087 for the BEA AquaLogic Publisher Service . Version 6.3 includes a container.conf file containing any port number settings that need to be changed after installation.