Packages to Install - ABO

Install the Back Office and the Update Manager

Product
ABO
AFS_Version
7.9
Category
Technical Notes

The user used for AFS execution will be asked during installation process. If it des not exist, it will be automatically created.

The following steps require super-user privileges.

Debian Back Office installation

Run the following command:

apt-get install antidot-bo

RHEL Back Office installation

Run the following commands:

yum install antidot-bo
yum install antidot-afs-httpd

antidot-bo is a meta-package containing all necessary dependencies for Back Office execution (Portal, Web Services, Administration Center, Analytics). It installs the following packages:

  • antidot-bo-server
  • antidot-bo-portal
  • antidot-bo-portal-lighttpd (Debian only)
  • antidot-bo-ac
  • antidot-bo-analytics

Debian installation check:

dpkg -l | grep antidot

RHEL installation check:

yum list installed | grep antidot

The Back Office components share the same root directory: /usr/local/afs7

The following example shows a typical directory structure for a Back Office installation:

/usr/local/afs7
.
├── bin
├── bo-ac
├── bo-server
├── conf
├── contrib
├── lib
├── logs
├── meta
├── mongodb
├── scripts
├── setup
├── share
├── tmp
├── var
└── Version

The Back Office file structure includes the following directories and files:

  • bin is the directory for binaries.
  • bo-ac is the directory for the Administration Center specific files.
  • bo-server is the directory for Back Office server specific files.
  • conf is the directory for configuration files.
  • contrib is the directory for third-party libraries.
  • lib is the directory for AFS v7.9 libraries.
  • logs is the directory with every AFS v7.9 log. Some logs (acp*, search*, click*) are execution logs and are logged as database, usable by the Antidot Back Office. The other logs (afs_*.log) are system logs coming from the running daemon (acp, logmanager or querymanager).
  • meta is the directory used to store filter and switch files.
  • mongodb is the directory for Mongo DB-related data.
  • scripts is the directory for the scripts used to drive the daemon, to manage user rights, and so on.
  • setup is the internal repository used to store data concerning the installation (user, group, directory, and so on).
  • share is the directory for the different templates for lighttpd configuration and models for scripts, models for scripts and necessary data for Pipes and Filters (PaF) filters (such as indexing stemming dictionaries, named entity extract training databases and so on).
  • tmp is the directory used for temporary storage. Nothing persistent is kept here. Each time the Query Engine is launched, the directory data is reset.
  • var is the directory used to store the process ID of the running daemons. It contains internal data to run the daemons. Each time the Query Engine is launched, the directory data is reset.
  • Version is the file used to store the information about the AFS version.

Debian Update Manager installation

Run the following command:

apt-get install antidot-afs-updatemanager

RHEL Update Manager installation

Run the following command:

yum install antidot-afs-updatemanager

The Update Manager, Back Office, and Query Maanger have to be installed either on a dedicated server each, or all three of them on a sole server.