You are viewing an old version of this page. View the current version.
This section provides information that you may need to follow in case you are upgrading one of these specific versions (seesection if you want to check which version is installed in your company):
|Kiuwan On-Premises version||Specific upgrade process needed||Apache load balancer optional changes|
Added health check for Kiuwan front instances
Added new error pages
Added kiuwanDomain variable to ease configuration
Removed unneeded modules
|2.8.1910.4||OPTIONAL||Added ProxyPreserveHost On directive|
Upgrading from version 2.8.1910.1
If you have currently installed Kiuwan On-Premises version 2.8.1910.1, you will need to follow this guide in order to adapt your Kiuwan On-Premises infrastructure to the latest version.
Due to changes in how Redis Cluster is created through the installation process, in order to keep your installation up to date with the latest infrastructure you will need to follow a different approach to perform a full upgrade from this version.
You will need both the kiuwan-cluster version you used to install 2.8.1910.1 and the latest available kiuwan-cluster (that can be downloaded here https://static.kiuwan.com/download/onpremise/kiuwan-cluster.tar.gz). We will refer to this locations:
- [INSTALLER_DIR_OLD]: where the old kiuwan-cluster version was untared.
- [INSTALLER_DIR]: where the new kiuwan-cluster version has been untared.
Note that if you are using AWS elasticache service to run Redis Cluster services you can ignore this section and follow the standard upgrade process.
Step 1: wait for all enqueued analyses to end
Make sure there are no running analyses before continuing to the next step. You can check this in the System Administration Console:
- Access Kiuwan On-Premises with sysadmin user.
- Access the Analysis Administration option in the upper right dropdown menu.
- Click on the "Active analyses" button and check if the table shows any running or pending analysis.
If you are using an automation tool to launch Kiuwan analyses, make sure you pause the needed jobs so no more analyses enter your Kiuwan On-Premises queues.
Once there are no more active analyses, you should wait for the pending analyses to be completely freed before stopping the Kiuwan server. This should take up to 30 minutes maximum.
Step 2: stop kiuwan services
Change the current directory to the old kiuwan-cluster docker scripts and stop all the Kiuwan On-Premises services:
This will stop all Kiuwan frontal, analyzer and schedulers containers currently running.
Step 3: update your current configuration
In order to update the current Kiuwan On-Premises clients and your volumes global configuration file, you should run the update script located in the new kiuwan-cluster:
Step 4: stop remaining containers and prune
Pruning containers is needed to safely upgrade from this version. To do so, run the uninstall.sh script from the new kiuwan-cluster installation directory.
Note that this step will NOT remove any data from your current installation:
Step 5: clean Redis cluster data
Redis Cluster current data must be cleaned up in order to start a new fresh cluster. Run the following command:
Step 6: update Redis cluster node information
Redis Cluster default configuration has been changed in the following versions of Kiuwan On-Premises. If you are running the provided service you will need to update the Redis Cluster nodes locations.
Edit the global configuration file:
You must change properties "redis.cache.nodes" and "redis.store.nodes" to these values:
Step 7: update your configuration
If you need to update any other configuration property, you can modify now any other configuration option. Changes will be taken into account when Kiuwan services are started in the next steps.
Please refer to Upgrading from versions prior to 2.8.1910.7 for details on how to modify your mail server configuration.
Step 8: run the install script for the new version
Running the installation script will recreate the new Redis Cluster and start all needed services:
Step 9: continue with full upgrade steps
You can now continue with the standard full upgrade process just where you left it: Step 8: load balancer manual configuration (optional).
Upgrading from versions prior to 2.8.1910.7
Configuration changes were made to how the mail server is configured starting from version 2.8.1910.7. If you made manual changes in the Wildfly instances configuration to support TLS/SSL/plaintext based email servers, you must update your mail server configuration.
- Edit the file [VOLUMES_DIR]/config-shared/globalConfig/globalConfig.properties
- Look for the following properties:
- Follow the instuctions found in the comments of each property or refer to Mail server configuration examples for details on how to set the value of each property.
- No labels