MediaBeacon R3Search is a faceted search engine organically integrated into MediaBeacon. It intuitively identifies relationships across a large data set and presents assets via facets arranged in a separate widget.
Each field in MediaBeacon can be presented as a browse facet in R3Search. Facets can be arranged on a per-group basis, so a particular business unit can interact only with the data that is relevant to their workflow. Please refer to the Widget Manual for more details on how to set it up.
R3Search is automatically enabled for every ACL. R3Search uses a single index for the entire repository, in addition to an index for administrative metrics. Metrics tools are described in the Widget Manual.
Local R3Search Server
This button manually stops the R3Search index.
This button manually rebuilds the R3Search index from asset metadata.
This button manually rebuilds the index used for administrative metrics.
This button opens the R3Search console, which can be used to look up information about a particular asset in a given R3Search index or to run queries. This is generally used for troubleshooting. The console can also be accessed in the MediaBeacon web interface from “Manage > R3Search.” For full documentation, please visit: http://lucene.apache.org/solr/
Refresh buttons refresh appropriate lists and drop-downs.
Zookeepers & Distributed Search
Zookeepers are part of MediaBeacon’s increased support for distributed searching. Administrators can set up an array of R3Search servers and Zookeeper servers to distribute the search load across the network. Zookeepers dynamically route search requests to the R3Search servers, which then process them. If a particular R3Search server becomes unresponsive, the Zookeeper will automatically reroute requests to a different server, avoiding outages for the end user. A given server array may contain multiple R3Search servers and multiple Zookeepers.
R3Search + Zookeeper
Allows the server to function as both a R3Search server and a Zookeeper. This server will process search requests, as well as route additional requests to other R3Search servers.
The server will only process search requests. It will not route search requests to other R3Search servers.
The server will only route search requests to other R3Search servers. It will not process the requests.
Zookeepers are whitelisted in the same way as external applications, which is described in the section “External SOA Applications.” All servers in the cluster—both R3Search and Zookeepers—must have the same set of Zookeepers listed. A Zookeeper must be running at each of the addresses specified in the list. If any listed Zookeepers are missing or aren’t running, the cluster will wait for them to start before serving requests.
Number of Shards
This option sets the number of shards to use for the R3Search index.
Sharding is a back-end function that splits the R3Search index into multiple segments, or “shards,” which can then be assigned to specific R3Search servers. This decreases response time, as the R3Search servers will only have to search their particular shard, rather than the entire index. Additionally, multiple R3Search instances can be assigned to a particular shard, which adds redundancy and stability to the index.
Automatically Start Local R3Search
This checkbox automatically starts R3Search at the same time as the MediaBeacon server.
This button brings up a new window with logs showing application status.