Legacy ActiveSpaces Cluster Member Discovery

There are two methods you can use to configure how the members of the Legacy ActiveSpaces cluster are discovered: multicast and well-known addresses.

By default, multicast is used, and in many cases default multicast values work without additional configuration.

For more information on cluster configuration, see TIBCO BusinessEvents Configuration Guide.

For TIBCO FTL cluster, the member discovery is handled internally by TIBCO FTL, see TIBCO FTL Documentation.

Cluster Member Discovery Using Multicast Discovery

If multicast is used, the cluster membership is established using the multicast IP address and port. When a TIBCO BusinessEvents processing unit (node) subscribes to this multicast IP address it broadcasts information about its presence to the address.

Multicast is used to discover new processing units (nodes) and add them to the cache cluster. Similarly when nodes are removed or moved to a different server, the multicast protocol ensures that members are kept current without any additional configuration.

Default values provided mean you may not have to configure any discovery-related properties. However, if you deploy multiple TIBCO BusinessEvents projects in your environment, you must specify different multicast address and port settings for each project.

Cluster Member Discovery Using Well-Known Addresses

When multicast is undesirable or unavailable, for example, if nodes are deployed to different subnets and broadcast between the subnets is not enabled, use well-known addresses (WKA) instead.

To use well-known-addresses you provide the IP addresses and ports of certain members to all potential, using CDD settings.

The disadvantage of well-known addresses is that configuration is somewhat fixed, and at least one of the well-known-address members must be running at all times so that new members can join the cluster.