|
Filebox Service |
  
|
Filebox Service
|
Filebox Service |
|
Overview
The "Filebox" service allows for direct file exchange between the mobile devices and MCL-Mobility Platform - mobile devices are able to send data to a central location (rendering the implementation of in-house file servers to host data unnecessary).
The "Filebox" service includes a virtual storage and forwarding space for business files (= Filebox) which is organized into a shared and a private space. A shared Filebox is accessed by all the sites in the account. A private Filebox is only accessed by the site that created it.
The external back-end initiates a digest authentication by providing MCL-Mobility Platform with the intended username ( = ID number of the target account) and password (= "Filebox Password" generated in the "Service Passwords" tab of the "Account Details" sub-module. See "Service Passwords" tab.).
Once a recognized/authenticated connection is established between the external back-end and the MCL-Mobility Platform account, the external back-end calls a web service to provide the settings/credentials that have been defined in a back-end profile with an enabled "Filebox" service. See Back-end Profile Details.
This information is, then, used by MCL-Mobility Platform to identify the scope for the "Filebox" service, meaning, which areas the external back-end should have access to, be it the private Filebox of a specific site or the shared Filebox of the account.
Be aware that you must have a compatible back-end profile within your MCL-Mobility Platform account (= a back-end profile that includes the "Filebox" service and is associated to the intended site or to all the sites, as required) so it can be applied to your back-end requests. See Back-end Profiles.
Filebox (shared or private) is divided into two areas: Inbox (which includes incoming files from paired devices) and Outbox (a container for outgoing files).
In terms of your MCL-Mobility Platform account, this virtual storage/forwarding space is managed in the "Filebox" sub-module available in each site. See Filebox.
Workflow of the "Filebox" Service
The illustration below displays the flow of information that is implemented by the "Filebox" service between the account's back-end host, the MCL-Mobility Platform's Filebox (Inbox and Outbox areas) and a device's own Filebox (which also includes Inbox and Outbox areas).
|
Back-end Host - Generates and collects business data in the form of files. When required, it forwards files into the Outbox (an MCL-Mobility Platform's Filebox area) that are synchronized with devices included in a device group and/or the operators within an operator group. At the same time, the back-end host can retrieve business files from Inbox (an MCL-Mobility Platform's Filebox area) that were sent by the devices.
MCL-Mobility Platform's Filebox - A virtual space that consists of an Inbox and an Outbox area, which not only receives/stores files forwarded by devices (in Inbox) but also sends files to the devices (through Outbox).
Devices running MCL Applications - The emitters (via their Outbox) and receivers (via their Inbox) of business files. |
If required, you can implement mechanisms to automatically manage the retrieval and upload of files from the Inbox/to the Outbox areas of your MCL-Mobility Platform account:
•a Windows Service (installed in the intended external back-end system(s)). Check for more details in our Knowledge Base.
OR
•an MCL.Net Library (integrated in your back-end application(s)). Check for more details in our Knowledge Base.
OR
•a Java Library (integrated in your back-end application(s)). Check for more details in our Knowledge Base.
Make sure you register/log in to our MCL Community to access our Knowledge Base.
Feel free to contact MCL Support for more information on each option.
