How to export and import a Glink configuration file
When you have spent time on customizing Glink for your equipment, server applications ad your requirements in general, you probably want to export your current set of configurations for back-up purposes or to share them with other users. This can be done in two ways.
​
Send configuration file by E-mail from your Android device
The Export configurations function is an choice in the action bar drop down menu. You will be asked if you want to include Connect macros before you are taken to the Send Mail function with your configurations attached to the message. The configurations are sent as a file-attachment named config.glinki.
​
Export the configuration file to file system
You can also Export your configuration to the Download folder on your device from the Sessions menu. Glink will display the file path when the file is exported, for example /storage/emulated/0/Download/config.glinki (Android 7, 8, 9, 11), /storage/emulated/0/Documents/config.glinki (Android 12 and above) or /storage/emulated/0/Android/data/no.gar.glinkXX/files/config.glinki (Android 10). Now you can use a File manager to copy the file or you can connect the device to a personal computer and use a File manager on the personal computer to copy the file from your device.
​
How to import a configuration file
The filename-extension .glinki is associated with Glink. This means that if you receive a Glink configuration file as an e-mail attachment and export it to the file system, you can import it into Glink by tapping the file. Glink will be started and inform you that you have received a new set of Glink configuration files. If you tap the Install button to install it, you will get a new set of configurations that will replace your current configurations. All your current configurations will be overwritten and lost.
​
From the Sessions menu you can also manually Import a configuration file that you have downloaded to the device, using the file picker, or put on a web server, by specifying the URL to this file.
Auto-import
Another possibility is to use the Auto-import feature. Glink for Android always checks the following path for a new Glink configuration file at start-up and when the user enters the Sessions menu:
/enterprise/usr/config.glinki (Only devices from Zebra and Point Mobile)
​
/SD Card/Android/data/no.gar.glinkXX/files//import/config.glinki
(Where XX is either vt ,5250, 3270 or omitted for the full version)
The "SD Card" folder (sometimes also referred as Phone Storage or Internal Storage) is often addressed like "/storage/emulated/0". For example:
/storage/emulated/0/Android/data/no.gar.glinkvt/files/import/config.glinki
/storage/emulated/0/Android/data/no.gar.glink5250/files/import/config.glinki
/storage/emulated/0/Android/data/no.gar.glink3270/files/import/config.glinki
/storage/emulated/0/Android/data/no.gar.glink/files/import/config.glinki
If/when Glink finds a config.glinki file in the import folder, the file will be imported and renamed to config.glinki_nn in the import folder. This is to make sure it is only imported once. nn is the next available number. The current configuration will be overwritten by the imported configuration file and lost.
​
The export and import functions allow administrators to prepare and customize configurations for a large group of users and distribute the configurations.
​
​
