Skip to main content
Feedback

Migrating 5.x → 6.1.0 / 6.2.0 (applies to v6.1.0+)

Deployment Mode

The following sections specify the steps required to migrate from Boomi Cloud API Management – Local Edition 5.x to 6.1.0 / 6.2.0.

The following deployment modes are available:

  • from untethered to untethered mode
  • from tethered to tethered mode

To export and import API utility, consider the following:

  • Export API data from Boomi Cloud API Management – Local Edition 5.x cluster via V3 API.
  • Import API data to Boomi Cloud API Management – Local Edition 6.1.0 / 6.2.0 cluster via V3 API.

Before you begin

  • Take a backup of your existing database used by Boomi Cloud API Management – Local Edition 6.1.0 / 6.2.0 before migration. You can restore the database from this backup in case of any adverse situation.

  • Get the migration package.

  • To extract the migration package, run the following command:

    tar xvf migrate_5x_to_6.tar.gz

Procedure

  1. Customizing Migration Configuration.

  2. 5.x → 6.1.0 / 6.2.0 Migration Container Build.

  3. 5.x → 6.1.0 / 6.2.0 Push Migration Container Images.

  4. Deploy Migration Pod - 5.x Cluster.

  5. Migrating Configuration Data 5.x → 6.1.0 / 6.2.0.

  6. Migrating Tokens 5.x → 6.1.0 / 6.2.0

  7. Migrating CMS data.

What to do next (After Migration)

Full Reload

Do a full reload of the memory cache in Boomi Cloud API Management – Local Edition 6.1.0 / 6.2.0.

kubectl create job --from=cronjob/loader-job-full manual-full-apimload-job

Undeploy Migration Pod in 5.x Cluster

Undeploy the migration pod in the cluster of the Local Edition versions 5.x cluster.

In the extracted migration package folder, run the following command:

./undeploy_migration.sh

The migration pod, persistent volume, configuration maps, and secrets are removed from Boomi Cloud API Management – Local Edition 5.x versions.

On this Page