When the variable Migration can be used to move jobs and their associated Connectors, Repositories, Authenticators, and Agents from one system to another (Test to Production)
Exporting jobs
-
From the Job Management screen, select one or multiple jobs.
-
Click Export Checked Jobs to export the jobs to a JSON file.
Changing System URL
During the migration process, a repositories URL must be changed from the test environment to the production environment, so it is imported into the target system properly. Follow the steps below to change the System URL:
-
Open the exported JSON file in a tool that supports editing JSON
-
At the top of the file is a section of systems. This is a unique list of systems for the associated jobs being migrated.
For example,
To change a systems URL during migration, edit the associated systemURL.
Do not change any other fields within the system or the file or it could corrupt the import.
Importing Jobs
-
From the Job Management screen, click Import Jobs
-
Browse for the JSON file and click Open to import the file to the UI.
To import jobs that use SQL Connectors, do the following:
-
If the target environment has the same Agent queue name and Database user/password, the JSON file can be imported. The Agent and authenticators are created first and then the Repository.
-
If the target environment has different Agent queue name, you must pre-create the same Agent in the Connect UI using the same name that exists in the import file.
-
If the target environment has different Database user/password, you must pre-create an authenticator with the same name that exists in the import file. The import will re-use the existing authenticator with proper credentials.
-