Multiple-Server Installation - Fluid Topics - 3.8

Install Fluid Topics on Multiple Servers

Product
Fluid Topics
FT_Version
3.8
Platform
RHEL
Category
Technical Notes
language
English
audience
public

A multiple-server installation consists in installing Fluid Topics on several servers in order to distribute the load and/or provide redundancy for critical components. By default, these servers are located in a single data center. Upon request, it is possible to distribute a multi-server installation across several data centers in different regions of the world. For more information, see Global Presence.

The following table identifies the components which can be installed on several servers:

Environment

Components

Description

Reply Environment

Query Manager, Autocomplete, Spellcheck, Content Repository, Click

Redundancy-ready

Web Server

Play

Redundancy-ready

Indexing Environment

Can be distributed across several servers

Back Office

BO Server, BO AC, UM

Database for user-related content

MongoDB

Redundancy-ready

Where:

  • QM = Query Manager
  • ACP = Autocomplete
  • AC = Administration Center
  • UM = Update Manager

All server combinations are possible.

Example

Consider a documentation portal based on the following multiple-server Fluid Topics installation:

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

The following picture illustrates this multiple-server Fluid installation:

FT_Multiinstall_schema

For more information about how to install servers, please consult Prepare AWS for a Fluid Topics Installation on Multiple Servers and Install Fluid Topics on Multiple Servers.

Example

All along this documentation, we will take the following example.

The OleanDor company's customers and coworkers often complain about their documentation:

"We can't find what we're looking for!"
"It is not pleasant to read. We have to switch pages all the time and pages take so much time to load..."

To solve these issues, the OleanDor company just signed with Antidot to install a Fluid Topics portal for their documentation.

To ensure a high-quality and easy access to their documentation portal, Fluid Topics will be installed on five servers:

  • front01 and front02: Fluid Topics and AFS Reply environment
  • idx01: AIF Indexing environment
  • bo01: Back Office environment
  • mong01, mong02, mong03 are clustered

My Stunning Company will provide the servers.

Here is the technical information they gathered in anticipation of the installation:

Server

  • Operating System: RHEL7 last update
  • Server architecture: multiple server
  • Repositories:
    • RHEL packages are located at the following URL: https://cdn.redhat.com/content/dist/rhel/server/7/
    • Antidot packages are located at the following URL: https://pkgs-oleandor.fluidtopics.net
  • To access the Antidot package repository, Antidot provided the following credentials:
    • login: my_login
    • password: my_password

Fluid Topics

  • Fluid Topics version: 3.5.18
  • Tenant:
    • Service: 1
    • Status: stable
  • Tenant ID: OleanDor
  • A logo file for the Fluid Topics tenant: my_logo.png

Configuration information

  • Customer name: oleandor
  • $MY_DATACENTER: my_datacenter

Emails

  • Emails sent from Fluid Topics must be sent from the following server: mail.oleandor.com. They must also be sent from the following sender: mail@fluidtopics.com

Content

  • The documentation is mainly written following the DITA standard.
  • Some old documents though are not yet structured and will be added to the portal in PDF format.
  • Some maintenance procedures will be created in FTML format.