IoT UI System – Quick Start for Testers and Support

1. Overview

This guide explains how to run the IoT UI system from the dist folder. Everything needed is inside dist:

  • app/ – built backend and Angular UI

  • conf/ – configuration and customization

  • bin/ – startup scripts and main app.env

  • ext/ – external libraries (rarely changed)

  • liquibase/ – database/ACS change sets

  • logs/ – logs

2. Folder Structure

📁 dist/
├── 📁 bin/
│    ├── 📄 app.env           # main configuration (paths, DB, ACS)
│    ├── 📄 start.cmd/sh      # start scripts
├── 📁 conf/
│    ├── 📁 customization/    # System customizations
│    │    ├── 📁 def/
│    │    ├── 📁 mc/
│    │    └── 📁 sc/
│    └── 📄 hazelcast-client.xml
├── 📁 app/                   # built application (backend + UI)
├── 📁 ext/                   # heavy libraries
└── 📁 liquibase/             # database/ACS change sets
└── 📁 logs/                  # logs

3. What’s Inside Each Folder

  • app/ – backend WAR/JAR and compiled Angular UI

  • conf/customization/ – customization files

  • conf/hazelcast-client.xml – hazelcast config config

  • bin/ – startup scripts + main environment variables

  • ext/ – heavy libraries rarely updated

  • liquibase/ – all database and ACS change sets

  • logs/ – logs from application

4. Troubleshooting

  • DB connection error → verify DB_HOST, DB_USER, DB_PASSWORD in app.env.

  • ACS connection error → verify ACS_WEB_SERVICE_HOST and credentials in app.env.

  • Application does not start → check start.sh/start.cmd permissions and Java version.

  • Any error → check logs/ for more details

← Back | Home