Upgrading from previous OL Connect versions
Users of OL Connect prior to 2022
Users of any version of OL Connect prior to 2022 should see the page Pre-existing User Data for information about exactly what data is saved or deleted.
Users of OL Connect prior to 2019.1
Users of OL Connect versions prior to 2019.1 should note that Update Client 1.2.40 is a prerequisite for both OL Connect 2019.1 and Connect Workflow 2019.1 installations. Only Update Client 1.2.40 has the capacity to upgrade the OL Connect license to the newer format that is required by the installers of those products.
If you do not have Update Client version 1.2.40 installed already, then the next time you run your Update Client it will show that there is an update available of itself to Version 1.2.40 (or later).
Simply click on the “Install” icon to initiate the upgrade.
For further details on how to upgrade the Update Client and update your Connect License see the Update Client 1.2.40 Upgrade Guide.
Note: An incomplete uninstall of OL Connect before a reinstall or upgrade to a newer version can lead to issues. See Issue after erroneous or incomplete update or re-installation.
Before you upgrade
Always backup before upgrading
It is recommended that you always backup your existing OL Connect preferences before upgrading to a new version. This will enable you to revert back to the previous version, in a worst case scenario in which the new version introduces issues with your existing production processes. Whilst the probability of such a worst case scenario is remote, it cannot hurt to take some simple precautions, just in case.
For instructions on how to do so, please see Backup existing OL Connect version.
Note: The scheduling settings were changed significantly in version 2019.2. Please make sure to record your current scheduling settings for reference before proceeding with an upgrade..
Recommendations
Before embarking on an upgrade, also follow these recommendations:
-
Prior to updating your production environment, all updates to OL Connect/Workflow should be performed in a development & test environment. This is both to test the upgrade process and to test that your solution is still working as expected. Having a development & test environment minimizes the risk of failure and business impact.
-
Planning the upgrade:
-
Perform the upgrade of your production server during off-peak hours when it least impacts business.
-
Prepare a rollback plan appropriate to your organization, which includes provisions for reverting in the case of catastrophic errors. This can be as simple as reverting to a snapshot or may be more involved on physical hardware.
-
Anticipate at least 1 hour of downtime to provide enough time for the installation and any rollback plan.
-
-
Consult the System requirements and Installation prerequisites before the upgrade to ensure that your environment is supported. If not, upgrading is not recommended.
-
When possible, disable your antivirus and anti-malware software during the upgrade process. If it is not allowed by the security policies, please consider configuring the proper exceptions:
-
Antivirus Exclusions (OL Connect
-
-
Read the OL Connect Release Notes . They provide information regarding enhancements in that release version (known issues, bug fixes, enhancements, new features, etc.)