# Installation and Upgrade Guide

# Upgrade

This chapter discusses how to upgrade from previous versions of Collaboration to the current version. This chapter lists upgrade paths and describes the following procedures, which you must perform in sequential order:

1. Running the Installer During Upgrade
2. Upgrading the Portal and Collaboration Databases
3. Post-Upgrade Procedures

Note: | If you are upgrading Oracle from 10.1.x to 10.2.x or SQL Server from 2000 to 2005, you should perform the Oracle or SQL Server upgrade before upgrading Collaboration.

## Upgrade Paths

The following table describes the upgrade paths that you can follow to upgrade to the current version of Collaboration:

Table 5-1 Upgrade Paths
Upgrade Path | Description
--- | ---
4.2 to 4.2 MP1 | Run the Collaboration installer and perform post-upgrade procedures (a script for upgrading the portal and Collaboration databases from 4.2 to 4.2 MP1 does not exist). For more information, see: Running the Installer During Upgrade Post-Upgrade Procedures
4.1 SP2 to 4.2 MP1 | Perform the procedures that are described in this chapter in sequential order. When performing the procedure “Upgrading the Portal and Collaboration Databases”, run the collaboration-server-4.1.2-to-4.2.1-upgrade.sql upgrade script.
4.1 SP1 to 4.2 MP1 | Perform the procedures that are described in this chapter in sequential order. When performing the procedure “Upgrading the Portal and Collaboration Databases”, run the following scripts in sequential order: collaboration-server-4.1.1-to-4.1.2-upgrade.sql collaboration-server-4.1.2-to-4.2.1-upgrade.sql
4.1 to 4.2 MP1 | Perform the procedures that are described in this chapter in sequential order. When performing the procedure “Upgrading the Portal and Collaboration Databases”, run the following scripts in sequential order: collaboration-server-4.1.1-to-4.1.2-upgrade.sql collaboration-server-4.1.2-to-4.2.1-upgrade.sql
Note: | You do not need to run an upgrade script for upgrading Collaboration 4.1 to 4.1 SP1. For this reason, you run the script for upgrading Collaboration 4.1 SP1 to 4.1 SP2 when performing this upgrade.
4.0.2 to 4.2 MP1 | Perform the procedures that are described in this chapter in sequential order. When performing the procedure “Upgrading the Portal and Collaboration Databases”, run the following scripts in sequential order: collaboration-server-4-0-2-to-4-1-0-upgrade.sql collaboration-server-4.1.1-to-4.1.2-upgrade.sql collaboration-server-4.1.2-to-4.2.1-upgrade.sql
(Windows Only) 3.x to 4.2 MP1 | If you are currently on Collaboration Server version 3.x, you must first upgrade to Collaboration Server 4.0.2. Refer to the Installation Guide for Plumtree Collaboration Server 4.0.2 for information on this upgrade path. After upgrading to Collaboration Server 4.0.2, upgrade Collaboration according to the instructions described in the 4.0.2 to 4.2 MP1 upgrade path.
2.x to 4.2 MP1 | If you are currently on Collaboration Server version 2.x, you must first upgrade to Collaboration Server 3.x. Refer to the Installation Guide for Plumtree Collaboration Server 3.0 for information on this upgrade path. After upgrading to Collaboration Server 4.0.2, upgrade Collaboration according to the instructions described in the 3.x to 4.2 MP1 upgrade path.
Note: | UNIX/Linux users - Collaboration 3.x was released only on Windows. The installation of 3.x must take place on a Windows machine.

## Running the Installer During Upgrade

To run the installer during upgrade:

1. Backup the portal and Collaboration databases and the Document Repository Service.

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

2. Stop the BEA ALI Collaboration service, Notification Service, Search Service, Automation Service and Document Repository Service.
3. Clear the embedded application server’s work directory. By default, this directory is located in:

- (Windows) C:\bea\alui\common\container\tomcat\<version>\work
- (UNIX/Linux) /opt/bea/alui/common/container/tomcat/<version>/work

4. 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.

5. On the machine hosting the previous version of Collaboration, run the installer and choose the following components:

- Collaboration
- Notification Service

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

6. Run the Collaboration installer on the machine on which you installed the portal’s Image Service. Choose the Image Service Files component.
7. (Windows only) Reboot the machine on which Collaboration is installed.

## Upgrading the Portal and Collaboration Databases

This section describes updating the portal and Collaboration databases. Perform the procedure that is appropriate to your database platform

Note: | You must upgrade both the portal and Collaboration databases. Additionally, both databases must reside on the same computer.

### Upgrading Oracle Databases

Assuming that you installed the Collaboration files in the default location, the Oracle upgrade script files are located on the Collaboration computer.

To upgrade Oracle 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. The scripts are located in one of the following paths:

- (Windows) <PT_HOME>\ptcollab\4.2\sql\6.1\Oracle\OracleNT9.2 OR <PT_HOME>\ptcollab\4.2\sql\6.1\Oracle\OracleNT10
- (UNIX/Linux) <PT_HOME>\ptcollab\4.2\sql\6.1\Oracle\OracleUnix9.2 OR <PT_HOME>/ptcollab/4.2/sql/6.1/Oracle/OracleUnix10

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 the upgrade script that is appropriate to your upgrade path. These scripts upgrade the Collaboration database schema:

- collaboration-server-4-0-2-to-4-1-0-upgrade.sql
- collaboration-server-4.1.1-to-4.1.2-upgrade.sql
- collaboration-server-4.1.2-to-4.2.1-upgrade.sql

Note: | If you are performing multiple upgrades, run the upgrade scripts in the order listed in Upgrade Paths.

6. Run the collaboration-server-portal-role-grant.sql script.
7. Using SQLPlus and the portal database server schema user ID and password, run the following:

- portal-collaboration-server-data.sql
- portal-collaboration-server-role-grant.sql
- portal-collaboration-server-upgrade.sql

### Upgrading SQL Server Databases (Windows Only)

Assuming that you installed the Collaboration files in the default location, the MS SQL Server 2000 upgrade script files are located on the Collaboration computer. These scripts are located in:

<PT_HOME>\ptcollab\4.2\sql\6.1\MSSQLServer

To upgrade SQL Server databases:

1. Run Query Analyzer.
2. Open, then run the following script files on the Collaboration database as the Collaboration database user:

- collaboration-server-4-0-2-to-4-1-0-upgrade.sql
- collaboration-server-4.1.1-to-4.1.2-upgrade.sql
- collaboration-server-4.1.2-to-4.2.1-upgrade.sql
- collaboration-server-portal-role-grant.sql

Note: | If you are performing multiple upgrades, run the upgrade scripts in the order listed in Upgrade Paths.

3. Open, then run the following script files on the portal database as the portal database user:

- portal-collaboration-server-role-grant.sql
- portal-collaboration-server-data.sql
- portal-collaboration-server-upgrade.sql

4. Close Query Analyzer.

## Post-Upgrade Procedures

This section lists, in order, additional procedures that you must perform after upgrading the portal and Collaboration databases.

1. Import the migration package. For details, see Importing the Collaboration Migration Package.
2. 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.
3. Start the Notification Service. For details, see Starting the Notification Service.
4. Start Collaboration. For details, see Starting Collaboration.
5. If desired, configure the following advanced Collaboration features:

- Personal Projects
- Bulk Upload
- Groupware Integration
- Publish to Knowledge Directory

6. For more information on configuring these features, see Administrator Guide for BEA AquaLogic Interaction Collaboration.
7. Verify that Collaboration is functioning correctly by accessing and analyzing the Collaboration Diagnostics page:

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

For more information on using the Collaboration Diagnostics page, see Administrator Guide for BEA AquaLogic Interaction Collaboration.

8. 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.