When I started installing Afaria for the first time, I got confused about the order to install various components and did not know what each component would do. Below article is aimed to help beginners to understand about various Afaria components and their description.
Afaria Installation medium contains a bunch of components which needs to be installed to have a fully functional Mobile Device Management Solution. Below is the order of installation indicated with numbers with brief description of each component.
1. Afaria Server
The Afaria Server is the core Mobile Device Management component which performs the device management tasks. Afaria Server can be installed as a standalone Server or as a Server Farm. Afaria Server doesn’t contain any User Interface.
2. Afaria API Server
Afaria API server exposes the Administration API which is used by Afaria Admin UI and it allows user to create custom Admin UI
3. Afaria Admin UI
The Admin UI is a HTML5 based web interface to that allows user to perform configuration on the Afaria Server and to manage Afaria devices. The new UI is designed to support different browsers like IE, Safari, Chrome, Firefox, etc.
4. Enrollment server
The Enrollment Server takes care of device onboarding by delivering the respective Enrollment policies. This component is used for delivery management payloads ( policies configuration for iOS devices )
5. Portal Package Server
Portal Package server is used to manage and deliver Enterprise applications through Application policies.
6. End User Self Service Portal
EUSSP is a Web portal for Afaria device users. It allows user to view the devices, enroll device and perform few administration like password reset, etc.
7. Email Server
Email Server is a Powershell Service for access control which will be polling the Afaria Server for access rules/policies and deliver the details to the email proxies.