Update of the IQ4docs System

Essentially, it makes sense to keep the IQ4docssystem up to date, i.e. to install new versions as soon as possible. The greater the time lag to the latest version (4.14), the higher the probability that manual adjustments will be required or that the update will have to be performed in several steps.

With a current service contract, you can update the system to the latest version at any time free of charge and benefit from new features and fixes, see also Change Log | Change overview.

All installed components are automatically updated by the Suite Installer during the update process. The package installers MongoDB and RabbitMQ are (as of version 4.9) excluded from this. These packages are not updated automatically because in most cases it is not necessary and, especially in a cluster installation, this causes an unnecessary interruption.

Licenses from version 4.1 or earlier are not compatible with newer versions. Contact your IQ4docs partner to update the license.

We recommend installing/updating the Embedded Client to match the version. However, a new version of the Embedded Client is not shipped with each release.

Update the Embedded Client (if necessary) on the devices and send the configuration to the device again (Set Up Device). You can show and check the Embedded Client version of the devices in the list view of the devices.

If there were no system areas in the version before the update, be sure to check if the system area was created correctly and if it was assigned to the devices correctly. If necessary, correct the information.

Starting with version 4.9, the database server is no longer created automatically during the update process of the Suite Installer. This is because new database servers usually have a different on-disk structure than the previous versions - to obtain this, the database must be backed up with the old database server and restored with the new database server. The new on-disk structure is generated automatically.

An update of the database server is not mandatory as IQ4docs 4.9 (and newer) also runs with DB server version 3.6.14.

Updating the database always requires a system downtime (even for cluster installations).

A possible procedure is described below.

  • Backup of the database.
  • Terminate all IIS services in the system.
  • Uninstall MongoDB (e.g. via Control Panel or Suite Installer).
  • Rename or delete the existing MongoDB installation directory (e.g. c:\IQ4docs\MongoDB).
  • Re-installation of MongoDB (e.g. via the Suite Installer, including establishing the cluster if necessary).
  • Restoration of the database.
  • Start all IIS services or restart the computer.

Starting with version 4.9, the RabbitMQ Message Broker is no longer updated automatically during the update process. The reason for this is to avoid version-dependent incompatibilities between RabbitMQ versions as well as cluster-operation downtimes.

If you want to update RabbitMQ, proceed as follows (in the case of a cluster installation, a downtime is unavoidable):

  • Uninstall RabbitMQ (e.g. using the Suite Installer of the currently installed version).
  • Restart the computer.
  • Delete the remaining RabbitMQ directory inside the IQ4docs installation directory.
  • Install RabbitMQ (e.g. via the Suite Installer, if necessary, establish the cluster).
  • After the reinstallation, restart the server.

Updating RabbitMQ requires a system downtime in any case (also for cluster installations).

If you have installed additional components, update them as well to the version delivered with the full installer.

  • IQ4docs Messenger

  • Local PrintService App

  • Client management

From time to time workflow modules are replaced by versions with more setting options or new modules. The old modules that still appear in the workflows continue to function, but are no longer present in the pool of workflows provided for use. Consequently, they cannot be used in workflows that need to be created or cannot be restored if they are deleted in an existing workflow.

These old modules should be replaced promptly with the new versions. You can recognize these modules by the fact that they are marked with a red exclamation point.