You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »


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.

Please follow the steps shown in Kiuwan On-Premises Installation Guide in order to upgrade.

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


Step 2: stop Kiuwan

To stop the running Kiuwan and prevent creating more data before backuping it up, run this commands in the Kiuwan on premise host. Make sure there are no running analysis before stopping the application server:

docker exec -it [kiuwan_on_premise_container_name] /bin/bash
supervisorctl stop wildfly

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.

Using mysqldump or MySQL Workbench (using self-contained file is recommended), backup these schemas data and structure:

  • opt_activity
  • opt_cinc
  • opt_insight
  • opt_metamodel
  • opt_qmm
  • opt_transaction

Access your persisten volume and backup central and source code repositories, located in:

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

Step 4: install Kiuwan on premises using the new installer tool (kiuwan-cluster)

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

We recommend using a new host(s) machine(s), so the old installation does not interfere in any way.

If it is mandatory for you to use the same machine to install the new Kiuwan on premise, 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 Kiuwan infrastructure

Execute these commands to create and start the new Kiuwan on premise infrastructure:

cd [INSTALL_DIR]/docker
sudo ./
sudo ./
sudo ./

Step 7: restore the database

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

You should connect to the MySQL server provided or the one you have installed if you chose to externalize this service.

After restoring the backup, execute this script to update the connection settings stored in the database. Remember to replace:

  • [MYSQL_HOST] with your MySQL server host.
  • [MYSQL_PORT] with your MySQL server port.
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 be updated to the current version (the one tied to the used kiuwan-cluster distribution). Execute in your new Kiuwan host console:

echo "2.8.1904.8" > [VOLUMES_DIR]/data-shared/publicData/current.version
cd [INSTALL_DIR]/docker
sudo ./
sudo ./
  • No labels