19.3 Updating a Multiple-Server Teaming System from 2.0 to 2.1

If your Novell Teaming 2.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.

19.3.1 Manual Teaming Database Update

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

  1. Stop Teaming.

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

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

    The update-2.0.0-2.1.n directory contains an update script for each type of database (MySQL, Microsoft SQL, and Oracle).

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

  5. Use the database client utility for your database type to run the script:

    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;

  6. After you have updated the Teaming database:

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

    or

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

19.3.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 Remote Lucene Server Installation program.

  1. Stop Teaming.

  2. Stop the Lucene Index Server.

  3. Copy the Teaming 2.1 Remote Lucene Server Installation program 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

    Because you are updating from Teaming 2.0, the existing license file (license-key.xml) on the remote Lucene server still works with the Teaming 2.1 Remote Lucene Server Installation program.

  4. Start the Teaming 2.1 Remote Lucene Server Installation program.

  5. Accept the License Agreement, then click Next.

  6. Select Update software and settings.

  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.

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