TermWeb 4 Requirements

Server hardware requirements

Minimum system requirements

Minimum requirements for TermWeb application. Requirements do not include requirements for database server.

• 3GB RAM for Linux, for Windows 4GB (6 GB recommended or more depending on usage and size of termbase)

• 2 GB hard-disk space for installation. Plus extra space for storing log files (this space depends on usage, logging level and storage policy of logs). Don’t include Operating System disk space requirements.

• When user uploads files to TermWeb it stored in database by default.

Server software requirements

Java Virtual Machine

Servlet Engine

Database support

TermWeb supports any of the following databases:

• MySQL 8.0.x

Elasticsearch Server

• For TermWeb versions since 4.0.9-4:
  You may choose any supported version of Elasticsearch depending on your company requirements.

  • Elasticsearch 7.17+
    https://www.elastic.co/guide/en/elasticsearch/reference/7.17/install-elasticsearch.html

    • Install plugin for it bin/elasticsearch-plugin install analysis-icu

    • In most cases for Elasticsearch process will be enough 1GB of jvm heap size.
      See https://www.elastic.co/guide/en/elasticsearch/reference/7.17/advanced-configuration.html#set-jvm-heap-size

    • Only staging areas rely on elasticsearch, so there is no need to create failover setup with two nodes.
      See https://www.elastic.co/guide/en/elasticsearch/reference/7.17/bootstrap-checks.html#single-node-discovery

    • Elasticsearch server may send to TermWeb logs warnings recommending to configure secure connections. If your Elasticsearch is not exposed to internet and secure enough, you may disable this warning by adding next configuration xpack.security.enabled: false to elasticsearch.yml. Otherwise follow to elasticsearch recommendations https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minimal-setup.html

    • We don’t use any geographical search, so you may want to disable downloading of geoip database: https://www.elastic.co/docs/reference/enrich-processor/geoip-processor

    • An examplle of added options to a configuration file elasticsearch.yml:

      xpack.security.enabled: false ingest.geoip.downloader.enabled: false cluster.name: termweb4-es discovery.type: single-node

  • Elasticsearch 8+
    https://www.elastic.co/guide/en/elasticsearch/reference/8.18/install-elasticsearch.html

    • Install plugin for it bin/elasticsearch-plugin install analysis-icu

    • In most cases for Elasticsearch process will be enough 1.5GB of jvm heap size.
      See https://www.elastic.co/guide/en/elasticsearch/reference/8.18/advanced-configuration.html#set-jvm-heap-size

    • Only staging areas rely on elasticsearch, so there is no need to create failover setup with two nodes.
      See https://www.elastic.co/guide/en/elasticsearch/reference/8.18/bootstrap-checks.html#single-node-discovery

    • Elasticsearch v8 comes with stricter security policy than v7. It uses https for connections by default. During first launch save default user password and certificate fingerprint. If your Elasticsearch is not exposed to internet and secure enough, you may disable user authentication by adding next configuration xpack.security.enabled: false to elasticsearch.yml. For reference see https://www.elastic.co/guide/en/elasticsearch/reference/8.18/security-minimal-setup.html

    • We don’t use any geographical search, so you may want to disable downloading of geoip database: https://www.elastic.co/docs/reference/enrich-processor/geoip-processor

    • An examplle of added options to a configuration file elasticsearch.yml:

      ingest.geoip.downloader.enabled: false cluster.name: termweb4-es discovery.type: single-node

  • Elasticsearch 9.0.x
    We did initial tests of our functionality and can confirm that TermWeb can work with v9. Configuration is the same as for v8.

  • Cloud versions
    TermWeb’s Elasticsearch client supports specification of API key for cloud installations. See TermWeb configuration (termweb.properties)
    
    

• For TermWeb versions before 4.0.9-4:

  • Elasticsearch 7.16.x
    https://www.elastic.co/guide/en/elasticsearch/reference/7.16/install-elasticsearch.html
    In most cases for Elasticsearch process will be enough 1GB of RAM.
    Only staging areas rely on elasticsearch, so there is no need to create failover setup with two nodes.
    Install plugin for it bin/elasticsearch-plugin install analysis-icu
    
    

• For TermWeb 4.0.8 and earlier:

  • Elasticsearch 7.3.x
    Required: to avoid CVE-2021-44228(log4shell) vulnerability set the Elasticsearch JVM option -Dlog4j2.formatMsgNoLookups=true and restart each node of the cluster, see documentation https://www.elastic.co/guide/en/elasticsearch/reference/7.3/jvm-options.html

Client requirements

Supported browsers

• Edge (last two major versions on day of release)

• Firefox (last two major versions on day of release)

• Chrome (last two major versions on day of release)

• Safari (last two major versions on day of release)

• Internet Explorer 11 or later (Deprecated since the release of TermWeb 4.0.9)

Minimum requirements

• Screen size: 800 x 600 (recommended 1024 x 768)

• Network speed: 128 Kbits/sec (recommended 512 Kbits/sec)

• Javascript and cookies enabled in web browser