The Central File Store and the Central File Server are used to store and distribute files that are associated with payloads. For example, .apk files in Software Payloads or OS update files could be stored in the Central File Store.
When you deploy a payload with a file associated with it, the smart device server receives a list of the files that it needs. The smart device server connects to the Central File Server and requests the files. The Central File Server connects to the File Store and sends the files to the smart device server. When the device checks in, it downloads the files from the smart device server. For more information about software payloads, see Software Payloads (Android/iOS).
By default, Avalanche locates the Central File Store on the same computer where the Enterprise Server is installed. However, you may choose to use a network drive or other location for storing files.
If a device checks in before the smart device server has finished retrieving the files, the server tells the device to try again in a few minutes.
The following sections provide guidance on when and where to use the Central File Store.
When you use a manifest URL, all of the devices retrieve files directly from the location listed in the payload. This may not be practical if large files are pushed out to many devices simultaneously or if the network connection is low-quality.
When you use the Central File Store, the devices retrieve files from the smart device server they have been configured to connect to. When you have several smart device servers, this spreads traffic out to several servers. Using the Central File Store may also reduce reliance on a poor network connection.
How many files will be stored and their size are the most important factors in deciding where the Central File Store should be located. Some files, such as OS updates, can be very large. If you have a lot of files or if your files are very large, consider using a separate location for the Central File Store. If you don't have many files or if your files are small, you may want to keep the Central File Store in the default location for ease of management.
You must have a certificate for the server where the Central File Store is located. If you set up the Central File Store in the same location as a smart device server, you can use the same certificate for both.
After upgrading to Avalanche 6.2, device enablers must be upgraded to 6.2.0.273 or newer to work with the Central File Store and receive new or migrated file payloads.
1.Create a software payload for the new Avalanche device enabler using a manifest URL.
2.Add the payload to a profile and deploy it to devices. Devices connect to Avalanche using the new enabler and can receive files from the Central File Store.
Using the Central File Store for a pre-6.2 payload
In previous versions of Avalanche, files were stored in the database. The upgrade process does not move those files out of the database, and they need to be moved manually after upgrading to Avalanche 6.2. After moving the files to the Central File Store, payloads can be edited to use the hosted files.
1.Configure the Central File Store.
2.Move the payload files into the Central File Store.
3.Edit the payload by clicking its name in the Available Payloads panel and selecting the desired file from the Central File Store.
4.Save the payload.
Use the following sections to configure the Central File Store and manage files.
All users with administrator privileges can edit the Central File Store settings, regardless of their home location.
The default port for the Central File Store is TCP 9000, but the port number may be configured during installation.
The Central File Store has the following configuration options:
FileStore UNC path
A network path to the location where you want the Central File Store. This path should be a dedicated path for the File Store. By default, this field is populated with a path local to the Enterprise Server. If you change this path after you begin storing files, everything in this folder is moved to the new location.
Mapping Username
A username associated with an account that has permission to access the network location. This account is used to retrieve files from the File Store. The account must have write permissions, not read-only permissions.
Mapping Password
A password associated with an account that has permission to access the network location.
Certificate Store (PFX/P12)
A certificate associated with the public address of the location of the Central File Store. If you have the Central File Store located at the same address as a smart device server, you can use the same certificate for both.
Certificate Store Password
The password associated with the certificate.
Public Server Address
The address and port for the Central File Store.
To edit the Central File Store settings:
1.Click Tools > Central FileStore.
2.Configure the settings for the Central File Store.
Add files to the Central File Store either directly, using your preferred file browser and adequate credentials, or through the Avalanche Console. You must have administrator permissions in Avalanche in order to manage files in the Central File Store through the Avalanche Console.
To manage files in the Central File Store with the Avalanche Console:
1.Click Tools > Central FileStore.
2.In the top right, click the Manage FileStore button.
3.Use the buttons at the top of the dialog to create directories, rename files, delete files, import files, export files, view file details, and refresh the Central File Store. Changes are automatically saved as you make them.
4.Click the X in the top right corner to close the dialog box.
If you replace a file with another file that has exactly the same name, the next time you do a deployment, the new file will be distributed to the smart device server. However, when you delete or rename files in the Central File Store, be sure to update any payloads using those files. The associated payloads do not update automatically.
Why should I use the Central File Store instead of manifest URLs?