WOZTERM UPGRADES

Wozterm upgrades configuration and help files when "Upgrade Wozterm" is selected from the Start Menu. This allows the regularly modified files to be upgraded without a full Radia rollout. This section describes the upgrade process.

Upgrading Wozterm

Upgrading Wozterm is very simple, thanks to Upgrade functionality re-used from the Ozterm Startup Scripts. An upgrade is dependant on two things – a reference to the file being upgraded existing in Upgrade.ini, and the file to be upgraded existing on the Upgrade Server as specified in Upgrade.ini.

When making changes to Wozterm Upgrades it is very important to follow the two steps below, in order.

Begin by placing the file to be upgraded onto the FTP Server. Currently our server is quhno200.nto.telecom.com.au. For access to this server please contact John Cavendish. Please specify that you must be placed into the “wozterm” unix group. Note that all upgrades should be monitored / approved by Nick Roots – effects of upgrades are nation-wide.

Wozterm files live in /home/wozterm/upgrade. They should be stored as they would be found under the Wozterm install directory. That is, a file that lives in "c:\program files\wozterm\scripts" should be FTP’d to "/home/wozterm/upgrade/scripts".

The second step in performing an upgrade is the modification of the upgrade.ini file. If the file to be upgraded is already listed in the upgrade.ini, no changes need to be made – the upgrade will occur when users begin a Wozterm Upgrade. If the file is not listed (explicitly or as part of a wildcard), it needs to be included in the appropriate Section. The sections are self explanatory – enter the file details as required under [CopyAlways], [CopyIfNewer] or [CopyIfNotExist].

Notes regarding format used by the upgrade.ini filelist sections:

• Key = Relative File/Folder Path from the Application Dir
• Value = Relative File(s) Path from the Upgrade Dir
• Wildcards (*) can be used in the Value only. If a Wildcard is used a Directory MUST be supplied as the Key
• Environment variables in the format %ENV_VAR_NAME% will be replaced by their current environment value

When changes are saved to the upgrade.ini file on the server, changes will take effect.

It is worth noting that although any file may be upgraded using the upgrade process, file size should be take into account. A 1MB file being copied to 10,000 desktops from one file-server will cause the server to be overwhelmed, and eventually 10GB+ of network traffic.

Example upgrade.ini

;This section is for configuration options - no Upgrade Files are defined here
[Config]
UpgradeHost=139.168.19.79
UpgradeDir=Wozterm


;Those files that will overwrite any existing version - including those that are newer.
[CopyAlways]

;Exchange List
scripts\NE.csv=scripts\NE.csv


;Those files that will only overwrite if the upgrade file is newer than the current file.
;IF UNSURE USE THIS SECTION
[CopyIfNewer]

;Wozterm Registered Scripts
scripts\connect.cmd=scripts\connect.cmd

;Wozterm HTML Help
help=help\*
help\images=help\images\*
help\wozterm=help\wozterm\*
help\wozterm\usermanual=help\wozterm\usermanual\*
help\wozterm\usermanual\images=help\wozterm\usermanual\images\*
help\wozterm\usermanual\tutorials=help\wozterm\usermanual\tutorials\*
help\wozterm\vbautomation=help\wozterm\vbautomation\*
help\wozterm\vbautomation\images=help\wozterm\vbautomation\images\*


;Those files that will only overwrite if the current file doesn't exist.
[CopyIfNotExist]