Note

This document is designed to be read by a competent system manager and it is generally recommended that upgrading for the first time should be undertaken with Caliach assistance.

Caliach Vision: Upgrading for Server Installations and Other Tips

Introduction: PC Installation

Normal installation of Omnis Studio and Caliach Vision on a desktop PC leads to a straightforward, repeatable and easily supported file structure.

Typically, under Windows, Omnis Studio will install into Program Files (e.g. C:\Program Files\RainingData\OS33 RT), and Vision installs into C:\Vision. Desktop and Start Menu shortcut items are usually created, to execute Omnis Studio and open Caliach Vision from these locations. The Vision help is automatically installed to the Help directory of the Omnis Studio installation selected as the default during installation.

To use this directory structure on desktop PCs, while accessing the data across a network, you only have to point individual Vision application libraries at the shared datafile in a directory on a file server.

At upgrade time, the main PC on the network can be upgraded directly from the CD, and the entire installation repeated or copied on to each user desktop PC. A small modification to shortcuts may be necessary to point to a new installation of Omnis Studio, unless a runtime sub-directory has been embedded into the Vision directory, as is usually recommended during initial Caliach Ltd installation.

Introduction: Server installations

However, as indicated in the Reference Book and on-line help (see Introduction -- Installation of Caliach Vision on a Network), the system can also operate in a "server" installation, where only the minimum directories and files are installed on the desktop PCs, with a single copy of the rest residing on the server alongside the main datafile. While this can increase network traffic, maintenance and upgrades are simplified, as long as upgrading procedures are suitably amended. This document seeks to clarify some of those amendments, and provide additional tips for the upgrade process. It must be read in conjunction with the appropriate upgrading help topic.

Note - For Windows Thin-Client environments (e.g. Windows Terminal Services or Citrix Metaframe), the minimal "desktop PC" installation normally in C\Vision is instead located in say, C:\Documents and Settings\All Users\UserName(s)\Vision on the application server. Network traffic is vastly reduced with this type of installation, and apart from the path change above, management is the same as for a standard server installation.

Changes for Server Installations

The main point to be aware of here is that a CD-based installer can only accommodate installations where a known directory structure exists on a desktop PC. Therefore the first step is to re-create a single desktop PC installation on the machine to be upgraded first (from here on called the "master PC").

The master PC equivalent in a Windows thin-client environment (from here on called the "master installation") will typically be the initial installation on the server, in C:\Vision. The overall process can be described as follows: -

Tip - For Windows Thin-Client installations it is probably worth running the master installation connected to the main datafile briefly just before upgrade, to make sure that the local Vision application library is updated by the latest ProgCode.upt maintenance release in the main database directory. This installation may not have been used, as it is usually installed on the server.

  1. Copy the shared Vision directories from the server back to the master PC or installation, even if the originals are still there from initial installation - the server files will have been used in preference to local ones, so will be the current set.
  2. Connect to a training datafile in the local data directory on the master PC or installation, and carry out the upgrade as described in the Upgrade Notes accompanying the release.
  3. Once all your custom features are re-enabled in the new version, ensure all users are off the system and your datafile is backed up, copy all the new shared directories back to the main datafile directory, and copy the new updated Vision application library to all desktop PCs, (or user directories for a Windows thin-client installation).
  4. Connect to the main datafile and allow the data to be upgraded, before backing up again and re-connecting other users.

General Upgrading Tips

Before Upgrading -

  1. Try and arrange it so that upgrading is carried out after routine data integrity maintenance and any archiving is carried out. For example, do any period routines, check A/R and A/P control analysis, G/L balances, that relatives are re-united, process quantities checked, etc..
  2. Advise all users to archive their current window layout (File/Advanced/Environment - Windows tab pane), so they can be restored after upgrade.
  3. Ensure that all customisation is up to date in both the master OpenVision.lbs library and both copies of your ProgCode.usa (in the master Custom directory and datafile directory.
  4. Don't forget to save any customised strings to your ProgCode.usa as well as custom program classes.
  5. Document any file class changes and remove modified file classes from your ProgCode.usa - they will not be usable after upgrade, and must NOT be copied to your new OpenVision.lbs (see below...).
  6. Document any language changes made using the Localisation function, and make sure they are saved to the Translate.df1 file.
  7. Discard the existing ProgCode.upt file - it will not be applicable to the new version.

During Upgrading -

  1. Upgrade Omnis Studio and any associated patches first, copying the contents of the new runtime directory to an "embedded" Omnis directory if you use one (see above).
  2. Before upgrading Caliach Vision, make sure you are not running it!
  3. Make sure you apply the latest maintenance release for the new version before connecting to your data - some fixes may be to data upgrading routines.
  4. Remember that the help will be installed into the Help directory of the Omnis Studio you specify during installation (if there is more than one) - if this is not the only one you intend to use, you must copy the "vision" help directory created within the Omnis "help" directory to other installations.
  5. Any file class modifications must be re-made in the new OpenVision.lbs and propagated using the Change Management System (CMS) class mover before connecting to your main datafile (see above...).
  6. Do NOT copy your old oCustom1 object class from your ProgCode.usa to the new OpenVision.lbs - you must use the oCustom1 code transfer tool in the CMS class mover to apply your custom code to the NEW oCustom1 in OpenVision.lbs, and then save the modified object class back to your ProgCode.usa using the CMS class mover, before copying to the data directory. A good tip here is to check that your code changes have been applied in OpenVision.lbs after using the tool, and then delete the oCustom1 object class in your CMS data file before copying it back - this way you can be certain that it is the new modified class that will be used.
  7. Don't forget to import any customised strings, and also apply language changes to the new version before propagation.