Summary

The main purpose of the manual upgrade process is to migrate data from the previous version of YSoft SafeQ 5 to a newer blank Dispatcher Paragon version if the automatic upgrade run from the installer fails or it is necessary to upgrade to the new server. It is divided into the particular steps that are run in order, and each next step depends on the previous one. For details see chapter The YSoft SafeQ 5 to Dispatcher Paragon Upgrade Tool.

See the general summary of upgrading for more information.

If there are ORS servers or the YSoft SafeQ 5 installation runs in a cluster, see Upgrading a YSoft SafeQ 5 Cluster Server Installation with a Non-trivial Environment Setup on how to upgrade them and how to upgrade more servers in a cluster in general.

Prerequisites

For details, see chapter General prerequisites.

In the case of a SQL Server database dedicated to YSoft SafeQ 5, a database must exist on the same database machine as the future Dispatcher Paragon database machine. It is possible to install Dispatcher Paragon onto a dedicated database and restore the database from YSoft SafeQ 5 installation there.

In the case of SQL Server, the YSoft SafeQ 5 database has a different collation than SQL_Latin1_General_CP1250_CI_AS, which is the default. Please create the Dispatcher Paragon database manually with the same database collation as YSoft SafeQ 5.

Preparation of the Environment

1. Check that all prerequisites all fulfilled.
2. In case of an embedded database, create a backup of the YSoft SafeQ 5 database (this backup will be imported to the same database where Dispatcher Paragon will be installed).
3. Install Dispatcher Paragon with the server installer on the same server where YSoft SafeQ 5 CML is installed. (It is also possible to install Dispatcher Paragon to a new environment but the Upgrade Tool must be obtained from the existing Dispatcher Paragon installation or support team directly).
   1. The installer will install the new Dispatcher Paragon Management Service and Spooler Controller into the new directory. The local Spooler Controller must be installed (it is part of the server installer) if the original YSoft SafeQ 5 installation does not have an ORS group set up.

   2. The installer will start the newly registered services and the Dispatcher Paragon will be up and running.

      1. Activate Dispatcher Paragon Management Service with a valid and recent license. 
      2. Stop all Dispatcher Paragon services (except Bundled PostgreSQL if there is no dedicated database).
      3. In the case of an embedded database, restore the YSoft SafeQ 5 database backup onto the same database machine where Dispatcher Paragon is installed
      4. Configure the Upgrade Tool manually according to The YSoft SafeQ 5 to Dispatcher Paragon Upgrade Tool.

Checks Before Upgrading 

1. Verify access to both YSoft SafeQ 5 and Dispatcher Paragon databases.
   • In the case of an MSSQL dedicated database, verify both databases exist on the same database machine, and both databases have the same collation.
2. Check YSoft SafeQ 5 services are stopped.
3. Check Dispatcher Paragon services are stopped (except Dispatcher Paragon Bundled PostgreSQL if there is no dedicated database).
4. Check the YSoft SafeQ 5 RBE rules file (typically located at "c:\SafeQ 5\conf\rools.drl") is available. If not, copy the file from the existing YSoft SafeQ 5 installation to an available location.
5. Check the Upgrade Tool is properly configured (i.e., all paths included exist, database connections work, etc.) - see The YSoft SafeQ 5 to Dispatcher Paragon Upgrade Tool for how to configure the tool.

Running the Upgrade

1. Run the Upgrade Tool manually according to The YSoft SafeQ 5 to Dispatcher Paragon Upgrade Tool.

2. See the Upgrade Tool logs and report to see if all steps were successful.

   1. If the Upgrade Tool succeeds, all Dispatcher Paragon services can be run again, or the server should be restarted.

   2. If there is a warning as the Upgrade Tool result, it is strongly recommended to review the changes to adjust them to match your business requirements.

   3. If there is an error or an exception as the Upgrade Tool result, the errors must be investigated according to the previously mentioned Upgrade Tool documentation.

3. Ensure that all common-success-steps are done.
4. After the upgrade, the previous version of the YSoft SafeQ 5 is still in the system. It is possible to uninstall it manually (later) running the appropriate YSoft SafeQ 5 installer.

Common Steps after a Successful Upgrade

• Because of upgrade does not solve licensing of migrated devices and entities in general, there can be the notification that re-licensing of the product is necessary for Management Service notifications (after administrator signs in). Reactivation must be done within 10 days after upgrade otherwise the devices can be removed from the system. Also, devices will not work until reactivation because of technical limitations. See how to activate new license after upgrade.
• Check in general that migrated data are as expected.
• If Dispatcher Paragon manages printing devices, all device terminals must be reinstalled (use Devices > Printers > select all devices > Actions > Reinstall terminal). After re-installation check that devices working properly.

• • All Konica Minolta Embedded Terminals requires setting of "Terminal mode".
• System configuration properties which should be reverted to default values:
  • mpsJobSendFailed
  • mpsMailAuthenticationFailed
  • mpsMailDuplicateAddress
  • mpsMailFooter
  • mpsMailHeader
  • mpsMailSendFailed
  • mpsMailSendOk
  • rejected-email-text
  • ruleBasedEngineConfigurationProblemsEmailBody
  • ruleBasedEngineConfigurationProblemsEmailSubject
  • sslPortInfo
  • welcome-to-safeq-text