Back to downloads
Install in a fresh directory

Install Connect Hub.

Choose the platform of the server you’re installing.

Windows

  1. Prepare your runtime. Install Java 17 and PowerShell 7. Set JAVA_HOME to your Java 17 installation directory.
  2. Verify and extract. Compare your download with the published checksum. Extract the ZIP into a new writable folder, then open PowerShell 7 in the extracted connect-hub-4.7.0 folder.
  3. Start the engine. Keep the terminal open while the server runs.
    .\connecthub-server.ps1
Read the full Windows guide →

macOS

  1. Prepare your runtime. Install Java 17 matching your Mac: ARM64 for Apple silicon or x64 for Intel.
  2. Verify and extract. Compare your download with the published checksum. Extract the ZIP, then open Terminal in the extracted connect-hub-4.7.0 folder.
  3. Start the engine. Keep the terminal open while the server runs.
    export JAVA_HOME=$(/usr/libexec/java_home -v 17)
    bash ./start-connect-hub.command
Read the full macOS guide →

Linux

  1. Prepare your runtime. Install Java 17 matching your server architecture. Bash is required.
  2. Verify and extract. Compare your download with the published checksum. Extract the TAR.GZ into a new writable folder, then open a shell in the extracted connect-hub-4.7.0 folder.
  3. Start the engine. Keep the terminal open while the server runs.
    bash ./connecthub-server
Read the full Linux guide →
Connect Hub Launcher 1.0.0

Open the Administrator

The launcher replaces the NextGen Administrator Launcher for Connect Hub. It includes its own Java with JavaFX.

Install
  1. Windows: run the .msi. It installs for your user only, without administrator rights. If Windows warns about an unknown publisher, choose More info › Run anyway.
  2. macOS: open the .dmg and drag Connect Hub Launcher to Applications. The first time, macOS blocks it: open System Settings › Privacy & Security and choose Open Anyway.
  3. Linux: sudo apt install ./Connect-Hub-Launcher-1.0.0-linux-x64.deb, or extract the .tar.gz and run connect-hub-launcher/bin/connect-hub-launcher.
Connect
  1. Add a connection with your engine's address, for example https://localhost:9448 through an SSH tunnel.
  2. The first time, the launcher shows the server certificate's fingerprint. Compare it with your engine's before you trust it. It remembers it for that connection.
  3. Open. The launcher downloads the Administrator once and starts it only if every file is signed by Connect Hub.

Before you install

Is this a native installer?

These are portable ZIP and TAR.GZ server packages, not EXE, MSI, DMG or PKG installers. Install Java 17 separately. Windows also requires PowerShell 7. The Linux package includes a systemd service file; Windows and macOS start in a terminal.

What is included in the engine?

Connect Hub 4.7.0, Hub plugin 1.21.3 and Channel History. The pilot uses Derby with a 1 GB Java heap limit; allow at least 2 GB RAM. No channels, patient data, local runtime database or private signing keys are supplied.

Can I upgrade my existing installation?

Use a fresh evaluation directory. Do not extract over an existing engine or reuse its database without a tested migration plan. Back up the complete installation before making changes.

How do I install the plugin separately?
  1. Back up your existing Connect Hub 4.7.0 installation and keep automatic channel deployment disabled.
  2. Install the plugin ZIP through Extensions, then restart the engine and reconnect the Administrator.
  3. Open Settings → Hub connection and pair with your authorized Hub workspace.
  4. Start with Monitor only and Restrict PHI enabled. Verify the policy on your connection before relying on it.

The engine bundles already include the plugin. Do not install it twice.

Open Integration Engine 4.6.0: use the OIE build of the plugin, then open the Administrator with the Connect Hub Launcher. The standard OIE launcher refuses it unless Allow self-signed certificates is ticked for that connection.

What has been verified?

The engine build, plugin checks and 230 bundled Administrator and extension JAR signatures were checked. Linux x86-64 and macOS Apple silicon startup passed with Java 17 and channel deployment disabled. Windows runtime, Intel macOS, Linux ARM64 and service lifecycle checks are pending. These checks are not production certification.

When should I deploy channels?

Keep automatic deployment disabled until your channel tests and approval are complete. Start with synthetic messages, validate outputs and error handling, and agree on a rollback plan before production deployment.

Verify your download with SHA-256

Compare the hash calculated on your computer with the corresponding value below. Each value identifies the exact published file.

Windows engine · 4.7.0
2b8b905e71a35228e4bcec0dad395c799fdc8aad1cc0124b2ef591a4cafa8a73
macOS engine · 4.7.0
83e9ec0a9e6a40e79b30cea1ed505369a2a7e1b09f6a217401af70f09ebea3e0
Linux engine · 4.7.0
7fbfb61278bdbf9a59a1766765c077d4deaa6bf74a90de8f95053016f000613f