Migrate Instances across Environments

Jet Analytics supports multiple environment deployments, allowing developers to maintain separate environments for development, testing, and production. Each environment contains its own set of instances that can be related to one another, and changes can be promoted from one environment to the next using instance migration.

Adding a new environment

Before adding environments, it is good practice to add your instances first. While instances can always be added or removed from environments later, including them at creation time saves time.

Instances not yet assigned to an environment appear in the Uncategorized Instances area of the Instances page.

Add a new environment

1. Navigate to Data Estate > Instances and click Add new environment.
2. Name the environment and select the instances to include.
3. Click Add.

Instances can also be added or removed using drag and drop. Hover over an instance to reveal the six-square drag handle on its left side, then drag the instance to the target environment.

Edit an environment

Click the edit icon on an environment to open the edit menu. Select the environment to edit — the form is identical to the creation form, with the title updated to Edit environment.

Delete an environment

Click the delete icon, select the environment to remove, and click Delete Environment. Instances previously assigned to the deleted environment move to the Uncategorized Instances area.

Migrate instances

Migrating an instance copies its metadata to a target instance of the same type, making the target a copy of the source. This is how changes are promoted through environments from development to production. Instances do not need to be in different environments to be migrated between them.

Note: You cannot migrate to an instance that has never been opened in Jet Analytics Data Integration. The metadata structure is created the first time an instance is opened, so the target instance must be opened at least once before migration.

Note: All instances must be upgraded to the current version before migrating. Open each instance in Jet Analytics Data Integration to apply any pending upgrades before attempting a migration.

To migrate an instance, navigate to Migrations inJet Analytics portal, click the arrow next to the source instance, and select the target instance.

The Jet Analytics Portal is managed by insightsoftware. Please contact Product Support for more information.

1. In the To field, select the destination instance. This step is the same for all instance types.

   

2. For Ingest instances: map each source data source connection to the corresponding target data source connection. This step migrates the configuration of data sources within the Ingest instance — such as table selections, primary key rules, and incremental load rules — but does not change the data source connection settings in the Portal.

   

3. For Prepare instances: map the source Ingest instance to the target Ingest instance.

   

4. For Deliver instances: map the endpoints.

   

5. Add a comment describing what is being migrated.
6. Review the summary of changes, then click Migrate.

The migration is added to the queue. The instance displays a progress indicator while the migration is running.

Note: When migrating to an Ingest instance, the Ingest Service must be restarted after the migration completes.

Note: Known issue: After migrating a Deliver instance, the tooltip displayed when hovering over a Deliver table in Jet Analytics Data Integration may not reflect the updated data. To resolve this, synchronise the Deliver instance with the Prepare instance. Even if there are no changes to synchronise, this operation refreshes the tooltip text.

Undo a migration (Prepare and Deliver)

When a Prepare or Deliver instance is migrated, a new version is created in the target instance containing the content from the source. If the migration needs to be undone, use the standard version history in Jet Analytics Data Integration to revert to a previous version:

1. In Jet Analytics Data Integration, right-click the target instance and select Open Version… to open the Select Version window.
2. Select the version to revert to and click OK.
3. Make a minor inconsequential change (such as renaming a table and then renaming it back) to mark the instance as having unsaved changes, then go to File > Save. A confirmation message will appear: "You are about to save an earlier version of the instance as the latest version."

   

Troubleshooting

Missing configuration when migrating instance

Ensure that both the source and target instances have matching mapped data source connections before proceeding with the migration.

Target instance has not been initialised when migrating instance

Open Jet Analytics Data Integration and open the target instance to initialise it. Then return to the Jet Analytics Portal and retry the migration.

The Jet Analytics Portal is managed by insightsoftware. Please contact Product Support for more information.