Install the Print Bridge

The Print Bridge is an independently installed service. Choose an always-on host that can reach the approved printers and the configured Ennea API. It can share a host with the machine Edge Runtime, but each service has its own installation, identity and permissions.

Prepare

• Confirm the supported OS/architecture in the supplied release manifest. An x64 package is not an ARM package.
• Obtain the release package and verify its SHA-256 manifest and publisher signature where supplied. A locally built unsigned package is not a signed production release.
• Agree the Ennea HTTPS API origin, proxy/network requirements and printer IPs or narrow CIDRs and ports with IT.
• Create a Print Bridge in the intended site and environment in Operations Studio. Generate a pairing code when the installer is ready; codes expire after 15 minutes and are single-use.

Do not use a production bridge identity for a test environment. Pairing codes and credentials are secrets; do not include them in command histories, screenshots or support tickets.

Windows

Use the supplied EnneaPrintBridge-version-windows-x64-setup.exe package. The installer includes the application runtime and service host. Customer IT does not need to install Node.js or pnpm separately.

1. Run the installer with installation authority.
2. Open Ennea Print Bridge Setup from the Start menu.
3. Enter the HTTPS API origin and the current pairing code.
4. Approve the required printer addresses or restricted networks and ports locally.
5. Start the service and verify the bridge's latest contact in Operations Studio.

The EnneaPrintBridge service runs as LocalService, starts automatically and has a restart policy. Pairing and local-policy changes require local administration. Configuration and state live in %ProgramData%\Ennea\PrintBridge\config and state, separate from application files.

For later administration, open an elevated PowerShell session:

$bridge = "$env:ProgramFiles\Ennea Print Bridge\ennea-print-bridge.cmd"
& $bridge status
& $bridge policy approve --network 192.168.20.51 --ports 9100
& $bridge check --host 192.168.20.51 --port 9100
Restart-Service EnneaPrintBridge

For managed distribution, the installer accepts /S for silent installation. Pairing and local policy still need explicit configuration.

Windows service installation, reboot behavior, organization signing and real printer acceptance must be verified on the supported Windows host before commissioning. A build workflow or successful macOS test alone is not that evidence.

Linux

Use the release archive for the supported distribution and architecture. For Linux x64:

tar -xzf ennea-print-bridge-1.0.0-linux-x64.tar.gz
cd ennea-print-bridge-1.0.0-linux-x64
sudo ./install.sh
sudo ennea-print-bridge init --url https://your-ennea-api.example
sudo ennea-print-bridge enroll
sudo ennea-print-bridge policy approve --network 192.168.20.51 --ports 9100
sudo ennea-print-bridge policy validate
sudo ennea-print-bridge check --host 192.168.20.51 --port 9100
sudo systemctl start ennea-print-bridge
sudo ennea-print-bridge status

enroll requests the pairing code interactively. The installer enables the service but leaves it stopped for setup. The ennea-print system account reads root-owned configuration in /etc/ennea-print-bridge and writes protected state in /var/lib/ennea-print-bridge. Do not initialize a second state directory for the same installation.

Connection policy

An explicit address is the narrowest policy. IT can instead approve a dedicated printer CIDR and selected ports to allow later printer additions within that boundary. An unrestricted office or machine network is not required. Approving a destination permits a connection; it does not create the central Printer record or prove successful physical output.

Cloud configuration cannot broaden this local policy. A newly configured endpoint outside it remains blocked until IT changes the host policy. No inbound network listener is required by the print service.

Verify the complete installation

1. Confirm the correct bridge/site/environment and recent contact.
2. Confirm the local policy and printer configuration revision.
3. Run a connection check without printing.
4. Queue one explicit test label, inspect the job and scan the physical output.
5. Restart the service and confirm its identity and journal persist.
6. Test a temporary cloud interruption and confirm acknowledgement recovery does not produce duplicate output.

The service's Sent result establishes TCP delivery, not printer-confirmed paper output. See Jobs and recovery.

Update, replace or remove

Use the release-specific service update procedure, preserve protected state and schedule changes with the operator. Keep the prior package and a compatible state backup for rollback. Never start two copies with the same copied identity and journal.

Revoke a compromised or retired bridge in Operations Studio. A deliberately replaced host needs a new pairing flow and reconciliation of old in-flight work. Revocation prevents further authorized cloud work; it cannot recall bytes already sent.

Updates are operator-controlled; the bridge never downloads executable updates. Stop the service, back up its protected configuration/state, run the approved installer and restart. Keep journal format compatibility when rolling back.

Uninstall through Installed apps → Ennea Print Bridge on Windows or sudo ./uninstall.sh from the Linux release package. Both retain configuration and state. With the service stopped, ennea-print-bridge forget removes the local credential while retaining replay evidence; revoke the bridge in Ennea separately. Remove retained files only after reconciling uncertain jobs. diagnostics produces redacted operational evidence; review it before sharing.

For a customer-hosted Ennea platform, pair a bridge with that deployment's HTTPS API origin. Re-pair deliberately when changing deployment; do not silently fall back to a public cloud endpoint.

Before changing the API origin, synchronize outstanding receipts and reconcile uncertain output on the original deployment. Stop the service and use forget, then init --url and enroll for the new origin. Pending receipts, accepted/sending jobs, credentials or an incomplete enrollment block an origin change. The journal and local policy are retained. For same-bridge repair, generate a fresh code and use Pair again in Windows Setup or run enroll while stopped; start the service afterward.