Control-M for Databases Plug-in Migration Tool
The Control-M for Databases Plug-in Migration Tool converts the Control-M for Databases plug-in to Control-M for Snowflake.
Migrating Control-M for Databases to Control-M for Snowflake
This procedure describes how to migrate the Control-M for Databases plug-in to Control-M for Snowflake plug-in.
Before You Begin
-
Install Control-M for Snowflake and create a connection profile.
Begin
-
Download the Control-M Migration Tool for Integrations from EPD.
-
Extract the downloaded files into a temporary directory.
-
Export the workspace with Control-M for Databases jobs to a JSON file, as described in Exporting a Workspace.
-
Edit the configuration file with the following steps:
-
Navigate to the Control-M Migration Tool for Integrations directory that you downloaded.
-
Open the migration_configuration_file.json in a text editor.
-
Add the job type, connection profiles, and hosts that you want to convert. See Configuration File Parameters.
-
-
Do one of the following to run the migration tool:
-
Windows: Run the following command:
plugins_migration_tool.exe -i <Exported_Workspace_Pathname> -c <Migration_Configuration_File_Pathname> -o <Output_File_Pathname>
For more information, see Control-M Migration Tool Parameters.
-
UNIX: Do the following:
-
Run the following command to ensure the migration tool has execution permissions:
chmod +x plugins_migration_tool
-
Run the following command:
./plugins_migration_tool -i <Exported_Workspace_Pathname> -c <Migration_Configuration_File_Pathname> -o <Output_File_Pathname>
For more information, see Control-M Migration Tool Parameters.
-
-
-
Import the output file with the updated job definitions, as described in Importing a Workspace.
Configuration File Parameters
Control-M Migration Tool for Integrations contains the migration_configuration_file.json file that instructs the Control-M Migration Tool how to handle the different job types in the exported JSON file.
You must edit the configuration file with the job type, connection profiles, and hosts that you want to convert. The Control-M Migration Tool only converts the job types, connection profiles, or hosts that you define in the configuration file.
The following example shows a configuration file to migrate the original Control-M for Databases to Control-M for Snowflake:
[
{
"Type": "Job:Database",
"ConnectionProfile": "{Databases1:Snowflake1},{Databases2:Snowflake2}",
"Host": "{Databases_Host1:Snowflake_Agent1},{Databases_Host2:Snowflake_Agent2}",
"Database": "{*:Database_Name}",
"Schema": "{*:Schema_Name}"
}
]
The following table describes the migration_configuration_file.json file parameters.
|
Parameter |
Description |
|---|---|
|
Type |
Determines the Control-M for Databases job type to convert. |
|
ConnectionProfile |
Maps the connection profiles of the original Control-M for Databases plug-in to the connection profiles of the Control-M for Snowflake plug-in. The following example maps the Control-M for Databases plug-in to the Control-M for Snowflake connection profiles: "{Databases1:Snowflake1},{Database2:Snowflake2}" You can include an asterisk (*) as a wildcard. "{*:Snowflake}" instructs the tool to convert all connection profiles listed in the exported JSON file to an Snowflake connection profile. |
|
Host |
Maps the Agents associated with the Control-M for Databases plug-in to the Agents associated with the Control-M for Snowflake plug-in. The following example maps the Control-M for Databases plug-in to the Snowflake hosts:
You can include an asterisk (*) as a wildcard. "{*:Snowflake_Agent_1}" instructs the tool to convert all Agents listed in the exported JSON file to an Agent associated with the Control-M for Snowflake plug-in. |
|
Database |
Determines the Snowflake database that the Control-M for Snowflake job uses. |
|
Schema |
Determines the database schema that the Control-M for Snowflake job uses. |
Control-M Migration Tool Parameters
The following table describes the migration tool parameters.
|
Parameter |
Description |
|---|---|
|
-i |
Defines the input file pathname. The input file is the exported workspace in JSON format. |
|
-c |
Defines the configuration file that instructs the Control-M Migration Tool how to handle the different job types in the input file. The migration_configuration_file.json file is downloaded with the Control-M Migration Tool. |
|
-o |
(Optional) Defines the path to the file with the converted job definitions. If you do not specify an output file, the Control-M Migration Tool creates the migration_output_file.json file as a default output file. |
