Secure Global Desktop Administration Guide > Getting started > Upgrading a customized Secure Global Desktop installation

Upgrading a customized Secure Global Desktop installation

When you upgrade your version of Secure Global Desktop, Secure Global Desktop Setup will preserve your existing configuration, but it does not upgrade any customized files.

There are two types of customized files that may need attention after you have upgraded:

• Customized files - these are files found in a standard Secure Global Desktop installation which have been changed by an Administrator, for example by adapting standard webtop themes or Expect scripts.
• Bespoke files - these are files your organization has created and added to a Secure Global Desktop installation, for example your own webtop themes and Expect scripts.

Note This page assumes that you are familiar with the directories in the Secure Global Desktop installation directory. By default, this is /opt/tarantella.

What happens during the upgrade

During installation, Secure Global Desktop Setup creates a backup of all customized files, including login scripts, by moving the standard Secure Global Desktop files in the following directories (and the subdirectories within them):

• var/docroot
  
  moved to var/docroot.oldversionnumber.
• var/serverresources/expect
  
  moved to var/serverresources/expect.oldversionnumber.
• etc/data
  
  moved to etc/data.oldversionnumber.
• etc/templates
  
  moved to etc/templates.oldversionnumber.

This means that immediately after an upgrade, your customizations will not be active. These customizations need to be manually upgraded.

Secure Global Desktop Setup leaves bespoke files in their current location and does not attempt to upgrade them. These files need to be manually upgraded.

Finding your customized and bespoke files

During the upgrade, if Secure Global Desktop Setup detects that you have customized and/or bespoke files, you will see a message that says four log files have been produced:

• var/log/upgraded.files
  
  This is a summary of the changes.
• var/log/customized.list
  
  This is a list of any files that the Administrator has edited or added.
• var/log/customizedchanged.list
  
  This is a list of any files that the Administrator has edited which have been changed by the upgrade.
• var/log/docrootjava.log
  
  This is a list of new or modified Java™ technology files from the original installation that Secure Global Desktop Setup has saved.

You can use these log files to identify the customized and/or bespoke files that need to be manually upgraded.

Manually upgrading customized files

The customizedchanged.list log file lists the customized files that may have to be manually upgraded.

For each file listed in this log file, there will be three versions of the file held on your system:

• the old, customized version, backed up in the var/docroot.oldversionnumber directory;
• the old, uncustomized version, in the etc/templates.oldversionnumber directory; and
• the new, uncustomized version, in the etc/templates directory.

To upgrade your customized files:

• Create a copy of your customized files from the var/docroot.oldversionnumber directory.
• Use a utility such as diff to compare the file in the etc/templates.oldversionnumber directory with the file in the etc/templates directory. This will highlight the changes that have been made between Secure Global Desktop versions.
• Use a utility such as patch to apply the same changes to your copy of your customized files.
• Copy the upgraded customized files into the correct location under var/docroot.

Manually upgrading bespoke files

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

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

To identify the changes, you need to compare:

• the old version of the standard Secure Global Desktop files in the etc/templates.oldversionnumber directory; and
• the new version of the standard Secure Global Desktop files in the etc/templates directory.

Use a utility such as diff to compare the files in these directories. This will highlight the changes that have been made between Secure Global Desktop versions. Apply these changes to your bespoke files, for example by using a utility such as patch.

Note if you have bespoke Expect scripts and you do not upgrade them, you must turn off security for X displays on the array-wide Security panel in Array Manager.

Copyright © 1997-2005 Sun Microsystems, Inc. All rights reserved.