FileWave Boosters Improved Server Message Routing
What
FileWave 11 introduced Booster Routing, a feature that allows off-loading direct traffic to the server by routing messages via Booster. This feature provides additional security if you only allow boosters to connect to your server and have all your devices only reach boosters. With FileWave 15.0, the internal notification system has switched entirely to NATS, replacing ZMQ; NATS, in addition to built-in security features and improved performances, brings much more flexibility and can then be used in more areas.
When/Why
FileWave 15.3 can now use NATS as the communication protocol for all maintenance messages between client and server. Fileset delivery still uses the classic protocol, but messages like Fileset status or check-in now use the lightweight and fast delivery mechanism offered by NATS.
How
Please review the Boosters documentation. If you manage Windows or macOS systems in either a FileWave-hosted or on-premise environment, one or more Boosters are optional but often recommended, especially when many clients share a LAN or VPN path. Boosters can minimize server and WAN traffic by caching Filesets and application installers closer to clients; in hosted deployments this also reduces traffic from the hosted FileWave server. For Windows devices, Boosters can also cache Microsoft OS updates and patches. For Apple OS updates and upgrades on macOS, iOS, and iPadOS, use Apple Content Caching instead. If you use Boosters for server-message routing, ensure that "Route server messages via boosters." is enabled in your Superprefs or Custom FileWave Client.
No comments to display
No comments to display