How to Transport Changes between Environments

Aim of this article

Explains how to transfer changes done in one environment to another. For example, changes from DEV can go to QA, changes from QA go to PROD or in reverse.

In addition, you can select just specific entities for the transfer.

Related sections

Integrations Table Options (Reference Manual)

Required permissions

Integration Instance - Admin

Steps:

Go to Account > Integrations.
In the Integrations table select a specific IM instance.
From the row menu select Transport to.
1. Select Target Environment where the changes should be applied.
2. Select objects (Mappers, Connections, Filters,...) which should be transported.
  Click the Target environment button to check whether a connection used on Target environment has been created and create one, if needed.
  If there are encrypted properties, you will be prompted to enter a new value (otherwise they would become invalid in the new environment due to unique secret keys).
Select application properties you want to include in the transport.
Click the Transport button to trigger the creation of a merge request. The process can take several minutes.
When the transport is ready, you will be notified in Notifications.
Click the corresponding notification to view details. In this dialog you have the option to Deploy it.
Alternatively, you can invoke this dialog from the row menu of the IM instance – it is the option Resolve merge request.
The merge request status can be viewed in the Merge Requests section. You will also find there a link to Git where you can see more details about the merge request.

Note:

When a transport is in progress or it is ready, the option Transport to is not in the row menu (to avoid parallel transports).
When routes, mappers, filters and connections were selected for transport, it may be necessary to update some of them after the transport, so that your integration works at a different environment. Typically you need to adjust connection details – URL, user, password, etc.
If you need to use a manual workaround for this procedure, follow these steps: For each route and mapper, create a local copy. In Workspace, copy the route/mapper to other instance (QA, Prod, etc.). Go to the other instance (QA, Prod, etc.) and deploy the copied route/mapper from Workspace.