Fluid Topics tenant installation - Fluid Topics - 3.7

Install Fluid Topics on Multiple Servers

Operating system
RHEL
Category
Technical Notes
Audience
public
Version
3.7

This section describes the procedure to follow in order to set up a tenant on a multiple-server (several machines) Fluid Topics environment.

Once all Fluid Topics components are installed, a {service ID - status} couple, also known as a tenant, must be configured to use Fluid Topics portals.

A tenant has an ID. It corresponds to the name given to the tenant configuration directory. It is case-sensitive.

A tenant is also identified by its Domain_Name. A domain name is generally related to the URL used to access the tenant's portal.

For example, the {1 - stable} tenant is identified by its domain name: doc.antidot.net.

The domain name of each tenant is the responsibility of the customer.

Fluid Topics tenant installation requires the following actions on the servers hosting the proper Fluid Topics environments:

  1. Tenant Configuration

    These steps must be performed on ALL servers (except servers hosting the MongoDB environment).

  2. Declare Project in the Back Office On any Servers

    These steps must be performed on the server hosting the Indexing environment.

  3. Install Tenants on Front Servers

    These steps must be performed on servers hosting the Reply environment.

  4. Configure Apache Virtual Host

    These steps must be performed on servers hosting the Reply environment.

  5. Install PaFs on The Data Processing Server

    These steps must be performed on the server hosting the Indexing environment.