TERR Server Ports in TIBCO Spotfire Server setup

TERR Server Ports in TIBCO Spotfire Server setup

To avoid network connectivity issues between Web Player nodes and TERR nodes appropriate ports need to be open between the TERR Nodes and Spotfire Server.

Default service communication ports are:
9501 - Web Player
9502 - TERR

The issue is that if you only open port 9502 between TERR service and Spotfire Server it will not work. Each and every new TERR service uses a separate port, unlike Web Player and Automation Services, for which port 9501 can be reused. 

Web Player and Automation Services instances communicate directly with the TERR Service, because of that port 9502 needs to be open between the TERR node machines. That is to say, for the TERR Server Edition default port (9502) needs to be open to computers running Spotfire Server, but it also needs to be accessible from any Nodes running Web Player or Automation Services. Thus the TERR Service runs on port 9502 by default - however, if you have other TERR services on the same node you need to add 1 to that port, e.g. 9503, 9504, etc. as each one needs to use a separate port. If multiple instances of TERR Service are installed across your nodes, they all effectively act as one unified pool of services. There is no affinity between a Web Player instance and a specific TERR Service instance. Why the port needs to be open between Web Player or Automation Services nodes and TERR nodes:
The initial request (to obtain a session) will go to the TIBCO Spotfire Server (TSS) to be routed to an available TERR Service node. However, following that initial request, all further communication (the job request and the data transfer) goes directly from the Web Player or Automation Services instance to the TERR service instance, specifically to avoid the unnecessary latency of proxying that communication through the TSS.