Configuration Options to Use Specific Ports and Network Interfaces

ActiveSpaces leverages TIBCO FTL internally to aid in connecting the different ActiveSpaces processes so that they can communicate over the network. In certain cases, you can specify additional configuration information when initially setting up the data grid processes to help influence what ports and network interfaces must be chosen when the processes are started.

For example, an ActiveSpaces client application might connect to an ActiveSpacestibdgproxy that is running on a server which has a firewall. In that case, a network administrator might open a specific port or ports in the firewall so that the TCP connections can be made to the tibdgproxy running behind the firewall. After the tibdgproxy is started, it reads from its data grid configuration what port it must bind to when listening for incoming TCP connections to ensure that traffic can pass through the firewall.