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

Before You Upgrade

This section describes the things you must know and do before upgrading.

Upgrades and Early Access Program Software

Upgrades to, or upgrades from, Early Access Program (EAP) software releases of SGD are not supported. EAP software releases must always be a fresh installation.

Conditions for Upgrading

The supported upgrade paths to this version of SGD are listed in the Oracle Secure Global Desktop 4.6 Platform Support and Release Notes available at http://docs.sun.com/app/docs/doc/821-1928.

If you want to upgrade from any other version of SGD contact Oracle Support.

If you are sure you want to perform an unsupported upgrade, you must create an empty file /opt/tarantella/var/UPGRADE before installing the new version of the software. Your SGD installation might not be upgraded correctly.

Before You Upgrade on Solaris OS Platforms

When you upgrade on Solaris Operating System (Solaris OS) platforms, the pkgadd command performs several checks and asks you to confirm the changes before installing the package. You can create an administration file that instructs pkgadd to bypass these checks and install the package without user confirmation.

To avoid user interaction, the administration file must contain the following lines:

conflict=nocheck
instance=unique

When you upgrade SGD, use the pkgadd -a adminfile command to specify the administration file.

If you do not specify an administration file when you upgrade, the SGD installation program creates one for you and gives you the option to quit the installation so that you can run the pkgadd command again with the -a adminfile option.

Upgrades and Your Existing Configuration

When you upgrade, the following changes are applied to your existing configuration:

Upgrades and UNIX Audio

Following an upgrade, if you want to use audio for X applications you must also upgrade the SGD Enhancement Module on your UNIX or Linux platform application servers. See How to Upgrade the SGD Enhancement Module for UNIX and Linux Platforms for upgrade instructions.

UNIX audio services might not work correctly if the versions of SGD and SGD Enhancement Module are different.