CONNECT HUB 4.7.0 | WINDOWS EARLY ACCESS | 2026-10-05

INSTALL
Install Java 17 and PowerShell 7 using your organization's approved sources.
Set JAVA_HOME to the Java 17 installation directory (without the bin suffix).
Open PowerShell 7 and verify java -version and $PSVersionTable.PSVersion.
Download the Windows ZIP and its .sha256 file into the same folder. Compare:
  Get-FileHash .\connect-hub-4.7.0-windows-early-access-20261005-r2.zip -Algorithm SHA256
with the hash in the .sha256 file before extracting.
Extract the ZIP to a writable directory, for example C:\ConnectHub.
In PowerShell 7, change into the extracted connect-hub-4.7.0 folder and run:
  .\connecthub-server.ps1
If Windows marks the downloaded script as blocked, review the launcher and use:
  Unblock-File .\connecthub-server.ps1
Follow your organization's PowerShell execution policy. No machine-wide policy
change is needed or recommended. This bundle does not install a Windows service.
Windows startup has not yet been tested on a Windows machine.

NEW INSTALLATION ONLY
Extract into a new writable folder. Do not overwrite an existing installation.
Requires Java 17 matching your computer architecture and at least 2 GB RAM.
The engine heap is limited to 1 GB. The pilot uses the bundled Derby database.
The headless engine does not need JavaFX. The desktop Administrator requires
its separate Launcher and an appropriate JavaFX runtime.

CONNECT
Keep the terminal open while the server runs. Connect your Administrator Launcher
to https://localhost:9448. A new database starts with admin/admin; change that
password immediately. The listener is loopback-only, so it is not remotely exposed.
For a remote server, use an SSH tunnel from your workstation:
  ssh -N -L 19448:127.0.0.1:9448 user@server
Then point the Launcher at https://localhost:19448.
This early-access build uses self-signed HTTPS and development code-signing
certificates. Verify the checksum and publisher before approving this specific
connection. This is a portable server bundle, not a signed native installer.

PLUGIN AND CHANNELS
Globalesm Hub 1.21.0 and Channel History are already included.
Do not install the plugin twice. Pair in Settings > Hub connection using a key
from your authorized workspace. Start with Monitor only and Restrict PHI enabled.
No channels, patient data, runtime database or private signing keys are included.
Keep server.startupdeploy=false until all channel tests and approval are complete.
Confirm the log says 'Skipping initial deployment of channels'. Use synthetic tests.
The separate plugin ZIP is only for existing Connect Hub 4.7.0 installations.

STOP AND BACK UP
Stop the foreground server with Ctrl+C; wait for it to exit before closing the
terminal or changing files. Preserve the entire extracted folder, especially
appdata and conf, for a backup while the engine is stopped. Never downgrade a
database in place. Restore a complete matching backup instead.

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.