CONNECT HUB ENGINE 4.7.0 | LINUX EARLY ACCESS | 2026-10-05
Includes Globalesm Hub plugin 1.21.0 and Channel History 1.0.0.
This installs the engine. A Globalesm Hub workspace and pairing key are separate.

REQUIREMENTS
Linux with Bash and Java 17. Use a Java build matching the server architecture.
The headless server does not require JavaFX. The desktop Administrator requires
an appropriate Launcher/JavaFX runtime on the administrator's computer.
Allow at least 2 GB RAM for this pilot; the engine heap is capped at 1 GB.
The included Derby database is for this pilot installation, not a production sizing recommendation.

NEW INSTALLATION ONLY
Do not extract this package over an existing engine or reuse an existing database.
Download the TAR.GZ, its .sha256 file and verify in the same directory:
  sha256sum -c connect-hub-4.7.0-linux-early-access-20261005-r2.tar.gz.sha256

Install Java 17 using your distribution's approved package source, then confirm:
  java -version

Create a dedicated user and extract into /opt:
  sudo useradd --system --user-group --home-dir /opt/connect-hub --shell /usr/sbin/nologin connecthub
  sudo tar -xzf connect-hub-4.7.0-linux-early-access-20261005-r2.tar.gz -C /opt
  sudo mv /opt/connect-hub-4.7.0 /opt/connect-hub
  sudo chown -R connecthub:connecthub /opt/connect-hub

The package includes startup deployment disabled, loopback-only HTTPS on port
9448 and a 1 GB heap limit. Keep server.startupdeploy=false until channel testing
is complete. No channels or patient data are supplied.

SYSTEMD (if your distribution uses systemd)
  sudo cp /opt/connect-hub/connect-hub.service /etc/systemd/system/
  sudo systemctl daemon-reload
  sudo systemctl enable --now connect-hub
  sudo systemctl status connect-hub
  sudo journalctl -u connect-hub -n 100 --no-pager

If Java 17 is not the default java on PATH, add an Environment=OIE_JAVA_PATH=...
line in a systemd service override, using the full path to your Java 17 executable.

REMOTE ADMINISTRATION
From your workstation, open an SSH tunnel (substitute your SSH user and host):
  ssh -N -L 19448:127.0.0.1:9448 user@server
Point your Administrator Launcher at https://localhost:19448.
On a NEW database the initial login is admin/admin; change it immediately.
The HTTPS certificate and code-signing certificate are self-signed for early
access. Verify the download checksum and publisher before approving this specific
connection in the launcher. This build does not have a CA-issued release signature.
Do not expose the initial login directly to the Internet.

HUB PLUGIN
The engine bundle already includes Globalesm Hub 1.21.0; do not install it twice.
For a separate, matching Connect Hub 4.7.0 installation, back up the engine first,
install globalesm-hub-1.21.0-connect-hub-4.7.0.zip through Extensions, restart the
engine with startup deployment disabled, then reconnect the Administrator.
This ZIP is not the Mirth, OIE or BridgeLink variant.
In Settings > Hub connection, pair using a key from your authorized Hub workspace.
Begin with Monitor only and Restrict PHI enabled. Keep configuration backups off
unless explicitly required. Never place pairing keys or credentials in shared instructions.

VALIDATION
Confirm the startup log says initial channel deployment is skipped. Confirm the
Globalesm Hub version in Extensions. Use synthetic messages for the pilot.
Do not import production channels or enable deployment until they are approved.
A passing smoke test is not production acceptance or a guarantee of no defects.

ROLLBACK / REMOVAL
Stop the service before changing files: sudo systemctl stop connect-hub
Preserve the complete /opt/connect-hub directory, especially appdata and conf.
Never downgrade an upgraded database in place. Restore a complete matching backup.

LAUNCHER NAMES
Use connecthub-server on Linux/macOS or connecthub-server.ps1 on Windows.
The legacy oieserver and oieserver.ps1 commands remain available for compatibility.