OPC UA
The OPC UA integration runs in process inside cms-api (the node-opcua library, pure
JavaScript) — no native SDK and no separate microservice, unlike SAP.
Connection
Register an OPC UA server under External Connections: endpoint, security policy and credentials. Test the connection before configuring the collector.
Collection — OPC_UA_TRIGGER
CMS watches a trigger tag and fires when its value changes. It is event-driven: there is no scheduled polling.
Typical use: the PLC writes 1 to an “order ready” tag; CMS detects it, reads the associated data
tags and forwards the message to the ERP.
Delivery — OPC_UA_WRITE
Writes values to OPC UA server tags from the message data — the path from the ERP back to the shop floor.
Writing changes the state of real equipment. Delivery goes through the write permission gate — keep it enabled in production. With the gate configured and its connection down, the write is refused, not released.
Testing without a PLC
The Simulators screen ships a built-in OPC UA server, with named tag profiles (one per simulated PLC). You can validate triggers and writes end to end before having access to the equipment.
A dropped connection raises the CONEXAO_OPCUA_PERDIDA alert.