Introduction

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.
Before proceeding with the update please ensure that a complete backup of the KE EMu server exists and is restorable.

There are four main components that require upgrading:

• Texpress (the database engine)
• TexAPI (web services)
• EMu Server (the application)
• EMu Client (the client)

The notes below detail how to upgrade all systems. Check the Releases table for Client specific notes.  Upgrading comprises the following steps:

• Stopping EMu services
• Installing Texpress
• Upgrading TexAPI
• Upgrading EMu Server
• Starting EMu services
• Upgrading EMu Client

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.

Requirements

• Texpress 8.1.001 or later.
• TexAPI 3.1.010 or later.
• EMu Server 3.1.01
• EMu Client 3.1.01

Stopping EMu services

1. Log in as emu
2. Enter client client
3. Enter emuweb  stop
4. Enter emuload  stop

Installing Texpress

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.

1. Enter cd  ~emu/texpress
2. Enter mkdir  -p  8.1.xxx/install where xxx is the version of Texpress being installed.
3. Enter cd  8.1.xxx/install
4. Obtain the appropriate Texpress version for your Unix machine via the KE Texpress hyperlink above. Save the release in ~emu/texpress/8.1.xxx/install calling it texpress.sh.
5. Enter sh  texpress.sh. The Texpress release will be extracted.
6. Enter .  ./.profile
7. Enter bin/texinstall  ~emu/texpress/8.1.xxx (expand the ~emu).
   The Texpress installation script will commence.
8. Enter cd  ~emu/texpress/8.1.xxx
9. Enter .  ./.profile
10. Enter texbldperms
11. Enter bin/texlicinfo. Obtain your Texpress licence code and place it in a file called .licence.
12. Enter bin/texlicset  <  .licence to install the licence.
13. Enter \rm  -fr  install
14. Enter cd  ~emu/texpress
15. Enter ln  -s  8.1.xxx  8.1

Upgrading TexAPI

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.

1. Enter cd  ~emu/texpress
2. Enter mkdir  3.1.xxx where xxx is the version of TexAPI being installed.
3. Obtain the appropriate TexAPI version for your Unix machine via the KE TexAPI hyperlink above.
   Save the release in ~emu/texpress calling it texapi.sh.
4. Enter sh  texapi.sh  -i  ~emu/texpress/3.1.xxx (expand the ~emu).
5. Enter \rm  -f  texapi
6. Enter ln  -s  3.1.xxx  texapi
7. Enter \rm  -f  texapi.sh

Upgrading EMu Server

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.

1. Enter cd  ~emu/client
2. Enter mkdir  install
3. Enter cd  install
4. Obtain the appropriate EMu version via the KE EMu Server hyperlink above.
   Save the release in ~emu/client/install calling it emu.sh.
5. Enter sh  emu.sh. The EMu release will be extracted.
6. Enter .  ./.profile
7. Enter bin/emuinstall  client. The EMu installation script will commence.
8. Enter cd  ~emu/client
9. Enter cp  .profile.parent  ../.profile
10. Enter .  ../.profile
11. Enter client client
12. Enter emureindex  -p eregistry
13. Enter emuload  stop
14. Enter emuweb  stop
15. Enter emubldlinks
16. Enter \rm  -fr  install

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.

1. Enter vi  .profile-local and add the Texpress options to the file. An example file is:
   TEXPRESSOPTS="${TEXPRESSOPTS} dateorder=mdy dateformat='dd MMM yyyy'"
   export TEXPRESSOPTS
2. Enter client  client
3. Any other client specific setting can be set at this time (eg shell specific settings, etc).

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.

1. The client will now be upgraded to EMu 3.1. If you are upgrading from a version prior to EMu 3.0.06 you must run the upgrade scripts sequentially for all versions after the old version before running the EMu 3.1 upgrade.
2. Enter emusecurity
3. Enter upgrade-3-1-01
4. Enter upgrade-3-1-01.security (may take some time)
5. This next step must, without exception, reindex every table. A reindex is required even if the table does not contain any records. Also if any table contains a data/tablename/emuoptions file which has the line:
   REINDEX=no
   then you must temporarily set the value to yes or comment out that line prior to running the emureindex command.
   Enter emureindex  -f  -p (may take some time)
6. Enter upgrade-3-1-01.tabs

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.

Starting EMu services

1. Enter emuload  start
2. Enter emuweb  start
3. Enter exit to close the command shell.
4. Log out.

Upgrading EMu Client

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.