Details for optimizing and configuring Global Search for TeamConnect can be found below. This information can be entered automatically into the TeamConnect properties file during the installer or manually entered into the teamconnect.properties file after installation.

 

 

Configuring the TeamConnect Properties File

Elasticsearch (Global search) parameters are able to be edited in the TeamConnect properties

file found in the WEB-INF folder.

 

The server address, name of the cluster, and indexing frequency are required for search to

function. The name of the cluster can be found in the Elasticsearch configuration file referenced here. The indexing frequency refers to how often (in seconds) TeamConnect will look for changes to existing, enabled indexed items and automatically update them. In the image below, the index will be scanned for modifications, additions, and entry removal every ten seconds.

 

The number of primary shards defaults to a value of '5'. Entering in any invalid character here will

thereby result in 5 primary shards.

 

The number of replica shards defaults to a value of '1'. Entering in any invalid character here will

thereby result in 1 replica shard.

 

Details on shards and replicas from Elasticsearch documentation:

An index can potentially store a large amount of data that can exceed the hardware limits of a single node. For example, a single index of a billion documents taking up 1TB of disk space may not fit on the disk of a single node or may be too slow to serve search requests from a single node alone.

 

To solve this problem, Elasticsearch provides the ability to subdivide your index into multiple pieces called shards. When you create an index, you can simply define the number of shards that you want. Each shard is in itself a fully-functional and independent "index" that can be hosted on any node in the cluster.

 

Note: The concurrent requests and bulk size for flushing requests are not required and do not

have default values.