# Installation and Upgrade Guide

# Upgrading Collaboration on UNIX and Linux

This chapter discusses how to upgrade from previous versions of Collaboration to Collaboration 4.1.

The following table summarizes upgrade paths and upgrade documentation:

Table 7-1 UNIX and Linux Upgrade Paths
Upgrade Path | Upgrade References
4.1 SP1 to 4.1 SP2 | Run the installer according to the procedures in Installing Collaboration on UNIX or Linux.
4.1 to 4.1 SP2 | Run the installer according to the procedures in Installing Collaboration on UNIX or Linux.
4.0.2 to 4.1 | Run the pre-upgrade procedures outlined in Pre-Upgrade Procedures. Run the installer according to the procedures in Installing Collaboration on UNIX or Linux.
Note: | You must also upgrade the Notification Service and Image Service when running the installer.
Run the post-upgrade procedures outlined in Post-Upgrade Procedures.
2.x to 4.1 | To upgrade from Collaboration Server 2.x, you must first upgrade to version 3.x, then upgrade to version 4.0.2, before upgrading to version 4.1. Collaboration 3.x was released only on Windows. The installation of 3.x must take place on a Windows machine. Refer to the Installation Guide for Plumtree Collaboration Server 3.0 for information on this upgrade path.

## Pre-Upgrade Procedures

This section describes the procedures you must perform before running the Collaboration installer. You must follow these procedures in the following order:

1. Backup the portal and Collaboration databases.

This allows you to recover your data if there is a problem during installation. For more information see your database documentation.

2. Stop the Notification Service, Search Service and Automation Service.

## Running the Installer

After you have completed the pre-installation procedures:

1. Copy the installer files to the directory where you have installed the old versions of the Collaboration files.

This allows the installer to use the silent properties file created by previous installations. For more information on using the silent properties file, see Silent Properties File.

Note: | The 4.1 version of Collaboration cannot point to a pre-Foundation 6.0 Document Repository. If you are running Plumtree Corporate Portal 5.0.x, you will need to install the 6.0 Document Repository as instructed in step 2. Review the silent properties file carefully for those new AquaLogic Interaction G6 components which may have different ports.

2. On the machine where you installed the previous version of Collaboration, run the installer and choose the following components:

- Collaboration
- Notification Service

If you are running Plumtree Corporate Portal 5.0.x, also install the Document Repository component at this time.

For step-by-step details on running the installer, see Installing Collaboration on UNIX or Linux.

3. On the machine where you installed the previous version of the Image Service, run the installer and choose the following component:

- Image Service

Note: | Note: Install Image Service Files on the same machine on which the portal's Image Service is installed.

For step-by-step details on running the installer, see Installing Collaboration on UNIX or Linux.

## Post-Upgrade Procedures

This section describes the procedures you must perform after running the Collaboration installer. You must perform these procedures in the following order:

1. Upgrade the Collaboration database.

The following sections describe the procedures for updating the portal and Collaboration databases. You must upgrade both the Collaboration database and the portal database. Both databases must reside on the same computer.

Before you run the SQL scripts described below, you must upgrade the portal to version 6.x. For more information, see the Installation and Upgrade Guide for BEA AquaLogic Interaction (UNIX and Linux) (Plumtree Foundation). Before upgrading, ensure that both databases are working correctly and you have access to them.

Upgrading Databases Using Oracle

Assuming that you installed the Collaboration files in the default location, the Oracle upgrade script files are located on the Collaboration computer in one of the following folders:

    $PT_HOME/ptcollab/4.1/sql/6.0/Oracle/OracleUnix9.2

    $PT_HOME/ptcollab/4.1/sql/6.0/Oracle/OracleUnix10

Perform the following to upgrade the Collaboration and portal databases:

1. Copy the Collaboration database upgrade scripts from the default installation location to an Oracle folder or subdirectory on the computer where the database resides.
2. Ensure that you have installed the latest Oracle patches.
3. Configure the database to archive log files if you are upgrading in a production environment.
4. Shut down the database to get a read-consistent backup.
5. Using SQLPlus and the Collaboration database server schema user ID and password, run collaboration-server-4-0-2-to-4-1-0-upgrade.sql. Then run collaboration-server-4.1.1-to-4.1.2-upgrade.sql. Then run collaboration-server-portal-role-grant.sql.
6. Using SQLPlus and the portal database server schema user ID and password, run portal-collaboration-server-data.sql. Then run portal-collaboration-server-role-grant.sql. Then run portal-collaboration-server-upgrade.sql.

2. Import the Collaboration Migration Package using the Migration Utility. This ensures that the paths to the portlets are upgraded to the new version. The following instructions are for Foundation 6.0. For a 5.0.x portal, import Collaboration5.pte found in <PT_HOME>/`ptcollab/4.1/serverpackages/5.0.`

1. Log on to the portal as a user who has administrative rights.
2. Click the Administration tab.
3. In the Select Utility drop-down, select Migration-Import and accept the defaults.
4. In the Migration Package area, go to File Path.
5. Click Browse to find the Collaboration6.pte file, located in `<PT_HOME\ptcollab\4.1\serverpackages\6.0`
6. Click Open.
7. Click Load Package.
8. If you are upgrading from an earlier version of Collaboration and have changed the port number that Collaboration runs on, check Overwrite Remote Servers.
9. Click Finish.
10. A pop up dialog displays asking if you want to import. Click OK.
11. The Collaboration folder is viewable in the Admin Objects Directory.
12. Click the Collaboration folder to check for the following objects: Content Source; Group; Portlet; Remote Server; Property; Web Service.

3. If you have set Collaboration to manually capture portal gateway values you must change the Web Service ID being used. It must be set to the WebService ID of the Notification Gateway Entry, which can be found in Collaboration Administration's Portal Access page.
4. Configure optional Collaboration features.

For more information on configuring these features, see Configuring Advanced Collaboration Features.

5. Restart the portal.
6. Start the Notification Service.
7. Start Collaboration.
8. If your portal is 5.0.x, start the G6 Document Repository you installed in Step 2.
9. To verify Collaboration is running, access the Collaboration Diagnostics page using the following URL:

    http://<your-collab-URL>:<your-collab-port>/collab/admin/diagnostic

For more information on using the Collaboration Diagnostics page, see Troubleshooting

10. Rebuild the Search Collection. After restarting Collaboration, perform the following steps to rebuild the search collection:

1. Log on to the portal computer as a portal administrator.
2. Click Administration.
3. Choose the Collaboration Administration utility.
4. Click Search Service.
5. Click Rebuild Search Collection.
6. Click OK.