Upgrades and Early Access Program Software
Before You Upgrade on Solaris OS Platforms
Upgrades and Your Existing Configuration
How to Upgrade a Fully Licensed Single-Server Array
How to Upgrade a Fully Licensed Multiple-Server Array
Upgrading a Customized SGD Installation
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 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.
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.
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.
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.
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:
SGD web server files – Web application files and files used to configure the SGD web server
SGD server files – Files used by the SGD server, such as login scripts
Two types of customized files might need attention after you have upgraded:
Customized files – Files found in a standard SGD installation that have been changed by an SGD Administrator
Bespoke files – Files your organization created and added to an SGD installation
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.
When you upgrade, the SGD installation program backs up the customized and bespoke SGD server files it detects and produces the following log files:
/opt/tarantella/var/log/upgraded.files – A summary of the changes
/opt/tarantella/var/log/customized.list – A list of any files that an Administrator has edited or added
/opt/tarantella/var/log/customizedchanged.list – A list of any files that an Administrator has edited that were changed by the upgrade
/opt/tarantella/var/log/docrootjava.log – A list of new or modified Java technology files from the original installation
Use these log files to identify the files that need to be manually upgraded.
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.
Use a utility such as patch to apply the changes identified in Step 2
to the copy of your customized file.
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.
Use a utility such as patch to apply the changes identified in Step 2 to the copy of your bespoke file.