Application Management
In addition to PLC data collection, the gateway can run several auxiliary tools (dashboard, data flow, monitoring, etc.) alongside it. This screen lets you see the status of those tools at a glance and handle start/stop/restart and new app deployment.
This screen shows the containers on the host docker (/var/run/docker.sock mount used).
plantpulse-edge itself is self-excluded — it does not appear in the list, and all operations (start/stop/delete/
inspect/logs/stats/deploy) are rejected via IllegalStateException (to prevent turning off or
deleting itself).
To restart plantpulse-edge, use SSH via systemctl restart plantpulse-edge.service
or the "Restart" button in the status bar (via signal file).
1. Opening the Screen
Click the [Applications] card on the main screen, or enter /ui/apps directly in the address bar.
┌────────────────────────────────────────────────────────────┐
│ ⊙ 애플리케이션 — 엣지에 배포된 컨테이너 · 시작/중지/재시작 │
│ [↻ 새로고침] [+ 새 앱 배포] │
├────────────────────────────────────────────────────────────┤
│ ℹ 이 화면에서는 엣지에 설치된 애플리케이션의 현재 상태를 │
│ 한눈에 확인하고, 필요할 때 시작·중지·재시작 할 수 있습니다.│
├────────────────────────────────────────────────────────────┤
│ [앱 카드] [앱 카드] [앱 카드] │
│ [앱 카드] [앱 카드] ... │
└────────────────────────────────────────────────────────────┘
The ← Back button from previous versions has been removed — use the top bar icon or the logo to navigate to other screens.
2. Top Actions
| Button | Action |
|---|---|
↻ Refresh (fa-sync) | apps.refresh() — redraws the cards immediately |
+ Deploy New App (fa-plus) | apps.openDeploy() — new container definition + registration modal (custom image / port mapping / environment variables) |
A small gray label in the upper right of the screen (#apps_status_label) occasionally shows the last update time, indicating that automatic polling is active.
3. Card Structure
Each app is displayed as a rounded-corner card (20px radius + gray border) that lifts slightly on hover.
| Card Item | Description |
|---|---|
| Large icon on left (square, light blue background) | App type — based on the container image |
| App name | Docker container name (e.g., pp-grafana, pp-node-red) |
| Status badge (rounded capsule) | running (green) / exited dead restarting (red) / paused (orange) / created (gray) |
| Image | Mono font + gray box. The Docker image in use (e.g., grafana/grafana:10.3) |
| Port | Click → opens the app screen in a new window automatically (e.g., 3000 → http://게이트웨이:3000/) |
| Created | The time the container was created |
| Resources | CPU / Memory (only for running apps, docker stats result) |
| Action area (bottom of card) | [Start] [Stop] [Restart] [Logs] buttons — enabled/disabled based on status |
The screen auto-refreshes every 10 seconds — it calls the backend /apps/list and redraws.
Common Auxiliary Apps
| Tool | Role |
|---|---|
| Grafana | Time series graphs / operational dashboards |
| Node-RED | No-code data flow / automation |
| HiveMQ (MQTT broker) | Message relay (Sparkplug B publisher) |
| Cassandra | Time series storage |
| Portainer | Visual Docker container management tool |
| Uptime Kuma | Simple availability monitoring (alive or dead) |
| File Browser | Web-based file manager |
Installed apps vary by environment. Which apps appear is the result of remote deployment by the system administrator on the IIoT platform.
Common Tasks
Opening an Auxiliary App Screen
Click the port number on the card to open the app's screen in a new window.
- Usually auto-connects in
http://게이트웨이IP:포트/format - Each app may require its own login (e.g., Grafana, Portainer)
Starting / Stopping / Restarting an Auxiliary App
| Action | How | Notes |
|---|---|---|
| Start | [Start] button on the card | Enabled only when the app is stopped |
| Stop | [Stop] button on the card | Enabled only when the app is running/paused |
| Restart | [Restart] button | Always available |
A confirmation dialog appears once, so you can press [Cancel] even if clicked by mistake.
Viewing Auxiliary App Logs
Click the [Logs] button on the card → shows the last 200 lines on a black screen. Use this to troubleshoot why an app isn't starting or to share with the system administrator.
Refreshing
You can press the [Refresh] button in the upper left to update immediately (separate from the automatic 10-second refresh).
Gateway Self-Management (Status Bar Quick Actions)
The 7 icons on the status bar at the bottom left control the gateway OS / applications themselves — common across all pages.
Detailed actions / required time / precautions are gathered in the separate document Status Bar Quick Actions.
| Icon | Action | Notes |
|---|---|---|
🎬 (fa-projector) System Reboot | OS reboot | About 3–5 minutes — stops all PLC collection |
🔁 (fa-repeat-1-alt) Restart Application | Restarts only Tomcat / gateway SW | Within 1 minute |
🗑 (fa-trash) Clean Temp Files | Cleans temp / cache | When disk is full |
⏱ (fa-stopwatch) Backup | Backs up settings + DB | Backup / Restore |
📄 (fa-file-alt) Download Logs | Diagnostic log zip | Attach when reporting issues |
🔌 (fa-microchip) O/S and Firmware Upgrade | Firmware update | Proceed with caution |
☁ (fa-cloud-download) S/W Upgrade | Gateway SW update (product.kopens.io) | Enabled only when the Upgrade Available! badge is visible in the top right |
During reboot / upgrade, PLC value collection is interrupted. It is recommended to perform these actions outside of operational hours.
Gateway Self-Installation
For system administrators – for initial installation in a new environment.
Basic installation is usually done by the system administrator beforehand, but if you are installing in a new environment for the first time, you can do a full installation with the following one-liner command.
bash < <(curl -s http://product.kopens.io/plantpulse-edge/install.sh)
This installs JDK / Tomcat / Cassandra / gateway all together.
If you need detailed build / deployment / configuration procedures, see app.properties Reference and Advanced — Developer Notes.
FAQ
Q. An application is “Stopped” but won't start
Possible causes include insufficient PC resources (e.g., low memory) or a port conflict.
- Check the memory / disk gauges on the main screen
- Try [Settings] → [Clean Temp Files]
- If it still doesn't work, use the [Logs] button to check the error message and share it with the system administrator.
Q. If I restart the gateway, will the PLC connections / tags be lost?
No. Settings are safely saved and will be automatically restored after the restart, and PLCs set to “Auto Start” will automatically resume collection.
Q. Can I place auxiliary apps on a separate PC, independent of the gateway?
It is possible, but the recommended configuration is to keep them on the same PC. Consult with your system administrator.