Remote Flows¶

Remote flow is an integration flow that is created and can be managed in the cloud, and needs to be exported to be deployed and run on-premise.

You can use remote flows to transfer data to the cloud when the data source in the local environment can not be directly accessed the cloud due to data security or network restrictions, etc.

After Creating Flows, the following operations can be performed:

Remote flows have the following features:

Deploying and Running On-premise

The flow can be exported as a JAR and deployed to the executable environment such as SCADA systems and local servers.

Monitoring and Triggering in the Cloud

The online/offline status of the flow can be monitored remotely, and you can update the status by triggering the flow via nodes.

By dragging and dropping nodes with different functions in remote flows, you can implement various operations. For example:

Receive trigger commands from cloud or servers: Receive commands from the cloud via Remote Task or from HTTP servers via HTTP Server.
Publish data to the 3rd-party server: Publish data to 3rd-party servers via AMQP Pub, MQTT Pub, Kafka Pub, HTTP Client, or SFTP Client.
Pre-process data on-premise: Compress or discompress data via Compress, and convert data format via CSV or Script.
Catch exceptions and resume at breakpoint: Catch exceptions via Catch and upload the caches via Checkpoint.