EBF Files is a solution that relies on the following components:
EBF Files Server
The EBF Files server is the middleware between mobile device and storage systems. It gets all requests from devices and forwards them to the storage. If the devices are authorized, the server receives containerized files from the storage and passes them to the mobile device.
The EBF Files server receives file requests from the EBF Files app and is responsible for forwarding them to the connected file systems. Before the requests are forwarded, they are converted to communication protocols understood by the file servers. As an example, an iOS device transfers settings via HTTP(S) protocol and the EBF Files server converts those into SMB format. The configuration of these interface parameters are stored in the EBF Files server database.
Additionally it is possible to combine EBF Files with proper tunnels and authorization for a more secure access to the files without manipulation.
EBF Files App
The EBF Files app is the client on the Android / iOS device where the files are being requested from. The app is used to request, receive, view, edit, upload and also offline-store files.
UEM System
The UEM System is the Device Management system which is needed for multiple features. The system can be used for simple deployment of the app to all devices, but also can be used to combine EBF Files with a tunnel and specific configurations for server access.
EBF Files Server Admin Portal
The EBF Files Admin Portal is a configuration point for file server connections and mobile devices.
File Server
The File Server is the directory with the needed folders, references and associated rights.
Active Directory
The AD is the directory for users, groups and associated access rights.
Database
EBF Files uses a database to store all configurations for organizations, domains and containers.
EBF Files serverless mode
Starting from app version 2.0.0 EBF Files can also be used in a serverless mode. This means, the app will work standalone and all configuration be provided via AppConfig parameters. Limitations are, that serverless mode does not support SMB containers, but only OneDrive and Sharepoint data sources.
For serverless mode you do not need a Files Server, an Active Directory or a database, just depending on a UEM system for the app parameters.