SUMMARY:
This document discusses a question concerning the communication protocol and port number used by Strategy Narrowcast Server 9.x - 10.x when delivering file subscriptions.
QUESTION:
What is the communication protocol and port used by Narrowcast Server 9.x - 10.x when delivering file subscriptions?
ANSWER:
File deliveries in Narrowcast are handled exclusivley through the built-in Windows system. This means that there is no specific port that needs to be opened in order for Narrowcast to deliver file subscriptions over a network as the concept of a port is exclusive to tcp/ip communication.
The File Information Transmitter runs under the same Windows account as the Strategy Execution Engine service. If the Execution Engine is running under a Windows domain account, the File Information Transmitter can deliver files to any network machines for which this account has the required permissions.
One way to ensure that Narrowcast Server can deliver files within a network is to ensure that the Execution Engine is running under a Windows domain account that has permissions on all machines where delivery is required. In this way no other authentication needs to be defined. If a mapped network drive is used to deliver files to networked computers in the Windows file system, the Windows account under which the mapped network drive is created must be the same as the administrative account for Narrowcast Server.
In summary, the API that Narrowcast uses for file deliveries is the native Windows API which does not make use of ports.
