Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

This page will guide you through the process of migrating from a Kiuwan On-Premises single-container installation carried out with the deprecated installation tool docker-for-kiuwan.

Migration process

Step 1: upgrade your single-container installation

First of all, you will need to upgrade your current installation to the latest available. A complete upgrade (both Kiuwan and clients) will be needed.

...

Once the upgrade is completed, you should see this versions in the KOP system administration console:

 
 

Step 2: stop the old Kiuwan On-Premises server

First, make sure there are no running analysis before stopping the application server. You can check this in the sysadmin console:

...

Code Block
languagebash
docker exec -it [kiuwan_on_premise_container_name] /bin/bash
supervisorctl stop wildfly
exit

Step 3: backup your data

Now that the application server is stopped but not the container itself, you can access the MySQL server and persistent volume to backup your data.

...

  • $DIR_PERSISTENT_VOLUME/$KIUWAN_HOST/KiuwanCentralWorkingDirectory
  • $DIR_PERSISTENT_VOLUME/$KIUWAN_HOST/repos/kiuwanSourceCodeRepository

Step 4: install a new Kiuwan On-Premises using the new installer tool (kiuwan-cluster)

Follow the steps provided in the Kiuwan On-Premises Installation Guide to prepare the new installation of Kiuwan On-Premises, but do NOT perform the installation step (that may be executing install.sh or other scripts depending on your installation needs).

...

If it is mandatory for you to use the same machine to install the new Kiuwan On-Premises, please make sure no persistent volume paths collide.

Step 5: restore the repository data

To restore the repository data into the new persistent volumes, copy the persistent volume backup to these folders:

  1. KiuwanCentralWorkingDirectory should be copied to [VOLUMES_DIR]/data-shared/repos/kiuwanCentralRepository 
  2. kiuwanSourceCodeRepository should be copied to [VOLUMES_DIR]/data-shared/repos/kiuwanSourceCodeRepository 

Step 6: start new Kiuwan On-Premises infrastructure

Execute these commands to create and start the new Kiuwan On-Premises infrastructure:

Code Block
languagebash
cd [INSTALL_DIR]/docker
sudo ./create-network.sh
sudo ./install-infrastructure.sh
sudo ./start-infrastructure.sh

Step 7: restore the database

Restore the MySQL backup, either using mysqldump or MySQL Workbench restore utility (import from self-contained file is recommended).

...

Code Block
languagesql
UPDATE opt_cinc.INFRA_TENANT_METADATA SET connectionUrls = '[MYSQL_HOST]:[MYSQL_PORT]' WHERE tenantId <> '0';

Step 8: complete the migration process

This last step forces Kiuwan On-Premises to update to the current version (the one tied to the used kiuwan-cluster distribution). Execute in your new Kiuwan host console:

Code Block
languagebash
echo "2.8.1904.8" > [VOLUMES_DIR]/data-shared/publicData/current.version
cd [INSTALL_DIR]/docker
sudo ./update.sh
sudo ./start-kiuwan.sh

Step 9: check your data and discard the old installation

Once the Kiuwan On-Premises servers are up, you can access your new installation using the same username and password and all the previous data will be there.

...