Installation — overview
Stand up a NomaUBL server — JDK 17 + an Oracle or PostgreSQL database + the JAR. Runs as a long-lived Java process, one per environment, started through the nomaubl.sh wrapper. Optional systemd unit and reverse proxy for production.
Requirements
What the host needs before installing NomaUBL — JDK 17, an Oracle or PostgreSQL database, OS support matrix, ports, file-system permissions and the optional reverse-proxy / TLS layer.
Install and layout
Run -install (directly via java -jar, or via the nomaubl.sh / nomaubl.cmd wrapper) to provision an environment. Understand the directory layout produced — config / input / process / ubl / template / shared resources — and how to install several environments side by side on Linux, macOS or Windows.
Configure
After the install, every connector, scheduler interval and operational setting is configured from the Settings UI — not by hand-editing config files. Start the service, sign in, then walk through the Configuration section.
Service supervision
Run NomaUBL as a long-lived service on Linux/macOS or Windows — nomaubl.sh or nomaubl.cmd for start/stop/status, a systemd unit (Linux) or NSSM Windows service (Windows) for auto-restart on boot, and an optional nginx reverse proxy in front for TLS and a friendly hostname.
Upgrade
Move an installed NomaUBL environment forward to a new release. One command — nomaubl.sh upgrade on Linux/macOS or nomaubl.cmd upgrade on Windows — handles the JAR swap, schema migrations, reference-data merge, customer XSL merge and service restart. Writes a full report and keeps a rollback backup.