Понял. Спасибо.
воплощал вот это:
Цитата:
By installing two Data Director services you can dedicate the services to receiving and sending data. In this case we assume that each store has a Data Director installed which can both receive and send data. The configuration could look something like this:
DD_IN is the service responsible for receiving data from the stores. Since this is the only responsibility of that service we get faster updates in the Head Office database since we never have to wait for the transmission to the stores to complete. This service should be installed first and should run on the default Data Director ports. This is done to minimize the configuration necessary in the stores. If this service is not run on the default port we need to modify the service file in the stores to indicate that the DD_IN is running on a non-default port, which is work that we are not interested in doing.
DD_OUT is the service responsible for sending data to the stores. This service should have multithreaded forwarding enabled. This service needs to have it’s own entry in the services file since it’s not running on a default port. Note that you only have to change the services entry on the host running the Data Director and the Scheduler. The remote Data Directors will never connect to this service and therefore they don’t need to know on which port it is running on.
В данном случае Форвардер действительно не нужен. Достаточно развести двух директоров по разным портам.
Хотя узнать бы его назначение не помешало бы.