| Unix: Upgrading Vitalware 1.4 to 2.0 |
|
| Vitalware 2.0 Install/Upgrade Notes |
IntroductionThe upgrade from Vitalware Version 1.4 to Vitalware 2.0.01 involves a number of steps. Please follow the instructions below carefully. You cannot skip any steps under any circumstances. There are four main components that require upgrading:
The notes below detail how to upgrade all systems. Check the Releases table for Client specific notes. Upgrading comprises the following steps:
In the notes below client refers to the name of the client directory for the current installation. The term ~vw is used to refer to the user vw's home directory. This is normally /home/vw. Requirements
Stopping Vitalware services
Installing TexpressInstalling Texpress 8.1 is only required for the first client upgraded to Vitalware 2.0. Once Texpress 8.1 has been installed this section may be skipped for subsequent upgrades.
Upgrading TexAPIInstalling TexAPI is only required for the first client upgraded to Vitalware 2.0. Once TexAPI has been installed this section may be skipped for subsequent upgrades.
Upgrading Vitalware Server
In order to allow easier upgrades of Texpress (without having to update the etc/opts file) all Texpress options are now set in the client specific .profile-local file. When upgrading from Vitalware 1.4 to Vitalware 2.0 you will have to add all Texpress options from the Texpress 8.0 installation. In particular the dateorder, dateformat, timeformat, latitudeformat, longitudeformat, tmppath and loadmemory settings should be noted. Please see Texpress options for a list of acceptable values.
Now that the client is installed the upgrade process can take place. The steps below may take some time to complete on large data sets.
The script upgrade-2-0-01.security sets the default record level security values. The default settings allow Everyone to Display, Edit and Delete records, subject to normal operational privileges. Some institutions may want to alter the default security upgrade to take advantage of their security model. If the default security upgrade is not required, custom built upgrade scripts must be produced to set the base security values. The upgrade-2-0-01.security script removes all history records from the upgraded tables. Standard Vitalware installations do not use the Texpress history facility so upgrading is safe. If an institution does use the history facility (TT & QLD?) another update mechanism is required (e.g. global edits from within the Vitalware client). The script upgrade-2-0-01.tabs adds the Security tab immediately prior to the Admin tab. If the Security tab is to be hidden from users, the appropriate tab switching entries must be modified after performing the upgrade. Starting Vitalware services
Upgrading Vitalware ClientWhen upgrading to Vitalware 2.0 the Windows client must be installed on all client machines. To upgrade the Vitalware Client follow the Installing Vitalware Client notes. |
| Mise à jour le Lundi, 15 Mars 2010 |