Icon

04.3_​Orchestration

04.3 Orchestration_solution
ExercisesAll the tasks can be found in the yellow annotations and the yellow components.Execute 04.0_Reset_DB&Big_Data_Environment before running this workflow 1 Call ETL on Customers data workflow and importits final status1. In the Credentials Configuration component, provide the username andpassword to the webservice, Amazon S3, and PostgreSQL database. NOTE. If you parameters (hostname, database name, port) are differentfrom the default ones, update them in the PostgreSQL Connector nodes inthe called workflows.2. Call the workflow 04.1_ETL_Customers and import its final status (CallWorkflow Service node) - Browse the workflow or provide the path manually - Auto-adjust the ports - Connect the Credentials Configuration component to the input flowvariable port 2 Call ELT on Usage data if ETL on Customers data executedsuccessfully1. Build an automated construction that will control whether to execute 04.2_ELT_Usage (CASE SwitchStart node, flow variable ports). Use ETL_failed variable to control which port is active2. Call the workflow 04.2_ELT_Usage and import its final status (Call Workflow Service node) - Browse the workflow or provide the path manually - Auto-adjust the ports - Connect the first output port of the CASE Switch Start node with the input flow variable port Session 4 OrchestrationExercise 04.3 Orchestration ETL_failed = 0: executethe next workflowETL_failed = 1: stopExecute04.2_ELT_Usageand import its statusExecute04.1_ETL_Customersand import its statusCredentialsConfiguration CASE Switch Start Call WorkflowService Call WorkflowService ExercisesAll the tasks can be found in the yellow annotations and the yellow components.Execute 04.0_Reset_DB&Big_Data_Environment before running this workflow 1 Call ETL on Customers data workflow and importits final status1. In the Credentials Configuration component, provide the username andpassword to the webservice, Amazon S3, and PostgreSQL database. NOTE. If you parameters (hostname, database name, port) are differentfrom the default ones, update them in the PostgreSQL Connector nodes inthe called workflows.2. Call the workflow 04.1_ETL_Customers and import its final status (CallWorkflow Service node) - Browse the workflow or provide the path manually - Auto-adjust the ports - Connect the Credentials Configuration component to the input flowvariable port 2 Call ELT on Usage data if ETL on Customers data executedsuccessfully1. Build an automated construction that will control whether to execute 04.2_ELT_Usage (CASE SwitchStart node, flow variable ports). Use ETL_failed variable to control which port is active2. Call the workflow 04.2_ELT_Usage and import its final status (Call Workflow Service node) - Browse the workflow or provide the path manually - Auto-adjust the ports - Connect the first output port of the CASE Switch Start node with the input flow variable port Session 4 OrchestrationExercise 04.3 Orchestration ETL_failed = 0: executethe next workflowETL_failed = 1: stopExecute04.2_ELT_Usageand import its statusExecute04.1_ETL_Customersand import its statusCredentialsConfiguration CASE Switch Start Call WorkflowService Call WorkflowService

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: Lada.Rudnitckaia
Created at: 2021-10-14
On NodePit since: 2022-11-12
Last update: 2024-11-21
Created with KNIME version: v4.5.2
Tags: Best practicesData engineerData engineeringEducationorchestrationworkflow dependenciesworkflow service

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!