Configuring Orchestration Stage
In the Orchestration stage, legacy scheduler scripts are transformed into modern scheduler tools. Scheduler scripts contain scheduling logic such as AutoSys JIL files which will be transformed into modern scheduler tools such as Databricks Workflows. Double-click the Orchestration stage to access the configuration page.
In this Topic:
Overview
In this section, you can customize the Orchestration stage’s name and give a suitable description as required. By default, Orchestration is provided in the Name field. Provide a relevant name and description that helps you to understand the purpose and scope of the Orchestration stage.
Transform
In this section, you can define the source and target along with the source files. The Orchestration stage transforms legacy orchestration scripts into modern scheduler tools such as Databricks Workflows. It employs pattern-based intelligent transformation to transform legacy scheduling logic and produces its target-native equivalent.
To configure the Orchestration stage, follow the below steps:
- In Source Type, select the scheduler script type such as AutoSys.
- In Orchestration Script, upload the scheduler scripts.
- In Target Type, select a modern scheduler tool such as Airflow, Databricks, or Amazon MWAA.
- Click Save to save the Orchestration stage. When the stage is successfully saved, the system displays an alerting snackbar pop-up to notify the success message.
- Click to execute the integrated or standalone pipeline. Clicking (Execute) navigates you to the pipeline listing page which shows your pipeline status as Running state. It changes its state to Success when it is completed successfully.
- Click on your pipeline card to see reports.
To view the Orchestration Stage report, visit Orchestration Report.
Output
The output of this transformation is the converted scheduler script into the target-native equivalent. A comprehensive report is generated as an output of this pipeline.
You can configure the output of this transformation for navigation to a further stage. By default, the output configuration is set to Error if the transformation is not 100%, or that can be configured to Continue, Stop, or Pause as required.