Setting Nerada Connection - AFS

AFS Installation and Administration Guide

Product
AFS
AFS_Version
7.10
Platform
RHEL
Category
Reference Guide

It is crucial to set the connection with Nerada database:

This configuration is done for each front or indexer in the conf.xml configuration file located in the /usr/local/afs7/conf/ folder.

To configure the connection between AFS platform and the Nerada database

Edit the conf.xml configuration file, for each front and indexer, located in /usr/local/afs7/conf/ and set the following parameter:

Whenever a setting is changed on a front, restart the Content Repository Manager by running the following command:

As root user

systemctl restart afs-crmanager.service

Example of a connectionString definition in the conf.xml file

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

Example 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:connectionString value="mongodb://my_nerada_mongo1:27017,my_nerada_mongo2:27017,my_nerada_mongo3:27017"/>
</afs:Mongo>
</afs:Nerada>
</afs:ContentRepository>
</afs:conf>

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

To enable afs_crep_deploy to write in the Nerada database

The Writing side of Nerada corresponds to the indexer.

Edit the conf.xml configuration file, for each indexer, located in /usr/local/afs7/conf/ and set one or both of the following parameters:

By default, afs_crep_deploy filter pushes to Nerada.

If both switches are off, then the afs_crep_deploy filter does not push anything and the following warning is provided: Neither Nerada nor legacy content repository was enabled on the write side, check your conf.xml

To enable the content repository fronts to read in the Nerada database

The Reading side of Nerada corresponds to all fronts associated with the database.

Edit the conf.xml configuration file, for each front, located in /usr/local/afs7/conf/ and set the following parameter:

  • ContentRepository/Driver: Determines which of Nerada (nerada) or Legacy Content Repository (reply_database) is responsible for responding to incoming queries

By default, the content repository fronts read only from the Nerada content repository.

Whenever a setting is changed on a front, restart the Content Repository Manager by running the following command:

As root user

systemctl restart afs-crmanager.service

It is possible to override the driver used to respond to content queries regardless of the one currently configured using the cr_driver query parameter.