Distributing Glink configurations from an EMM/MDM

Glink has many configuration parameters that are available through the Settings screens in Glink. The configuration file can be exported and used as input for MDM distribution of Glink configuration parameters.

Glink configuration parameters can be set individually from the MDM server or the MDM server can set a Glink parameter that instructs Glink to download a complete configuration file from a network location. A combination of the two methods can also be used. In the latter case the configuration file will be downloaded before specific parameters are set to complement or override the parameters in the file.

Below you will find some examples on how you can distribute a Glink configuration file.

Use the following keys to trigger a download of a new configuration file

config.versionThis parameter specifies the version of the MDM parameters. If the version matches the version on the device, the rest of the parameters are ignored.
config.urlThis parameter provides the URL of the Glink configuration file. Please note that this parameter is ignored if the config.version parameter is missing or the version matches the version on the device

Here is an example: 

    config.version=2
    config.url=http://myhost.mydomain.xx/glink/group1/config.glink

Set up Glink configuration parameters directly

Glink can be configured directly from the MDM if the MDM supports managed app configuration. The MDM either use a menu to set the Glink parameters or it imports a JSON formatted configuration file containing the Glink parameters. The method and format vary with the different MDMs.

The following parameters are sufficient to create a host configuration with default values:

config.versionThis parameter (key-name) specifies the version of the MDM parameters. If the version number matches the version number on the device, the rest of the parameters are ignored.
config.nameThis is the name of the configuration (session) and must be provided. The configuration is created if it does not already exist. Additional parameters will be set for this selected configuration.
com.servernameThis specifies the IP address of your host

For example: 

    config.version=1    
    config.name=myhost
    com.servername=myhost.mydomain.com

For other parameters you have to check your exported Glink configuration file config.glinki. These parameters must be defined as parameter_key/parameter_value pairs. For example: 

    Parameter key 1_config.name / Parameter value myhost2
    Parameter key 1_com.servername / Parameter value host2.mydomain.com
    Parameter key 2_config.name / Parameter value myhost3
    Parameter key 2_com.servername / Parameter value host3.mydomain.com

Parameters for the first session, named with config.name, you do not need a prefix, but other sessions need a prefix. Session 2 parameters are prefixed with 1_, session 3 parameters are prefixed with 2_ and so on.

How you set these parameters will depend on your MDM. Different methods are used. While some MDMs present a menu with the parameters that can be set (MobileIron, Meraki, Intune), others require an JSON-/XML-file with key-name and key-value pairs.

Here are some examples:

MobileIron (iOS), Meraki (iOS), Intune.

General options

Parameters that are common to all sessions and configured in the General options menu, must be configured in a config.name named GeneralOptions, without a n_ prefix. For example: 
    Parameter key config.name / Parameter value GeneralOptions
    Parameter key screen.noautolock / Parameter value true

Passwords

Passwords are normally entered as the encrypted string you see in an exported Glink configuration file. Starting from version 2.4.3 you can also specify passwords in clear text if you use the prefix ##. For example the password that protects access to Settings, General options, New configuration, Export configurations and more: 
    Parameter key config.name / Parameter value GeneralOptions
    Parameter key screen.cfgpassword / Parameter value ##settingpassword
or the password for an auto-logon to IBM AS400/iSeries: 
    Parameter key config.name / Parameter value AS400
    Parameter key com.servername / Parameter value myhost.mydomain.com
    Parameter key com.ibm5250user / Parameter value username
    Parameter key com.ibm5250subspw / Parameter value ##as400password
    Parameter key com.ibm5250usealtlogin / Parameter value true

XML Schema

The AppConfig Community, supported by a collection of industry leading EMM solution providers, have defined a standard schema to configure apps. Using this definition, the Glink parameters can be specified in a XML document using the following syntax: 
    <managedAppConfiguration>
    <version>1</version>
    <bundleId>no.gar.glink5250</bundleId>
    <dict>
       <string keyName="config.name">
           <defaultValue>
                  <value>MyConfigName</value>
           </defaultValue>
       </string>
       <string keyName="com.servername">
           <defaultValue>
                  <value>MyServerAddress</value>
           </defaultValue>
       </string>
    </dict>
    </managedAppConfiguration>
Please note that the bundleId must match the Glink version you are using; either no.gar.glink5250, no.gar.glink3270, no.gar.glinkvt or no.gar.glink .