20.4 Updating a Multiple-Server Teaming System from 1.0 to 2.1

If your Novell Teaming 1.0 system is distributed across multiple servers, the Teaming 2.1 Installation program can update Teaming components on the Teaming server, but you must manually update any Teaming components that you have placed on remote servers.

20.4.1 Manual Teaming Database Update

In order to update the Novell Teaming 1.0 database when the Teaming Installation program cannot do it for you, you must run the Teaming 2.1 database update scripts on the database server.

  1. Stop Teaming.

  2. Change to the directory where the Teaming 2.1Installation program is located.

  3. Unzip the teaming-2.1.n-sql.zip file to create the update-1.0.0-2.0.n directory and the update-2.0.0-2.1.n directory.

    These directories contain update scripts for each type of database (MySQL, Microsoft SQL, and Oracle).

  4. Change to the update-1.0.0-2.0.n directory.

  5. Copy the update script for your database type to the server where the Teaming database is located.

  6. On the database server, use the database client utility for your database type to run the update script to convert the Teaming database structure from 1.0 to 2.0:

    MySQL:

    mysql -uusername -ppassword< /path/update-mysql.sql

    Microsoft SQL:

    osql -Uusername -Ppassword -i update-sqlserver.sql

    You can also use the script with the SQL Server Express Utility to update the database.

    Oracle:

    		 
    sqlplus "/ as sysdba"
SQL>spool update-oracle.out;
SQL>@update-oracle
SQL>quit;

  7. Return to directory where the Teaming 2.1 Installation program is located.

  8. Change to the update-2.0.0-2.1.n directory.

  9. Copy the update script for your database type to the server where the Teaming database is located.

    The update script for converting the database from 2.0 to 2.1 has the same name as the update script for converting from 1.0 to 2.0, so you overwrite the first update script when you copy the second update script to your database server.

  10. On the database server, use the client utility for your database type to run the update script to convert the Teaming database structure from 2.0 to 2.1.

  11. After you have updated the Teaming database to 2.1:

    (Conditional) If your Lucene Index Server is also on a remote server, continue with Section 20.4.2, Manual Lucene Index Server Update.

    or

    (Conditional) If all Teaming components that need to be updated are on the Teaming server, follow the instructions in Section 20.3, Updating a Single-Server Teaming System from 1.0 to 2.1.

20.4.2 Manual Lucene Index Server Update

In order to update your Novell Teaming index when the Teaming Installation program cannot do it for you, you need to run the Teaming 2.1 Remote Lucene Server Installation program.

The default location for the Lucene Index Server software has change from Teaming 1.0 to Teaming 2.1:

Linux:

Teaming 1.0:

/opt/icecore/luceneserver

Teaming 2.1:

/opt/novell/teaming/luceneserver

Windows:

Teaming 1.0:

c:\icecore\luceneserver

Teaming 2.1:

c:\Program Files\Novell\Teaming\luceneserver

You can update the Lucene Index Server software in its current Teaming 1.0 location or you can install to the new Teaming 2.1 default location.

The default location for the Lucene index has also changed from Teaming 1.0 to Teaming 2.1:

Linux:

Teaming 1.0:

/home/icecoredata/lucene

Teaming 2.1:

/var/opt/novell/teaming/lucene

Windows:

Teaming 1.0:

c:\home\icecoredata\lucene

Teaming 2.1:

c:\Novell\Teaming\lucene

Because you need to reindex your Teaming site after performing the update, the Teaming 2.1 Lucene index is created in the new default location.

  1. Stop Teaming.

  2. Stop the Lucene Index Server by using the following command in the directory where the Lucene Index Server is currently installed:

    Linux:

    ./indexserver-stop.sh

    Windows:

    indexserver-stop.bat

  3. Copy the Teaming 2.1 Remote Lucene Server Installation program and the Teaming 2.1 license file (license-key.xml) from the directory where the Teaming 2.1 Installation program is located to a convenient directory on the server where the remote Lucene Index Server is located.

    The name of the Remote Lucene Server Installation program varies by platform:

    Linux:

    lucene-installer.linux

    Windows:

    lucene-installer.exe

  4. Start the Remote Lucene Server Installation program.

  5. Accept the License Agreement, then click Next.

  6. Select Update software and settings to install to the current Teaming 1.0 location.

    or

    Select New installation to install to the new Teaming 2.1 location.

  7. Click Next to continue.

  8. Click Next to accept the installation location.

  9. Click Next to accept the Java JDK location.

  10. In the Host field, specify the hostname where you are installing the remote Lucene Index Server.

  11. Change Lucene configuration settings as needed, then click Next.

    For information about Lucene configuration settings, see Section 9.5.2, Changing Lucene Configuration Settings.

  12. Click Install to install the updated Lucene Index Server software.

  13. Click Finish when the update is completed.

  14. Start the Lucene Index Server.

    Linux:

    ./indexserver-startup.sh

    Windows:

    indexserver-startup.bat

  15. Now that all remote Teaming components have been updated, follow the instructions in Section 20.3, Updating a Single-Server Teaming System from 1.0 to 2.1.