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
├── java
├── lib
├── scripts
├── setup
└── share
The Back Office file structure includes the following directories:
- 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.
- java is the directory for Java files.
- lib is the directory for Back Office libraries.
- scripts is the directory for the scripts used to drive the daemon, to manage user rights, and so on.
- setup is the internal repository for installation-related data (user, group, directory, and so on).
- share is the directory for the different templates for lighttpd configuration and models for scripts.
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.