When installing and starting one or more TIBCO Streaming nodes, either in StreamBase Studio or at the command line with the epadmin command, the StreamBase Runtime opens multiple TCP and UDP ports for outgoing and incoming traffic. This is to provide channels for node communication and administration, and to allow node-to-node communication. These ports are required even when nodes are installed on a single machine using the hostname localhost.

To connect to a node running on a remote machine, the epadmin command allows you to specify:

Use a command like the following to determine a node's administration port:

epadmin servicename=nodename.clustername display node | grep Admin    [macOS, Linux]
epadmin servicename=nodename.clustername display node | findstr Admin [Windows]

If you have configured the node with a node-specific username and password, you may have to specify that those parameters as well.

Some development or server machines may experience port blocking by their firewall software. If it is not feasible to disable the local firewall, you can configure the firewall to allow incoming traffic as follows:

The following diagram shows how the required network ports are used to communicate between nodes and administration clients.

Configure node port settings in the NodeDeploy root object of the node configuration configuration type. These settings are described in more detail in the Runtime Admin Guide [cross-ref], as follows: