Configuring the TIBCO BusinessEvents DataGrid Listen URL
The listen URL is used for direct communication between the members of the metaspace. It is configured the same way for multicast and for unicast discovery (see Configuring the TIBCO BusinessEvents DataGrid Discover URL). The listen URL value must be different for each cluster member, so configure it at the PU level.
The listen URL uses this format:
tcp://interface:port[-EndPort |*]/
The cluster member binds to the specified interface and the specified port when creating the TCP socket. Specify the parameters as follows.
| Parameter | Notes |
|---|---|
interface |
To specify a value, use the desired IP address.
The value for interface must be the same in both the discovery and the listen URLs for a node. If there are multiple interfaces on one machine, specify the interface you want to use and do not rely on the default value. The default value for interface is the first available interface provided by the operating system for the machine. |
port |
To specify a single port use the port number in the listen URL, as shown in this example:
tcp://interface:6000/ You can use an auto-incrementing feature, as explained in Auto-incrementing Within a Range of Ports. The default value is the first available port in the 50000+ range. |
Multiple Nodes on One Machine
If multiple nodes (engines) are running on one machine, identify each uniquely. Use the same value for interface, but a different value for port for each node.
Auto-incrementing Within a Range of Ports
If a machine has blocked some ports in the default range, or if you want to use a different range, configure the listen URL to start with a specified IP address and port, and optionally provide an upper limit. If the specified port is not available, TIBCO API Exchange Gateway auto-increments the port until it finds an available port, up to the specified upper limit, if any. To specify a specific range use this format:
tcp://interface:Port-EndPort/
For example, given the following listen URL, TIBCO API Exchange Gateway attempts to open port 8000 and if it is not available it tries the next port number, until it finds an available port, up to 9000 (inclusive). If none is available, it keeps retrying. Make some ports in the specified range available so that the cluster nodes can start.
tcp://interface:8000-9000/
To specify a range with the upper limit of unsigned short minus one, use this format:
tcp://interface:Port-*/