Upgrading an Existing Quillix System
Click here to see this page in full context

Upgrading an Existing Quillix Capture Installation

Quillix Capture - Deprecated Versions

All versions of Quillix prior to and including version 4.4 have been deprecated and are no longer supported. While versions 4.5 and 4.6 are still supported, limited bug fixes are available due to the degradation of Internet Explorer and ActiveX technologies upon which these versions were built. Prevalent recommends updating to Quillix Capture version 5 in order to take advantages of new features and the additional security available using SSL with modern browsers.

Upgrading to Quillix Capture 5.x from version 4.x

The Quillix Installer will upgrade any Quillix System starting from version 4.0. To ensure a smooth upgrade, please take note of the upgrade prerequisites and special considerations noted below.

As with an upgrade of any software, it is strongly recommended that you back-up your existing Quillix database, as well as any files located in process data stores used by Batch Profiles or Document Types, before running the Installer.

Prerequisites

Before running the Installer to upgrade Quillix Capture, you should have the following:

  1. Login credentials for the Quillix Database
  2. Login credentials for the IIS Account (if not using Local System Account)
  3. File and directory permissions/credentials on the target installation computer
  4. Verify minimum system requirements are met as discussed in the System Requirements topic
  5. Obtain a new Quillix Capture 5 License File from Prevalent or your authorized Quillix vendor
  6. Create appropriate ODBC data sources for Quillix to use to connect to your Database Server.  Note, the Process Manager, Quillix Web, and the 32-bit Quillix Server require 32-bit ODBC data sources, while the 64-bit Quillix Server requires a 64-bit data source.  32-bit and 64-bit data sources must be created with the same names.

Note: Create only a 32-bit ODBC DSN when using the 32-bit version of Quillix Capture.  Create the 32-bit and 64-bit DSN when installing the 64-bit version of Quillix Capture.

Performing the Upgrade

Obtain either the 32-bit or 64-bit version of the Quillix Capture Installer, and run on the target computer.

Upgrading Quillix Capture from earlier 5.x versions

Upgrading Quillix Capture from version 5.x is straightforward and simple.  After performing a full system backup, run the Quillix Capture installer and follow the on-screen directions.

It is strongly recommended that you back-up your existing Quillix database and installation files, as well as any files located in process data stores used by Batch Profiles or Document Types, before running the Installer.

Prerequisites

Before running the Installer to upgrade Quillix Capture, you should have the following:

  1. Verify minimum system requirements are met as discussed in the System Requirements topic
  2. Create appropriate ODBC data sources for Quillix to use to connect to your Database Server.  Note, the Process Manager and 32-bit Quillix Server require 32-bit ODBC data sources, while the 64-bit Quillix Server requires a 64-bit data source.  32-bit and 64-bit data sources must be created with the same names.

Performing the Upgrade

Obtain either the 32-bit or 64-bit version of the Quillix Capture Installer, and run on the target computer.

Special Considerations

OLE DB No Longer Supported

Note: OLE DB is no longer supported as a database connection method for Quillix Capture. New ODBC data sources must be created in order to upgrade from a version of Quillix Capture older than version 5.3.  OLE DB is still supported for Web Client database lookups and the DBLookup QSX.

Changing Database Brand

Starting in version 5.3, Quillix Capture supports several new database brands such as MySQL and MariaDB.  It is important to note that the Quillix Installer will not migrate an existing Quillix Capture system from one database brand to another.  In order to run Quillix Capture 5.3 and higher on a non-SQL Server database, a new installation of Quillix Capture must be performed.

Web Client Files with Possible Custom Changes

The following Web Client files are backed up by the Quillix Installer to preserve any custom code, styles and settings that have been changed.  These files will be copied in their original locations with the extension of .bk and replaced with the newer version.  After installation, the changes in these files will need to be manually merged with the newer versions of the files in order for them to be recognized by the Web Client.

Service Errors in Web Client

See the troubleshooting topic Service Errors in Web Client for more information.

Desktop Shortcuts for Older Versions

Old desktop shortcuts (4.6 and older) for Server Manager no longer work.  Version 5 installs a new Process Manager executable, which may leave 4.6 and older desktop shortcuts and icons unusable. In this case, delete the old icons/shortcuts.

Web Database Lookups 4.4 and Older

If upgrading from 4.4 or older versions, and the Web Client Database Lookup has been used, LookupEncrypt.exe must be run.  All lookup connection strings are now stored encrypted.  Lookupencrypt.exe can be found in the Support folder where Quillix Capture has been installed.  Run this utility ONCE, then activate all Document Types and Batch Profiles as the utility updates the design tables only.

 Legacy Web Database Lookups

Any Database Lookups using legacy QWebDBPicklist or QWebLookup modules, or custom lookup or validation modules, need to be changed to use the ProgID of the module rather than the name of the WSDL.  For example, QWebLookup.IDataExtension should be used instead of QWebLookup.WSDL and QWebDBPicklist.IDataExtension should be used instead of QWebDBPicklist.WSDL.  Each Index Field has these settings under the Lookup/Validation settings category.

 

Related Topics: