Manage
This chapter describes how to operate a configured OPC router: the runtime settings, who is authorized to log in, how to check the system status, how the system remains fail-safe, and which interfaces other systems use to connect.
- Basic Settings – Runtime Options: runtime, flow status, project backups, log output, user interface language, and resetting the databases to their factory defaults.
Users and Security
- User Management – View, create, and delete internal and external users, and manage their roles, as well as user roles and their permissions.
- Login Options – the three ways to access Web Management: local user with password, Windows authentication, and Microsoft Entra ID, each with its own scope and setup page.
- Secrets – store credentials centrally instead of repeating them in the connections.
- Certificate Management – Import, create, and view certificates; the router retrieves them from a Global Discovery Server via OPC UA GDS.
- OAuth 2.0 – Basics – the terms and flows involved in every OAuth 2.0 login.
- Secrets and Credentials in the OPC Router – Risk Assessment for IT Security and Operations: Storage of secrets and certificates, logging in to Web Management, and handling during backup, export, and redundancy.
Diagnostics and Monitoring
- Status Logging Options – Create a diagnostic log for flow execution and configure logging for transfer and runtime services.
- Escalation Levels – What the router does when too much status data accumulates: levels 0 through 4 and their countermeasures, which apply only to status logging.
- Notification Group – Set up email notifications and specify the scenarios in which they are sent.
- Metrics Export – Export runtime metrics to monitoring systems such as Grafana, Prometheus, or InfluxDB (Enterprise+).
- Health Endpoints – The HTTP endpoints where a load balancer or monitoring system queries the system’s health.
Availability
- Redundancy—operating a pair of OPC routers in hot standby mode, including guaranteed redundancy, SAP operation, third-party redundancy, and HTTP(S) failover concepts using Nginx and Traefik.
- Store and Forward – Temporarily store data when it cannot be transferred due to an error and resend it as soon as transfer is possible again.
Versioning
- Versioning – engineering the project as a versioned state, including creating and restoring snapshots.
- Project Export and Import: Exporting an OPC Router project writes selected parts of the project structure to an export file, optionally with or without encrypted authentication data; importing an OPC Router project reads an export file and resolves conflicts in plug-in configurations and flows.
Interfaces and Extensions
- pronubes Integration – Configure the connection to the pronubes IT/OT integration platform.
- Dynamic Instances API – Create and remove flows at runtime via an API.
- Dependency Storage – View, update, and delete the added assemblies.