Skip to main content

ZeroMQ Replacement with NATS (End of Life)

What changed

FileWave replaced ZeroMQ with NATS across FileWave 14.8 through 15.0. Current supported releases use NATS; this page preserves the migration sequence for administrators reviewing old firewall rules or upgrade history.

Why the history still matters

ZeroMQ is being replaced withand NATS incarried internal communication and notifications between FileWave components. During the transition, a processmixed-version startingenvironment withcould v14.8.

use

When/Why

different

Thismessaging moveservices willon naturallydifferent occurconnections. whenWhen upgradingauditing an old configuration, match each firewall rule to the FileWave components where eventually NATS will replace ZMQ everywhere it is used.  This articleversions and releasecomponents notesthat willoriginally explainrequired what is migrated in each new version.  it.

ThisThe doestransition havechanged an impact on whatthe network ports are used inbetween FileWave.

FileWave

How

Server,

Central, PleaseClients, observeBoosters, ourand TCPIVS. portsUse KBthe current port article for additionalfirewall and deprecated ports.

    As of FileWave 14.8, NATS will be implementedconfiguration instead of copying a rule set from an older release.

    Historical migration sequence

      FileWave 14.8: NATS replaced ZeroMQ for AdminFileWave to Central-to-Server communication. InFileWave 14.9 the ZeroMQ features for clients is removed.9: NATS isreplaced used for allZeroMQ notifications between clientsClients, Server, and servers as well as boosters.Boosters. InFileWave 15.00: ZeroMQ is entirelywas removed and no longer used.completely.