Skip to main content
Feedback

Migrating Configuration Data 5.x → 6.1.0 / 6.2.0

Migrating the configuration data to Local Edition 6.1.0 / 6.2.0 is a two-step procedure. It is applicable when migrating the configuration data from the Local Edition versions 5.3.x, 5.4.x, 5.5.x, and 5.6.x.

  1. Exporting the configuration data to an SQL file.

  2. Importing the SQL file to the Local Edition database.

Exporting the Data to an SQL File

Procedure

  1. Log in to the migration-container in the migration-pod. Update default with the namespace used by Boomi Cloud API Management – Local Edition 5.x, and then run the following command:

    kubectl exec -it migration-pod --namespace default -- /bin/bash

  2. To export the configuration data, run the following script:

    migrate.py --export_config

Importing the SQL File to 6.1.0 / 6.2.0 Database

Procedure

  1. Log in to the migration-container in the migration-pod. Update default with the namespace used by Boomi Cloud API Management – Local Edition 5.x, and then run the following command:

    kubectl exec -it migration-pod --namespace default -- /bin/bash
    note

    It is recommended to run the following command in the screen shell so that even if the migration pod shell times out, configuration import will not be affected.

    To install the screen shell in the migration pod, run the following command:

    apt-get install screen -y

  2. To import the configuration data to the Boomi Cloud API Management – Local Edition 6.1.0 / 6.2.0 database, run the following command:

    migrate.py --import_config

Updating Date and Timezone

Boomi Cloud API Management – Local Edition 5.x uses the America/Los Angeles timezone. It is updated to UTC in Boomi Cloud API Management – Local Edition 6.1.0 / 6.2.0.

Procedure

  1. Log in to the migration-container in the migration-pod. Update default with the namespace used by Boomi Cloud API Management – Local Edition 5.x, and then run the following command:

    kubectl exec -it migration-pod --namespace default -- /bin/bash

  2. To update the date and time in the configuration data, run the following command:

    migrate.py --update_timezone
On this Page