Working with Flow Runtimes
Use these scenarios to configure your IoT data to use an OCI managed Node-RED editor.
Set up the common IoT resources once, to create the shared models, adapters, gateway, HVAC digital twin instances, and Boiler digital twin instances for the Flow runtime scenarios, then use these scenarios to demonstrate data ingestion, event processing, and logging.
- Scenario: Ingesting Live Data from an External Broker subscribes to an external MQTT broker and sends each live message to OCI IoT.
- Scenario: Ingesting Batch Data from Object Storage downloads sequential CSV objects from Object Storage and sends each batch to OCI IoT.
- Scenario: Monitor Normalized IoT Data, Send Commands, and Email Alerts dequeues
NORMALIZED_DATA, ignores HVAC pressure records, and sends a Boiler reset command when a mapped Boiler digital twin's pressure exceeds 100. It pollsRAW_COMMAND_DATAevery 5 seconds for up to 70 seconds and publishes a success, failure, or timeout notification. This managed Flow Runtime pattern does not require an external application to access the IoT database directly. - Scenario: Configure Logs for an IoT Flow Runtime sends Node-RED system logs to OCI Logging.
To let a flow execute a workspace procedure, use Scenario: Grant a Database Privilege to a Flow Runtime. It includes the prerequisites, database connection setup, grant, verification and revoke steps. This scenario does not require the shared HVAC or Boiler sample resources.
For the available managed nodes, configuration, permissions and message inputs/results, see the Flow Runtime Node Reference.