The Migration tool allows users to quickly and easily send Matillion ETL resources from one Matillion Instance to another.
The Migrate menu can be reached via the main Project menu from within the Matillion ETL client: Project → Migrate.
From Migrate, users can select resources from their (source) Matillion ETL instance and send them to a target Matillion ETL instance in a similar manner to the Import and Export functions in the v1 API. This approach, unlike the API, can be used to move many resources at once and indeed clone an entire instance.
- No resources are destroyed during migration. Migrating a resource essentially clones it to the target instance.
- Your network administrator must ensure that the target Matillion ETL server allows incoming TCP/IP connections from the source Matillion ETL server.
Configuring a Migration
The Migration menu requires the following configuration:
- Destination URL: The URL (including Port Number, if appropriate) of the target Matillion ETL Instance. This can be an IP address and should be preceded by http:// or https://where appropriate.
- Username: The username to log into the target Matillion ETL instance, as made necessary by that instance's User Configuration.
- Password: The password to log into the target Matillion ETL instance, as made necessary by that instance's User Configuration.
- Please ensure that the target instance is running a version of Matillion ETL that is at identical or newer than the version on the source instance. Both instances should be hosted on the same platform and using the same Database service.
- Permissions still apply as usual to both the source user and target user. For example, if the target instance user does not have permission to write Shared Jobs, then they cannot be used to import Shared Jobs via the Migration tool. See documentation on Permissions for more information on how these are set.
Resources to be migrated must be clicked and marked with a tick. When a box is selected, it marks everything (that is not already ticked) preceding it in the tree structure with a dash. The dash shows resources that are not to be migrated but must exist for the checked resources to be migrated properly. For example, if a single Job is included, the Version, Project and Project Group are marked as they must exist in the target instance for the Job to be migrated. Thus, it is not possible to migrate a Job from the source to a different place (e.g. a different Project) in the target.
When the configuration is complete and you have checked all resources to be migrated, click OK to attempt the migration. If the migration is unsuccessful, an error message will be displayed and the the user will have the opportunity to click Back to return to the previous screen with its configuration intact. Errors with longer messages can be seen in full using the ellipsis button to the right.
The following resources can be migrated using the Migrate function:
- API Profiles
- Manage Change Data Capture (CDC)
- Project Groups
- Shared Jobs
The following resources cannot be migrated using the Migrate function:
- (Enterprise only) Groups and granular Permissions
- LDAP setup/User Configuration
- Imported drivers/Drivers that are not included with the product
- Custom Python packages
- Backend Configuration changes (For example: Emerald.properties file)
- Any custom files/certificates
- GIT Configuration
- Customizations to built-in API Profiles