Skip to main content

Post-Installation Inspection

Once installation (One-line Installation, Factory Line Installation, Air-gapped Network Installation) is complete, transition the gateway to Operational Readiness in the following order.

1. 1-Minute Health Check​

sudo bash /opt/kopens/install/bin/status.sh
curl -ks https://127.0.0.1/api/v1/system/version | python3 -m json.tool
curl -ks https://127.0.0.1/api/v1/system/health | python3 -m json.tool

Expected:

  • container running + healthy
  • 9 ports listening (80, 443, 1883, 1884, 6379, 9042, 1880, 12000, 12443) — 7799 (Tomcat JMX) listens only on 127.0.0.1
  • /api/v1/system/version → build_date / image_tag / container_mode=true
  • /api/v1/system/health → 200, all components UP

pe-status If all items are ✓, proceed to the next section. If any are ✗, refer to the "Troubleshooting" section of Container Mode Operation.

Before deploying to production, also complete the acceptance log as specified in the Production Readiness Criteria.

2. Change Initial Passwords — First​

Do not deploy to production using the default credentials created during installation. Refer to Initial Password Change for what and how to change — this is a mandatory commissioning item and must be performed before the backup and mirroring steps below.

3. Configure Automatic Backup​

sudo tee /etc/cron.d/plantpulse-edge-backup > /dev/null << 'EOF'
# 매일 새벽 3시 백업 + 일요일 새벽 4시 30일 초과 백업 삭제
0 3 * * * root /opt/kopens/install/bin/backup.sh > /dev/null 2>&1
0 4 * * 0 root find /data1/pp-backups -name 'pe-backup-*.tar.zst' -mtime +30 -delete
EOF

sudo bash /opt/kopens/install/bin/backup.sh
ls -lh /data1/pp-backups/

Details: Backup and Recovery

4. External NAS / S3 Mirroring (Disaster Recovery)​

If backups exist only on the same disk as the gateway, there is no disaster recovery effect. External mirroring is strongly recommended:

# 컨테이너 백업 예시
LATEST=$(ls -t /data1/pp-backups/pe-backup-*.tar.zst | head -1)
rsync -av "$LATEST" "$LATEST.sha256" nas:/backup/edge/

5. User and Permission Settings (Optional)​

If per-user accounts are required beyond the default admin:

The gateway provides screens for User, Role, and Menu Access Permissions.

ScreenAddressFunction
User Management/system/userCreate accounts and assign roles
Role Management/system/roleDefine roles
Menu Access Permissions/system/menu_accessDefine menus accessible by role
ScenarioRecommendation
Single-person OperationUse the default account and change only the password
Multi-person OperationSplit accounts and assign roles to track who did what
External PartnersPerform the verification below first
Verify that access is actually blocked before granting access to partners

While screens and tables for roles and menu access permissions exist, it is safer to directly verify in the installation whether these are actually applied to each request.

How to verify — Create an account with a restricted role, log in with that account, and attempt to access a blocked menu (e.g., Delete Connection) to see if it is truly disabled. «The menu is hidden» and «Access is blocked even when entering the address directly» are different.

If specific items must be shown to external parties, it is more reliable to use Platform Permission Groups to open only necessary items instead of the gateway screen.

6. Next Steps​

  1. Home Screen Card / Action Guide — Meaning of the 30 cards
  2. Add New PLC Connection
  3. Tag Registration + PLC Address Entry (Complete Guide for 44 Drivers)
  4. Sparkplug B Publishing — For external SCADA integration
  5. Flow (Node-RED) — Automation / Alarms / External Integration
  6. Operation Overview — Start/Stop/Restart/Backup/Upgrade/Diagnostics

7. Acceptance Test Checklist (For Delivery · SI Partners)​

All the following items must pass during new site acceptance:

  • For container mode, status.sh all OK; for native, verify 5 Java/Node processes in bin/ps.sh
  • /api/v1/system/version HTTP 200 + intended edge_id/site_id/container_mode returned
  • /api/v1/system/health HTTP 200 + components UP
  • Production Readiness Criteria acceptance log generated + sha256 recorded
  • /api/v1/monitoring HTTP 200 + cpu_used_percent < 30%, memory_used_percent < 60%
  • All 30 home cards displayed + 1-second update operation
  • Register 1 Simulator OPC → Start → Chart normal in /ui/opcua tree
  • Register 1 actual PLC → collection status 🟢 normal + last value updated
  • After container systemctl restart plantpulse-edge.service or native bin/restart.sh, PLC reconnection is automatic (auto_collect=true)
  • Backup cron registered + first backup file/directory creation verified
  • First backup .tar.zst and .sha256 copied to external backup location
  • Message arrival verified at external SCADA / Sparkplug receiver
  • Password Change completed (default admin password changed)
  • /etc/kopens/credentials.txt permission 0600 root verified + password delivery procedure completed
  • 30-second monitoring via log-viewer — no SEVERE / ERROR level logs
  • Disk free space 30%+ (df -h /data1)
  • OS NTP sync (timedatectl) normal
  • Gateway IP / access information delivered to operation team + handover document signed

Learn More​