Version: 2024.1.2

Overview

Server Requirements​

Hardware​

Detailed description see: Elastic Hardware

  • Memory
    • Minimum: 8GB
    • Recommended: >= 16GB
  • CPU
    • Same as inPoint Server Requirements
  • Disk
    • Minimum: High performance server disks (15k RPM)
    • Recommended: SSD
  • Network (when clustered)
    • 1Gbit Ethernet

Software - ElasticSearch​

Software - inPoint.Indexer​

  • Same requirements as the inPoint.Server
  • Elasticsearch 7.17.8 (Same or different environment)

Elasticsearch and Kibana​

Elasticsearch is an open source search engine based on the Java Library Apache Lucene. The program searches and indexes documents of different formats, saves the search results in a NoSQL format (JSON) and outputs them via a RESTful web interface.

Kibana is also an open source software that runs on the search engine Elasticsearch. It enables the search and visualization of the data contained in Elasticsearch indexes.

X-Pack is a package that contains multiple extensions (Security, Alerting, Monitoring, Reporting, Graph, Machine Learning) for Kibana. We mainly use "monitoring" to monitor the status of the indices.

Please check this to see all informations related to the license.

Text Analyze​

The analyzers is the part of ElasticSearch which transforms the text and the metadata of a document or folder into searchable terms. The text will be broken into smaller parts (tokenization) and these parts are then brought in a standard format (normalization). The same rules which apply during indexing will also be used during search for the text entered by the user.

The user can use any of the predefined Elasticsearch Analyzers or any custom analyzer (see Indexer Settings).

Important:
The goal of the process is to find relevant matches and not only exact matches, this can cause undesirable side effects. Names, abbreviations, identifiers or wildcard searches (where only a part of a word is present) may not work properly with linguistic normalization. In this case it's better to not use linguistic and use the standard analyzer.

When searching for specific fields an exact search can always be done.

The analyzer is set during the creation of the index and can't be changed later. Its is only possible to create an index with the desired setting and use the reindex api to copy all data (see also the example in the migration documentation).