Set the conf.xml File of the Indexing Server - Fluid Topics - 3.8

Install Fluid Topics on Multiple Servers

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

To configure the communication with the Back Office server

The conf.xml Configuration File is required to indicate where is the server hosting the Back Office. This way, the Indexing server is able to communicate with the Back Office Administration Center when installing the processing pipelines.

  1. Edit the following file:

    As root user

    /usr/local/afs7/conf/conf.xml

  2. Add the lines regarding the Administration Center as follows:

    <?xml version='1.0' encoding='iso-8859-1'?>
    <afs:conf xmlns:afs="http://ref.antidot.net/v7/afs#">
    <afs:AC>
    <afs:Server>
    <afs:host value="$BACK_OFFICE_HOSTNAME"/>
    <afs:UpdateManager>
    <afs:host value="$BACK_OFFICE_HOSTNAME"/>
    </afs:UpdateManager>
    </afs:Server>
    </afs:AC>
    <afs:BO>
    <afs:Server>
    <afs:apiKey value="$BACK_OFFICE_USER_API_KEY"/>
    </afs:Server>
    </afs:BO>
    </afs:conf>

    Where $BACK_OFFICE_HOSTNAME is the hostname of the server hosting the Back Office Environment set as a name attribute.

To configure the connection between Fluid Topics and the Nerada database

The conf.xml Configuration File is required to indicate where is the server hosting the Nerada database.

  1. Edit the following file:

    As root user

    /usr/local/afs7/conf/conf.xml

  2. Add the lines regarding the Nerada database as follows:

    <afs:conf
    xmlns:afs="http://ref.antidot.net/v7/afs#">
    <afs:ContentRepository>
    <afs:Driver value="nerada"/>
    <afs:Nerada>
    <afs:Mongo>
    <afs:connectionString value="mongodb://$NERADA_MONGO_HOSTNAME:27017"/>
    </afs:Mongo>
    </afs:Nerada>
    </afs:ContentRepository>
    </afs:conf>

    Where $NERADA_MONGO_HOSTNAME is the hostname of the server hosting the Nerada database. Its default value is localhost.

Case of a connectionString definition in the conf.xml file if several hosts are in the cluster

<afs:conf
xmlns:afs="http://ref.antidot.net/v7/afs#">
<afs:ContentRepository>
<afs:Driver value="nerada"/>
<afs:Nerada>
<afs:Mongo>
<afs:afs:connectionString value="mongodb://$NERADA_MONGO_HOSTNAME1:27017,$NERADA_MONGO_HOSTNAME2:27017,$NERADA_MONGO_HOSTNAME3:27017"/>
</afs:Mongo>
</afs:Nerada>
</afs:ContentRepository>
</afs:conf>

For more information on the connectionString parameter, see the MongoDB documentation.

For these modifications to be taken into account, it is mandatory to restart the PaF Manager by running the following command:

As root user

systemctl restart afs-pafmanager.service

In our example, add the following lines:

<?xml version='1.0' encoding='iso-8859-1'?>
<afs:conf xmlns:afs="http://ref.antidot.net/v7/afs#">
<afs:AC>
<afs:Server>
<afs:host value="bo01" />
<afs:UpdateManager>
<afs:host value="bo01"/>
</afs:UpdateManager>
</afs:Server>
</afs:AC>
<afs:LogManager>
<afs:storages>
<afs:listItem value="sqlite" />
<afs:listItem value="text" />
</afs:storages>
</afs:LogManager>
<afs:ContentRepository>
<afs:Driver value="nerada"/>
<afs:Nerada>
<afs:Mongo>
<afs:connectionString value="mongodb://oleandor_nerada:27017"/>
</afs:Mongo>
</afs:Nerada>
</afs:ContentRepository>
</afs:conf>