The clients request a service id for processing their request

* During the initial message flow the client requests a service id from
  the Service Manager
* Service Manager replies to the client with a unique service request id,
  which the client uses in order to subscribe to the Service Manager's
  result publisher
* When a message arrives at the Service Manager's sink it is published
  on the result publisher socket with a topic set to the unique request
  id of the client
Bind the Result Publisher to a random port on the Service Manager

* Also, be more verbose when in debug mode
The service request id is part of the message which the backend agents receive
Subscribe the backend agents to the topics from the config file

* The backend agents also subscribe to topics related to the platform
  they run (e.g. FreeBSD, Linux, etc..) and their node name