Application Management (/ui/apps)
Beyond PLC data collection, the gateway can also run several companion tools (dashboards, data flows, monitoring, and so on). This screen gives you an at-a-glance view of their status and lets you start, stop, restart, or deploy a new app.
This screen lists the containers of the host docker (using the /var/run/docker.sock mount).
plantpulse-edge excludes itself — self-exclude: it does not appear in the list, and every
start/stop/delete/inspect/logs/stats/deploy operation is rejected with IllegalStateException (so that
it cannot shut down or delete itself).
To restart plantpulse-edge, use SSH with systemctl restart plantpulse-edge.service
or the "Restart" button on the status bar (via a 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 the previous version has been removed — navigate to other screens using the left sidebar or by clicking the logo.
2. Top Actions
| Button | Action |
|---|---|
↻ Refresh (fa-sync) | apps.refresh() — redraws the cards immediately |
+ Deploy New App (fa-plus) | apps.openDeploy() — modal for defining and registering a new container (custom image / port mapping / environment variables) |
A small gray label at the top right of the screen (#apps_status_label) occasionally shows the last refresh time, indicating that automatic polling is alive.
3. Card Structure
Each app is shown as a rounded card (20px radius with a gray border) that lifts slightly on hover.
| Card Item | Meaning |
|---|---|
| Large icon on the 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 in a gray box. The docker image in use (e.g. grafana/grafana:10.3) |
| Port | Click → opens the app screen automatically in a new window (e.g. 3000 → http://게이트웨이:3000/) |
| Created | Time the container was created |
| Resources | CPU / memory (running apps only, from docker stats) |
| Action area (bottom of the card) | [Start] [Stop] [Restart] [Logs] buttons — enabled or disabled depending on status |
The screen refreshes automatically every 10 seconds — it calls the backend /apps/list and redraws.
Commonly Seen Companion Apps
| Tool | Role |
|---|---|
| Grafana | Time series graphs / operations dashboards |
| Node-RED | No-code data flows / automation |
| HiveMQ (MQTT broker) | Message relay (Sparkplug B publisher) |
| Cassandra | Time series store |
| Portainer | Visual docker container management tool |
| Uptime Kuma | Simple availability monitor (up or down) |
| File Browser | Web file manager |
The installed apps vary by environment. Which apps appear depends on what the system administrator has deployed remotely from the IIoT platform.
Common Tasks
Opening a Companion App Screen
Click the port number on the card to open that app's screen in a new window.
- Normally connects automatically in the
http://게이트웨이IP:포트/form - Some apps may require their own login (e.g. Grafana, Portainer)
Starting / Stopping / Restarting a Companion App
| Action | How | Notes |
|---|---|---|
| Start | [Start] button on the card | Enabled only when stopped |
| Stop | [Stop] button on the card | Enabled only when running or paused |
| Restart | [Restart] button | Always available |
A confirmation dialog appears once, so you can [Cancel] if you clicked by mistake.
Viewing Companion App Logs
The [Logs] button on the card shows the last 200 lines on a black screen. Use it to identify why an app fails to start, or to pass along to the system administrator.
Refresh
Click the [Refresh] button at the top left to update immediately (independent of the automatic 10-second refresh).
Managing the Gateway Itself (Status Bar Quick Actions)
The seven icons on the status bar at the bottom left of the screen control the gateway OS and the application itself — available on every page.
Detailed behavior, expected duration, and cautions are collected in a separate document: Status Bar Quick Actions.
| Icon | Action | Notes |
|---|---|---|
🎬 (fa-projector) System Reboot | OS reboot | About 3–5 minutes — all PLC collection stops |
🔁 (fa-repeat-1-alt) Restart Application | Restarts only Tomcat / gateway SW | Under 1 minute |
🗑 (fa-trash) Clean Temporary Files | Clears temp / cache | When disk space is low |
⏱ (fa-stopwatch) Backup | Backs up settings + DB | Backup / Restore |
📄 (fa-file-alt) Download Logs | Diagnostic log zip | Attach when reporting a problem |
🔌 (fa-microchip) O/S and Firmware Upgrade | Firmware update | Proceed with care |
☁ (fa-cloud-download) S/W Upgrade | Gateway SW update (product.kopens.io) | Enabled only when the Upgrade available! badge appears at the top right |
During a reboot or upgrade, PLC value collection is temporarily suspended. We recommend performing these outside operating hours.
Installing the Gateway Itself
For system administrators — when installing for the first time in a new environment.
The base installation is usually done in advance by the system administrator, but for a first-time installation in a new environment you can install everything at once with the following one-liner.
bash < <(curl -s http://product.kopens.io/plantpulse-edge/install.sh)
Internally, this installs JDK, Tomcat, Cassandra, and the gateway.
If you need detailed build / deployment / configuration procedures, see Advanced — Configuration File Guide and Advanced — Developer Notes.
Frequently Asked Questions
Q. An application is "stopped" and will not start
The PC may be short on resources (e.g. out of memory), or there may be a port conflict.
- Check the memory / disk gauges on the main screen
- Try [Settings] → [Clean Temporary Files]
- If it still fails, check the error message with the [Logs] button and pass it to the system administrator
Q. If I restart the gateway, will PLC connections / tags be lost?
No. Settings are stored safely, so they are restored automatically after the restart, and PLCs configured for "auto start" resume collection automatically.
Q. Can companion apps run on a separate PC from the gateway?
It is possible, but the recommended configuration is the same PC. Consult your system administrator.