Get up and running
Choose the platform of the server you’re installing.
Windows
- Prepare your runtime. Install Java 17 and PowerShell 7. Set JAVA_HOME to your Java 17 installation directory.
- 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.
- Start the engine. Keep the terminal open while the server runs.
.\connecthub-server.ps1
macOS
- Prepare your runtime. Install Java 17 matching your Mac: ARM64 for Apple silicon or x64 for Intel.
- 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.
- 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
Linux
- Prepare your runtime. Install Java 17 matching your server architecture. Bash is required.
- 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.
- Start the engine. Keep the terminal open while the server runs.
bash ./connecthub-server
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.0 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?
- Back up your existing Connect Hub 4.7.0 installation and keep automatic channel deployment disabled.
- Install the plugin ZIP through Extensions, then restart the engine and reconnect the Administrator.
- Open Settings → Hub connection and pair with your authorized Hub workspace.
- 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.
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.
30c171c8a74e5b6b5d2df87b464107300964db8a407f102d4bbb8f905acb28b3e32b14b59ffd43c00153586aba6ed9505dd10b9a128301793ada82791c95845d9b8b5d580ecf7196795c752f2f8c07ef6aa4149b6504d9879678efa0f5592b3c