Minor-Version Update Notes
Notes and additional information about upgrading from a major version to a minor version, or updating from a minor version to another minor version; for example, 8.4.1 to 8.4.22 or 2018.0.1 to 2018.0.3.
Table of Contents
- Checking for version-specific steps
- Common upgrade errors
- Summary of version-specific steps for version 8.4x
If you're updating from a major or micro version to a later micro update—for example, version 8.4.1 to 8.4.22—it's important to follow through the entire upgrade procedure. Even though it's a micro-release, it's important that you don't miss any steps. Be sure to:
- Check for version-specific steps: see Checking for version-specific steps.
- Review common errors and make sure you don't skip those steps: see Common upgrade errors.
Checking for version-specific steps
In some cases, upgrading to a specific micro-version might require an additional step that isn't part of the core upgrade process, such as a specific configuration task.
In defining the upgrade process you're going to follow, check for information in these two places:
- The main upgrade instructions for the main version you're upgrading to:
- Version 2018.0.x: Upgrading Akana API Platform from Version 8.4x to Version 2018.0.x
- Version 8.4x: Upgrading Akana API Platform from Version 8.2 to Version 8.4x
- Release notes for the micro version you're upgrading to: Check for any additional upgrade steps that might be covered in the release notes for the specific micro version. Release notes are available with the product ZIP files on the Rogue Wave Support Center (https://library.roguewave.com). You can also find this information in Summary of version-specific steps for version 8.4x below.
Common upgrade errors
Here are some reminders for specific tasks that are part of the standard upgrade process but are sometimes forgotten, either in a major or minor upgrade, causing problems with the installation. The instructions below are for upgrade to version 8.4x:
- When upgrading existing containers: Forgetting to delete the configuration cache file. See Step 2-5: Clear Configurator cache (if needed).
- Setting up the update.properties file correctly for the version, if you're using Silent Upgrade mode. See Upgrade container to Akana API Platform 8.4 (silent upgrade) (this is part of Step 2-6: Upgrade container).
- When upgrading existing containers: Clear browser cache before launching the upgraded Akana Administration Console. If you don't clear the browser cache and refresh, you won't see the user interface changes included in the update (if any). See Step 2-10: Clear browser cache.
- When upgrading existing containers: After upgrade, turn scheduled jobs back on. Part of the upgrade process is turning off the scheduled jobs; but it's important to turn them back on afterwards (simple.scheduler.enabled and org.quartz.scheduler.enable properties both set to true). This step must be run on one container that's connected to the database. Refer to the following steps in the upgrade documentation:
Summary of version-specific steps for version 8.4.x
Version 8.4 includes the following version-specific steps shown below. If you're upgrading from a version before to a version after any of the below items, be sure to include that step in your upgrade process.
|This version...||Included the following specific upgrade step...|
Version 8.4.6 includes an optional JRE update required for the platform's support of a specific HSM device.
The version of the Java Runtime Environment (JRE) that the platform uses was upgraded to version 1.8.0_144. This was needed for the platform’s support of the Thales HSM NCipher security provider.
Two additional steps: