This repository contains "Conversion Rules" code samples created for various Schedulers, Applications and Homegrown's tools.
You can use those code examples to convert from those tools to Control-M using the Control-M Self-Conversion or as an example
for creating conversion rules using Groovy and Control-M Self Conversion API.
For more information on Control-M Self Conversion, see Control-M Self Conversion and the Control-M Self Conversion API online documentation.
For Control-M Self Conversion Training Video click Here.
For more information on Helix Control-M Self Conversion, see Helix Control-M Self Conversion and the Helix Control-M Self Conversion API online documentation.
To download the latest Control-M Self Conversion:
- Go to: https://control-m-conversion.s3.eu-central-1.amazonaws.com/Control-M_Conversions_for_DS/Index.html
- Download the Conversion Tool zip file
- Extract it
- Click SelfConversion.bat
To contribute, please follow these guidelines.
-
Every conversion and its associated files must be contained in its own folder. Name this folder as the name of the tool that you convert from.
-
The folder should contain:
- SampleData - A folder that holds tool sample Input Data in XML format that we want to convert to Control-M data.
- MappingLogic.xlsx - The mapping logic used for conversion in this sample, from the tool sample input data to Control-M data.
- ConversionRules.json - The tool Conversion Rules json file that contains the Self Converion rules code.
- ControlM_Result.xml - The Control-M data created by the Self Converion when converting the tool sample data using the Demo Tool conversion rules.
- HelixControlM_Result.json - The Helix Control-M data created by the Helix Control-M Self-Conversion when converting the tool sample data using the Demo Tool conversion rules.
-
Include a README.md file that explains the sample. A good description helps other community members to understand your sample. The README.md uses Github Flavored Markdown for formatting text.