Exit Print View

Oracle Secure Global Desktop Installation Guide for Version 4.6

Document Information

Preface

1.  Installing SGD

2.  Upgrading SGD

Before You Upgrade

Upgrades and Early Access Program Software

Conditions for Upgrading

Before You Upgrade on Solaris OS Platforms

Upgrades and Your Existing Configuration

Upgrades and UNIX Audio

Performing the Upgrade

How to Upgrade a Fully Licensed Single-Server Array

How to Upgrade a Fully Licensed Multiple-Server Array

Upgrading a Customized SGD Installation

Upgrading Customized SGD Web Server Files

Upgrading Customized SGD Server Files

Upgrading Other SGD Components

How to Upgrade the SGD Enhancement Module for Microsoft Windows

How to Upgrade the SGD Enhancement Module for UNIX and Linux Platforms

How to Upgrade the SGD Client Automatically

How to Upgrade the SGD Client Manually

How to Upgrade the SGD Gateway

3.  Getting Started With SGD

4.  Removing SGD

Performing the Upgrade

How you upgrade SGD depends on whether you are upgrading a single-server or multiple-server array. If you have customized SGD, you might have to upgrade your customized files manually.

How to Upgrade a Fully Licensed Single-Server Array

  1. Make sure no user sessions and application sessions are running in the array, including suspended sessions.
  2. Upgrade the server by installing the new version of SGD.

How to Upgrade a Fully Licensed Multiple-Server Array

Before You Begin

All SGD servers in a multiple-server array must run on the same version of the SGD software. This means that to upgrade an array, you must dismantle the array, upgrade each server independently, and then rebuild the array.

  1. Make sure no user sessions and application sessions are running in the array, including suspended sessions.
  2. Dismantle the array.

    On the primary SGD server, detach the secondary SGD servers from the array:

    # tarantella array detach --secondary server

    Detach only one secondary SGD server at a time. After making the change to the structure of the array, wait until SGD has copied the change to all the SGD servers in the array before making any further changes. Run the tarantella status command on the primary SGD server to check the status of the array.

    When a secondary SGD server is detached from an array, it loses its license keys and, temporarily, you might not be able to log in to SGD on this host.

  3. Upgrade the primary SGD server by installing the new version of the software.
  4. Upgrade the secondary SGD servers by installing the new version of the software.
  5. Rebuild the array.

    The clocks on all SGD servers must be in synchronization. If the time difference is more than one minute, the array join operation will fail.

    On the primary SGD server, add the secondary SGD servers to the array:

    # tarantella array join --secondary server

    Add only one secondary SGD server at a time. After making the change to the structure of the array, wait until SGD has copied the change to all the SGD servers in the array before making any further changes. Run the tarantella status command on the primary SGD server to check the status of the array.

    When a secondary SGD server is added to an array, it gains any license keys installed on the primary SGD server.

Upgrading a Customized SGD Installation

When you upgrade, the SGD installation program preserves the customized files it finds, but it does not upgrade them. These files have to be manually upgraded. Two sets of files might need to be upgraded:

Two types of customized files might need attention after you have upgraded:

Upgrading Customized SGD Web Server Files

When you upgrade, the SGD installation program backs up any customized SGD web server files it detects. Backed-up files and their locations are listed in the /opt/tarantella/var/log/webservercustomized.list log file.

To upgrade the customized files, use utilities such as diff and patch to compare and merge the differences between the backed-up files and the files in the standard SGD installation.

The SGD installation program copies any bespoke SGD web server files it finds into the new installation. These files are not changed.

Upgrading Customized SGD Server Files

When you upgrade, the SGD installation program backs up the customized and bespoke SGD server files it detects and produces the following log files:

Use these log files to identify the files that need to be manually upgraded.

How to Manually Upgrade Customized SGD Server Files

  1. Create a copy of the customized file.
  2. Identify the changes made between SGD versions.

    The customizedchanged.list log file lists the customized files that have to be manually upgraded. For each file listed in this log file, your system will have three versions of the file:

    • The old, customized version in one of the following directories:

      • /opt/tarantella/var/serverresources.oldversion for login scripts.

      • /opt/tarantella/etc/data.oldversion for other files such as color maps.

    • The old, uncustomized version in the /opt/tarantella/etc/templates.oldversion directory.

    • The new, uncustomized version in the /opt/tarantella/etc/templates directory.

    Use a utility such as diff to compare the old, uncustomized file with the new, uncustomized file. This highlights the changes made between SGD versions.

  3. Apply the changes to the customized file.

    Use a utility such as patch to apply the changes identified in Step 2 to the copy of your customized file.

  4. Copy the upgraded customized file into the correct location in the new SGD installation.

How to Manually Upgrade Bespoke SGD Server Files

  1. Create a copy of the bespoke file.
  2. Identify the changes made between SGD versions.

    The docrootjava.log and customized.list log files list the bespoke files that might have to be manually upgraded.

    The only way to upgrade bespoke files is to compare versions of the standard SGD files to identify changes that have taken place and then apply those changes to your bespoke files.

    Use a utility such as diff to compare the old, uncustomized file with the new, uncustomized file. This highlights the changes made between SGD versions.

    To identify the changes, compare the following files:

    • The old version of the standard SGD files in the /opt/tarantella/etc/templates.oldversion directory.

    • The new version of the standard SGD files in the /opt/tarantella/etc/templates directory.

  3. Apply the changes to the bespoke file.

    Use a utility such as patch to apply the changes identified in Step 2 to the copy of your bespoke file.

  4. Copy the upgraded bespoke file into the correct location in the new SGD installation.