If you install Flow Director from a
zip archive, you need to have Java 8 or later installed on your machine.
You can check the version with
If you use Flow Director as Docker image, you will need to have docker and docker-compose installed.
Installation from a
After download you need to unpack the archive. Then go to
For Unix-based systems execute
On Windows systems execute
Flow Director then displays this startup message:
Starting Flow Director ... Please wait about 20 secs before you connect to http://localhost:8080
Running Flow Director as Docker Image
Use the GitHub repository edgebroker/flowdirector-docker.
Follow the instruction in the repository's
README file to get Flow Director up and running within 2 minutes.
Scaling Flow Director / Connect to an existing SwiftMQ Router [Network]
Flow Director can be scaled up by just adding more SwiftMQ Routers and connecting the embedded router to the new
routers. This automatically builds a network and all nodes are available for flow orchestration and client connections.
All routers that are part of the network must have different names. The name of the embedded router is
A router network are SwiftMQ Routers connected and reachable by each other. They can be directly connected or indirectly via other routers. There can only be a single Flow Director per router network that manages it.
Flow Director can connect to an existing SwiftMQ Router (or a network of routers) by using the
Explorer app and creating
a routing connector from the internal router to the remote router.
Another and much smarter way is to create a dedicated flow per remote router with
CLI flow components to create that routing connector
on flow start and remove it on flow stop. This allows you to dynamically connect to different, may be
standalone, routers or all at once.
A third way is to create a routing listener in the embedded router via
Explorer app and let the new routers connect to
the listeners. This is more dynamic as remote routers can just connect without changing the configuration of the embedded
Please note that the remote SwiftMQ Routers must be of release 12.1.0 or later!