The GMN Paul Müller Industrie GmbH & Co. KG openXEdge runs a suite of services in Docker containers. This page gives you the overview: what runs, what it is for, and where the in-depth documentation lives. The exact documented versions are shown on the documentation status page.
Operation & base system
| Service | Purpose |
|---|---|
| MainUI | The central user interface — login, settings, updates, diagnosis, and the frame in which all other interfaces are embedded. |
| UpdateService | Background service that installs staged firmware updates and automatically rolls back on failure. Deliberately runs separate from the rest of the stack. |
| Maintenance Sidecar | Executes maintenance actions and one-time maintenance migrations — see Maintenance actions. |
| Mosquitto / PostgreSQL | Internal MQTT broker and internal database. No user interface of their own; not reachable from outside. |
Data acquisition & visualization
| Service | Purpose | In-depth docs |
|---|---|---|
| IO-Link Master Proxy | Connects the IFM IO-Link master and provides its configuration UI under IOLink Master Configuration. | Configure the IO-Link master |
| IDEA4S-Bridge | Reads the IDEA-4S sensors and provides device status + parameterization (tile IDEA4SBridge, device settings in Settings). A GMN product. | Configure an IDEA4S device |
| DataStore | Brinkhaus product for data storage and forwarding; stores the edge’s measurement data (tile DataStore). | Dedicated DataStore manual in the Brinkhaus customer portal |
| Grafana | Dashboards on top of the collected measurement data (tile Grafana). | Grafana dashboards |
Extensions
| Service | Purpose | In-depth docs |
|---|---|---|
| AppStore (FLECS) | Installation of additional apps on the edge; installed apps appear as tiles on the home page. | Use the AppStore |
One suite, one interface
All of the interfaces mentioned above are embedded in MainUI — you log in to MainUI once and reach Grafana, DataStore, IDEA4S-Bridge, and the IO-Link master without further logins, from every LAN port of the edge (see Remote access). The services themselves do not open any ports to the outside.
If part of the suite fails (e.g. because a network cable was unplugged), the remaining services keep working and reconnect on their own as soon as the counterpart is reachable again — the edge is designed for unattended operation.