21.3 Updating a Multiple-Server System from Vibe 3.2 to Vibe 3.3

If your Novell Vibe 3.2 system is distributed across multiple servers, the Vibe 3.3 installation program can update Vibe components on the Vibe server, but you must manually update any Vibe components that you have placed on remote servers.

21.3.1 Backing Up Vibe Data

Ensure that your Vibe data is backed up before you begin the update process. For information about the data that needs to be backed up, see Backing Up Vibe Data in the Novell Vibe 3.4 Administration Guide.

21.3.2 Manual Vibe Database Update

To update a database from Vibe 3.2 to 3.3, you must run the Vibe 3.3 database update script.

  1. Stop Vibe.

  2. Ensure that no application (such as a command prompt or Windows Explorer) is running on the Vibe 3.2 system.

  3. Change to the directory where the Vibe 3.3 installation program is located.

  4. Unzip the teaming-3.3.n-sql.zip file to create the update-3.2.0-3.3.n directory.

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

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

  6. (Conditional) If you have multiple Oracle databases, you must edit the update-oracle.sql script and add @database_name to the first line of the script. For example, connect sitescape/sitescape@vibe.

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

  8. After you have updated the database from Vibe 3.2 to Vibe 3.3:

    If your Lucene Index Server is also on a remote server, continue with Section 21.3.3, Remote Lucene Index Server Update.

    or

    If all remaining components that need to be updated from Vibe 3.2 to Vibe 3.3 are on the Vibe server, follow the instructions in Section 21.2, Updating a Single-Server System from Vibe 3.2 to Vibe 3.3.

21.3.3 Remote Lucene Index Server Update

To update your index from Novell Vibe 3.2 to Novell Vibe 3.3 when the Vibe installation program cannot do it for you, you need to run the Remote Lucene Server installation program.

  1. Stop Vibe.

  2. Stop the Lucene Index Server.

  3. Ensure that no application (such as a command prompt or Windows Explorer) is running on the Vibe 3.2 system.

  4. Copy the Vibe 3.3 Remote Lucene Server Installation program from the directory where the Vibe 3.3 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

  5. Start the Vibe 3.3 Remote Lucene Server installation program.

  6. Accept the License Agreement, then click Next.

  7. Select Update software and settings.

  8. Click Next to continue.

  9. Click Next to accept the installation location.

  10. Click Next to accept the Java JDK location.

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

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

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

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

  14. Click Finish when the update is completed.

  15. Start the Lucene Index Server.

  16. Now that all remote Vibe components have been updated, follow the instructions in Section 21.2, Updating a Single-Server System from Vibe 3.2 to Vibe 3.3.