19.4 Updating a Multiple-Server Teaming Site

If your Novell Teaming 1.0 system is distributed across multiple servers, the Teaming 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.4.1 Remote Teaming Database

In order to update the Novell Teaming database when it is not located on the Teaming server, you must run the Teaming 2.0 database update script.

  1. Stop Teaming.

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

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

    The update-1.0.0-2.0.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 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.4.2, Remote Lucene Index Server.

    or

    (Conditional) If all Teaming components that need to be updated are on the Teaming server, follow the instructions in Section 19.3, Updating a Single-Server Teaming Site.

19.4.2 Remote Lucene Index Server

In order to update your Novell Teaming index when the Lucene Indexing Server is not located on the Teaming server, you need to run the Remote Lucene Server Installation program.

The default location for a remote Lucene index has changed between Teaming 1.0 and Teaming 2.0.

Teaming 1.0:

/opt/icecore/luceneserver

Teaming 2.0:

/opt/novell/teaming/luceneserver

Because you need to reindex your Teaming site after performing the update in any case, you can update the Lucene Index Server software in its current location (/opt/icecore/luceneserver) or you can install to the new default location (/opt/novell/teaming/luceneserver).

  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 Remote Lucene Server Installation program and the Teaming license file (license-key.xml) from the directory where the Teaming 2.0 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 location.

    or

    Select New installation to install to the new 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 19.3, Updating a Single-Server Teaming Site.