Projects Gateway Lifecycle

Goal

Deploy a PLC project to a gateway / edge (non-cloud) target by running it on a runtime that points at that platform, rather than at a cloud-hosted runtime.

Note

There is no separate “Gateway” project type — you use a normal PLC only (or PLC with HMI) project. “Gateway lifecycle” refers to where the runtime executes: an on-prem gateway / edge device instead of the cloud. To reproduce this end to end you need a registered edge/gateway device and a runtime bound to it.

Before you start

• Prerequisites: A built PLC project (see PLC lifecycle), and a registered gateway/edge device available as a deployment target (see Edge connect register and Devices).
• Required role/permission: An Editor/Admin-level role with rights to manage devices and runtimes.
• Settings that affect behavior:
  • Runtime target / platform — the runtime’s configured platform decides whether the project runs in the cloud or on the gateway/edge device. Choose the gateway target when creating the runtime.
  • Device registration / connectivity — the gateway must be claimed and online before it can accept a deployment.
  • Licensing — running on an edge/gateway device consumes a license bound to that device; see Licensing and License status on edge device.

Steps

1. Build a PLC only (or PLC with HMI) project — see PLC lifecycle.
2. Make sure the gateway/edge device is registered and online (see Edge connect register and Devices).
3. Open the project’s Runtimes at /portal/workspace/runtimes/:id and add a runtime whose target is the gateway/edge platform/device.
4. Deploy the latest build to that runtime.
5. Start the runtime and confirm it is running on the device — see Runtime control overview and Edge admin overview.

No captured steps yet. Run make regenerate-flows after a portal-e2e:docflow pipeline run produces docflow-output/projects-gateway-lifecycle.json.

Related

• PLC lifecycle
• Runtime control overview
• Edge connect register
• Devices
• Licensing