Topology and hosting
One binary, three roles: backend, store hub, Connect Agent.
The same server executable runs as the backend, as an optional store hub on a store’s LAN, or as a Connect Agent next to SAP. You choose where each runs; the registers only need the backend’s address and certificate fingerprint.
ROLES
BackendAPI, portal, workers, PostgreSQL
Store hubshared tables and orders on the LAN
Connect Agentoutbound bridge to the Service Layer
Registersreach the backend, or the hub on the LAN
Hosting
Three places for the backend.
Your premisesThe backend next to SAP Business One; the Service Layer on the LAN; registers over the WAN or a VPN. The simplest topology, no agent needed.
Your cloud VMA Windows VM you own on any provider with HTTPS exposed to the stores; the Connect Agent next to SAP relays the Service Layer calls outbound only.
A CERTICONS-hosted VMThe same backend run by CERTICONS under your name and licence, one tenant per server, with the Connect Agent on your LAN. Still installers, still your data.
Optional roles
When a store or a network needs more.
Store hubRestaurants and multi-register stores whose registers must share table state, held tickets and kitchen orders when the WAN is down run the binary in store mode on a LAN machine. Registers talk to the hub on the LAN; the hub mirrors upstream when the WAN returns. Drilled with three registers and a hub outage.
Connect AgentWhen the backend cannot reach the Service Layer, the binary runs in agent mode next to SAP, enrols like a device, opens an outbound-only channel and relays calls. SAP is never exposed to the internet; the agent holds no SAP password of its own.