Multiple-Server Installation - Fluid Topics - 3.4

Fluid Topics Installation and Administration Guide

Product
Fluid Topics
FT_Version
3.4
Platform
RHEL
Category
Reference Guide

A multiple-server installation consists in installing Fluid Topics on several servers in order to distribute the load and/or to provide redundancy for some critical components more efficiently.

The following list shows an example of how all components can be installed on several servers to provide redundancy:

  • Reply Environment (QM (Query Manager), ACP, Spellcheck, Content Repository, Click) - redundable
  • Web Server (Play) - redundable
  • Indexing Environment (can be distributed over several servers)
  • Back Office (Back Office Server, Back Office AC (Administration Center))
  • UM (Update Manager)
  • Database for user-related content (MongoDB) - redundable

All server combinations are available.

This documentation is based on the following multiple-server Fluid Topics installation:

  • Two Front servers linked by a Load Balancer to provide redundancy
    • Reply Environment (QM (Query Manager), ACP, Spellcheck, Content Repository, Click)
    • Web Server (Play)
  • One Indexer server
    • Indexing Environment
  • One Back Office server
    • Back Office (Back Office Server, Back Office AC (Administration Center))
    • UM (Update Manager)
  • One MongoDB environment hosting three clustered servers

The following picture shows the schematic example of this multiple-server Fluid Topics installation:

FT_Multiinstall_schema

For more information about the preparation of proper servers, please consult Prepare AWS for a Fluid Topics Installation on Multiple Servers.

For more information about how to configure a multiple-server installation, see Install Fluid Topics on Multiple Servers.