--- 格式版本: 2 标题: "Using the IoT Flow Runtime Editor" 原文链接: "https://docs.oracle.com/en-us/iaas/Content/internet-of-things/node-red.htm" 发布日期: "2026-09-02" 发布时间校准状态: "found" 发布时间需复核: "否" 发布时间来源: "rule:scrape:strict_html_body" 发布时间证据: "cpp-last-modified-time: 2026-09-02 16:38:29Z" 发布时间校准原因: "规则确认唯一严格发布时间，来源 scrape:strict_html_body" 发布时间校准置信度: "high" 发布时间候选数量: 6 发布时间严格候选数量: 2 发布时间原页读取状态: "source template page reused from URL open" 发布时间未找到原因: "" 发布时间校准时间: "2026-09-07T22:20:12+08:00" 发布时间仲裁状态: "skipped" 发布时间仲裁尝试次数: 0 发布时间仲裁耗时毫秒: 0 发现时间: "2026-09-07T22:07:29+08:00" 入库时间: "2026-09-07T14:44:36.309Z" 来源平台: "固定入口" 搜索渠道: "fixed_url" 搜索词: "https://docs.oracle.com/en-us/iaas/releasenotes" 匹配关键词: [] 相关厂家: - "Oracle" 相关专家: [] 内容类型: "网页" 抓取工具: "Free Fetch + Defuddle" 清洗工具: "Defuddle Markdown + Defuddle/Readability 正文提取" 原始附件: [] AI优质: "否" AI打分: 26 AI分档: "非优质" AI质检状态: "不通过" AI打分理由: "正文主线是OCI IoT的Node-RED编辑器操作指南，包括Flow Runtime多用户协作、软件更新、备份恢复、Oracle/OCI节点和模块管理，完全不是超节点、AI Rack、机柜级系统或AI基础设施。主题相关性0分，不满足任何高价值准入通道；虽来源为Oracle官方文档，但属教程/运维说明，按教程与运维选型硬否决处理，最高54分。历史知识库虽有Oracle OCI相关AI基础设施条目，但本文无新增机架级产品、标准、部署或工程机制。" AI质检模型: "zj-deepseek-v4-flash" AI质检时间: "2026-09-07T22:44:41+08:00" AI主题相关性: 0 AI来源权威性: 12 AI新颖性: 2 AI技术细节: 4 AI商业部署信号: 0 AI完整性: 8 AI评分提示词版本: "v17-精简生产版" AI评分提示词SHA256: "48fb9777f386026761b4873eaff30807694fb11e9b352d7c69bf2dfde750cc7d" AI评分知识库版本: "knowledge_base_v1-20260819+runtime.99" AI评分知识库SHA256: "0fbd91b8efdf08ea0580fc2df2684b6db7e286b65c7b6430d7666940f4e954c3" AI评分知识库检索词: "[\"Oracle\",\"https://docs.oracle.com/en-us/iaas/releasenotes\",\"OCI-integrated\",\"OCI\",\"IAM\",\"OCID\",\"JSON\",\"CLI\",\"API\",\"SQL\",\"SDK\",\"API-signing\"]" AI评分知识库命中: "[{\"id\":\"runtime-dccd09f98e2ca028070793f0\",\"title\":\"https://blogs.oracle.com/cloud-infrastructure/oci-achieves-nvidia-exemplar-cloud\",\"sourceType\":\"ai_excellent_article\",\"time\":\"\",\"matchedTerms\":[\"Oracle\",\"OCI\"],\"rank\":-12.894529052729364},{\"id\":\"runtime-51cfe3db04ed0bd3efb5e0e3\",\"title\":\"The full stack behind abundant intelligence\",\"sourceType\":\"ai_excellent_article\",\"time\":\"2026-08-25\",\"matchedTerms\":[\"Oracle\",\"API\",\"SDK\"],\"rank\":-12.31675899132279},{\"id\":\"runtime-bf4039a0342d37545e9459a2\",\"title\":\"Most Neoclouds Suck At Security\",\"sourceType\":\"ai_excellent_article\",\"time\":\"2026-08-30\",\"matchedTerms\":[\"Oracle\",\"OCI\",\"CLI\",\"API\"],\"rank\":-11.7056378512895},{\"id\":\"runtime-66d1ddc58948150bffee973a\",\"title\":\"Delivering Vera: NVIDIA’s First CPU Built for Agents Is Shipping Now\",\"sourceType\":\"ai_excellent_article\",\"time\":\"\",\"matchedTerms\":[\"Oracle\",\"OCI\",\"API\"],\"rank\":-11.360008220524834},{\"id\":\"runtime-0210d17c29c694da454d0e78\",\"title\":\"HPE caps stellar Q3 with Oracle ‘gigawatt scale’ networking deal\",\"sourceType\":\"ai_excellent_article\",\"time\":\"\",\"matchedTerms\":[\"Oracle\",\"OCI\"],\"rank\":-10.083741755394508}]" 采集批次: "2026年9月7日22点05分18秒" 采集批次ID: "20260907-220517-361" 去重键: "https://docs.oracle.com/en-us/iaas/Content/internet-of-things/node-red.htm" --- Use the OCI-integrated Node-RED editor to build and deploy flows, configure Oracle Database and OCI nodes, and collaborate with other authorized users. Each [IoT Flow Runtime](https://docs.oracle.com/iaas/Content/internet-of-things/flow-runtimes.htm "An IoT Flow Runtime is an OCI native resource that provides a managed Node-RED runtime within an IoT domain.") provides a managed [Node-RED editor](https://nodered.org/docs/user-guide/editor/). Open the editor from the [Flow Runtime details](https://docs.oracle.com/iaas/Content/internet-of-things/get-iot-flow-runtime.htm#top "Get information about an IoT Flow Runtime.") page in the OCI Console. OCI Console single sign-on authenticates you to the editor, so you don't need separate Node-RED credentials. If you need help finding the IoT Flow Runtimes, see [Listing IoT Flow Runtimes](https://docs.oracle.com/iaas/Content/internet-of-things/list-iot-flow-runtimes.htm "List IoT Flow Runtime resources in a compartment or IoT domain."). The Node-RED editor, uses this format for the flow runtime endpoint: ``` https://.flows.iot..oci.customer-oci.com/ ``` Your OCI [IAM permissions](https://docs.oracle.com/iaas/Content/Identity/policyreference/iot-policy-reference.htm) determine whether you can view or edit the flows. ## Working with Multiple Users More than one authorized user can open and edit the same Flow Runtime. Each user works in a separate browser editor session; this isn't character-by-character collaborative editing. If another user deploys changes while you have undeployed changes, you have the option to review and merge the newer deployed flow configuration before you deploy. Coordinate deployments and keep related work on separate flow tabs when possible. Separating work into tabs also makes changes easier to compare and merge. For more information, see [Flow Structure](https://nodered.org/docs/developing-flows/flow-structure). ## Updating Flow Runtime Software OCI IoT manages the software for a Flow Runtime, including the managed Node-RED runtime. Don't use the Node-RED [Palette Manager](https://nodered.org/docs/user-guide/editor/palette/manager) to update the managed runtime. The Palette Manager manages permitted node modules. When one or more Flow Runtimes require a software update, OCI sends an announcement that lists the affected region, Flow Runtime name, Flow Runtime OCID, and the **Action required by** deadline. You have 14 days (336 hours) from the notification time to update each listed Flow Runtime. 1. Open the announcement and review the affected resources and deadline. To find a listed resource in the Console, see [Listing IoT Flow Runtimes](https://docs.oracle.com/iaas/Content/internet-of-things/list-iot-flow-runtimes.htm#top "List IoT Flow Runtime resources in a compartment or IoT domain."). 2. Before updating, move any required files from the Flow Runtime's local file system to Autonomous Database, [File Storage](https://docs.oracle.com/iaas/Content/internet-of-things/configure-iot-flow-runtime-storage-access.htm#top "Add up to 5 File Storage mounts to an IoT flow runtime's network configuration."), or another persistent storage service. The local file system is ephemeral and files on it might be lost during deactivation or activation. Data stored in Autonomous Database and mounted File Storage file systems is retained. If you need another recovery point for the flow definitions, . 3. [Deactivate the affected Flow Runtime](https://docs.oracle.com/iaas/Content/internet-of-things/deactivate-iot-flow-runtime.htm#top "Deactivate an active IoT Flow Runtime, to disable or pause the IoT flow runtime, so no messages are processed.") and wait for the deactivation work request to complete and the lifecycle state to become **Inactive**. 4. [Activate the Flow Runtime](https://docs.oracle.com/iaas/Content/internet-of-things/activate-iot-flow-runtime.htm#top "Activate an inactive IoT Flow Runtime.") to apply the pending software update. Wait for the activation work request to complete successfully and the lifecycle state to become **Active**. For work request states and details, see [Work Requests for IoT Domain Groups, Domains, and Flow Runtimes](https://docs.oracle.com/iaas/Content/internet-of-things/work-requests.htm#iot-work-requests "Get work request information for IoT domain group, domain, and flow runtime operations."). 5. Open the editor and verify that the flows, Flow Runtime interface, Oracle nodes, and other permitted node modules used by the workload operate normally. If activation or flow execution fails, review the [configured Flow Runtime logs](https://docs.oracle.com/iaas/Content/internet-of-things/configure-logs-flow-runtimes.htm#top "Send Node-RED system-console logs from an IoT Flow Runtime to OCI Logging in the customer tenancy, generate a test message, and verify that the message is available."). ## Backing Up and Restoring Flows The **Flows** tab stores the Flow Runtime's one current, complete Node-RED `flows.json` configuration file. Adding another `flows.json` replaces that active configuration; it doesn't create a separately retained backup. Save a point-in-time copy outside the Flow Runtime, such as in an Object Storage bucket. A [File Storage mount](https://docs.oracle.com/iaas/Content/internet-of-things/configure-iot-flow-runtime-storage-access.htm "Add up to 5 File Storage mounts to an IoT flow runtime's network configuration.") makes files available to running flows and isn't required for this management-side backup. ### Backing Up the JSON Flows Configuration 1. In the Node-RED editor, [export the complete flow JSON configuration](https://nodered.org/docs/user-guide/editor/workspace/import-export#exporting-flows) and download the JSON file. You can instead [retrieve the active flows JSON](https://docs.oracle.com/iaas/Content/internet-of-things/get-iot-flow-runtime-flows.htm "Get the complete opaque Node-RED flows JSON for a specified IoT Flow Runtime OCID.") from the Flow Runtime by using the Console, CLI, or API. 2. [Create an Object Storage bucket](https://docs.oracle.com/iaas/Content/Object/Tasks/managingbuckets_topic-To_create_a_bucket.htm) or select an existing backup bucket. Enable object versioning when you want Object Storage to retain earlier versions that use the same object name. 3. Upload the JSON file. Use a name that identifies the Flow Runtime and backup time, for example `flow-runtimes//2026-07-28T160000Z-flows.json`. 4. Record the Flow Runtime OCID, Node-RED version, export time, and reason for the backup. Download the object and confirm that it contains valid JSON before depending on it for recovery. ### Restoring the JSON Flows Configuration 1. Retrieve and externally save the current flows JSON configuration before replacing it. 2. Download the point-in-time JSON configuration that you want to restore from Object Storage. 3. Add the JSON on the **Flows** tab, or [replace the complete flows JSON](https://docs.oracle.com/iaas/Content/internet-of-things/update-iot-flow-runtime-flows.htm "Add or replace the complete Node-RED flows.json for an IoT Flow Runtime.") by using the CLI or API. If you need help finding flows, see [Listing IoT Flow Runtimes](https://docs.oracle.com/iaas/Content/internet-of-things/list-iot-flow-runtimes.htm "List IoT Flow Runtime resources in a compartment or IoT domain."). 4. Open the **Node-RED editor** and verify the flows, shared configuration nodes, and installed node modules. Reenter any required credentials that the exported JSON didn't preserve, and test critical flows. ## Oracle Nodes The managed [palette](https://nodered.org/docs/user-guide/editor/palette/) includes and in addition to the standard Node-RED nodes. The nodes available in a Flow Runtime can depend on the service version. ### Oracle Database Nodes The **db-nodes** group connects flows to an Oracle Database, including a customer Autonomous Database when configured. | Node | Description | | --- | --- | | **db-connection** | Defines a shared Oracle Database connection that the other database nodes use. | | **begin transaction** | Obtains a database connection and begins a transaction for downstream database operations. | | **end transaction** | Commits or rolls back the current transaction and releases its database connection. | | **enqueue** | Adds a message to a configured Oracle Database transactional event queue. | | **dequeue** | Retrieves a message from a configured Oracle Database transactional event queue. | | **sql** | Runs a SQL statement by using the configured database connection. | ### OCI Nodes The **oci-nodes** group connects a flow to supported OCI IoT operations. | Node | Description | | --- | --- | | **iot-config** | Defines the shared OCI Config authentication, region, and default compartment settings used by OCI nodes. | | **send command** | Sends a command to a digital twin instance. | | **subscribe** | Subscribes a flow to messages from a supported OCI IoT source. | | **telemetry** | Sends telemetry from a flow to OCI IoT. | ## OCI Config Options The palette labels the shared configuration node **iot-config**. Its edit dialog uses the **OCI Config** label. Select the authentication type appropriate for the flow: | Authentication type | Description | | --- | --- | | **Config File** | Uses an OCI SDK configuration file and the selected profile. | | **Instance Principal** | Uses the identity of the OCI compute instance when an instance principal is available to the runtime environment. | | **Resource Principal** | Uses the Flow Runtime resource principal. This option avoids storing a user's long-lived credentials in the flow. Add the Flow Runtime to a dynamic group and grant only the [policies required for the OCI resources](https://docs.oracle.com/iaas/Content/Identity/policyreference/iot-policy-reference.htm) that its nodes access. | | **API Key (Simple)** | Uses OCI user API-signing key information supplied to the configuration node. Protect these credentials and use a resource principal instead when the target service supports it. | Set **Region** to the region containing the target resources. Set **Compartment OCID** to the default compartment for child OCI nodes. A child node can override the default compartment. After changing the configuration, select **Update**, select **Deploy**, and then use **Test Connection**. ## Managing Node Modules The [Palette Manager](https://nodered.org/docs/user-guide/editor/palette/manager) is a built-in feature in the Node-RED editor. It lets you install, update, disable, or remove node modules without using the command line and provides an integrated package interface associated with the public Node-RED library. In an OCI IoT Flow Runtime, you can manage only the modules and versions that the service makes available or permits. To explore additional Oracle custom nodes, see [Node-RED Oracle Cloud Nodes](https://github.com/oracle-samples/node-red-nodes) on GitHub. The repository includes nodes for Oracle Database and Advanced Queues (AQ), Oracle Fusion Cloud SCM, OCI services, and the OCI IoT Platform, along with installation guidance, node references, and example flows. Before installing a node from the repository, confirm that the module and version are permitted for your Flow Runtime.