Oracle WebCenter Analytics Communications

6-40 Oracle Fusion Middleware High Availability Guide

6.3.2.4 Oracle WebCenter Analytics Communications

Oracle WebCenter Analytics consists of individual Collectors which receive requests from Oracle WebCenter Analytics clients, such as Oracle WebCenter Spaces. This section describes how an Oracle Analytics Collector cluster works. In a clustered environment, producers clients of the collector and collectors are configured with a cluster-specific channel name. Each collector periodically broadcasts a heartbeat with its location to the cluster-specific channel. The producer listens to the channel for these collector heartbeats, and when it hears one, adds the collector to its list of known collectors. When the producer needs to send an event, it uses a round robin algorithm to select a collector from its list and sends the event to that collector. If a collector stops either being stopped purposefully or failing, it stops broadcasting a heartbeat. When the producer stops hearing the heartbeat it removes the collector from its list and stops sending events to that collector. If the producer does not hear any collector heartbeats, it does not send any events. Oracle WebCenter Analytics uses UDP and multicast on a configured set of ports to communicate with its clients. For a single node setup, the client is configured with a WLST command that has the server hostport location and simply transmits all events to this location via UDP. For a multiple node setup, the server is configured to broadcast via UDP multicast the locations of the various servers running on the cluster; the client is configured with the same WLST command, so it will receive the locations of these servers and keep the list of available servers in a list which is persisted in memory. Additionally, if a client does not receive a periodic heartbeat from a server to indicate it is functioning, it will remove that server from its list of known servers, and will cease sending events to it. Oracle recommends that Collectors be configured as unicast, forming a 1-1 relationship with the Oracle WebCenter Analytics client.

6.3.2.5 Oracle WebCenter State Replication