|UNIX: Upgrading EMu 3.0 to 3.1|
|EMu 3.1 Install/Upgrade Notes|
The upgrade from EMu Version 3.0 to EMu 3.1.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 ~emu is used to refer to the user emu's home directory. This is normally /home/emu.
Installing Texpress 8.1 is required for the first client upgraded to EMu 3.1 only. Once Texpress 8.1 has been installed this section may be skipped for subsequent upgrades.
Installing TexAPI is required for the first client upgraded to EMu 3.1 only. Once TexAPI has been installed this section may be skipped for subsequent upgrades.
Upgrading the EMu Server is required for each client installed on the server. The upgrade process updates all records on the system. The time to upgrade a client may be considerable for large data sets. Before commencing the upgrade it is worth investigating what record level security is required by the client, as this will affect the data updates.
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 EMu 3.0 to EMu 3.1 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-3-1-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-3-1-01.security script removes all history records from the upgraded tables. Standard KE EMu installations do not use the Texpress history facility so upgrading is safe. If an institution does use the history facility another update mechanism is required (eg. global edits from within the EMu client).
The script upgrade-3-1-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.
When upgrading to EMu 3.1 the Windows client must be installed on all client machines, including machines that had EMu 3.1 beta releases installed. To upgrade the EMu Client follow the Installing EMu Client notes.
|Last Updated on Monday, 15 March 2010 19:49|