Client software upgrade

Depending on the volume and location of end users, you can update the iBase client software on a machine-by-machine basis, or deploy it across a network using Windows Installer and enterprise systems management software.

Whichever method you use to deploy the client software, the following actions need to be performed.

Backing up client data

There are a number of files that are deployed with the iBase client and may have been modified by end users. When the upgrade occurs, these will be overwritten with the later default versions. A full list of the files that may be affected can be found in Client file types. If these files have been modified, you must back them up before the upgrade takes place.

Upgrading the client software

iBase clients are only compatible with the database that they were released with or later versions. When the backup of client data is complete, you can begin the update of client software.
Note:
  • You must upgrade your iBase databases before you upgrade iBase clients
  • iBase Designer does not support backward compatibility. You should only use it with databases that have been upgraded. Users of iBase Designer should upgrade their installed software at the same time as the databases are upgraded.

Merging the client data changes

When the upgrade is complete, you will need to restore any client data that was included in the backup process to the client system.

You can copy the following files directly from the backup:
  • WSExclude.txt
  • FTExclude.txt
  • i2.wor
  • i2.apr
You must merge the following files from the backup with the new versions of each file:
  • commandgroups.mdb
  • iconlist.txt
  • i2.mxd
For each of the above files:
  1. Open the new version.
  2. Merge in your changes.
  3. Save the file in the installed location.

Upgrading the iBase Scheduler

In order to allow the scheduler to interact with clients that have been upgraded, you must also update iBase Scheduler. This method will retain all scheduler history in the Scheduler database:
  1. Stop the Scheduler service.
  2. Upgrade iBase on the machine running the Scheduler service.
  3. Restart the Scheduler service.