Exporting Keyboards to Devices using an Alternate MDM

To export keyboards to Wavelink Terminal Emulation using a mobile device management (MDM) software other than Wavelink Avalanche, you can use the Wavelink Configurator. This tool is based upon the Wavelink Avalanche service, but only allows you to create profiles and payloads for use on devices managed by another MDM.

With this tool, you can upload a keyboard bundle and associate a keyboard with a host profile, which you then export as a configuration file. The file can then be distributed using your MDM software, either as a configuration file deployed directly to the device for Android devices, or as a key-value pair that points to the configuration file for iOS devices to download.

You can configure multiple TE Host Profile Configuration payloads in a configuration file. You can only deploy one Productivity Pack Configuration payload to each device, which contains one keyboard bundle.

When you deliver a custom keyboard payload to mobile devices, all default keyboards in TE are overwritten and are no longer usable.

For the key-value pair on iOS devices, the Key is com.wavelink.configuration.url. The Value is the location for where you are hosting the Configuration.json file, whether it is a web server or network drive location, including the file name. Configuring with a key-value pair can only be performed on devices with iOS 7.0+.

To export keyboards to the TE Client when the device is managed by another MDM software:

3 From the Profiles tab on the left of the screen, click the Add Payload button in the Available Payloads panel.

4 The Payload dialog box appears. Select the iOS and Android option, and then the Productivity Pack Configuration payload to upload a keyboard bundle.

5 To use specific keyboards with a host profile, you must also create a TE Host Profile Configuration payload and add the desired keyboard tags. On each keyboard you can enter Keyboard Tags from the Editor panel of the Keyboard Editor, which are used in this payload. Only the custom keyboards on a mobile device containing the tags associated with a host profile payload are used during a session. When no keyboard tags are associated with a host profile, all keyboards will be used in their order of creation in the Keyboard Editor. If multiple keyboards share the same tags entered in this payload, keyboards are given priority based on their order of creation in the Keyboard Editor. For more information about keyboard tags, see Editor Panel.

6 Configure the options as desired and click Save. Repeat the previous steps as needed to create additional configuration payloads.

9 Enter a unique name for the profile, then select the payloads you want to include in the profile. Save your changes.

Your browser downloads the Configuration.json file. This file can be renamed as needed, though the new file name should always be reflected correctly within the key-value pair for iOS devices. After the key-value pair is deployed to the iOS device from your mobile device management software and the TE Client is launched, it downloads the configuration file from your web server and applies the new keyboard configuration.

If you are configuring for Android payloads, perform the steps below to complete the configuration process.

13 From a word processing application like Notepad, create a text file and name it TEConfigurationURL.xml.

14 Enter the following, substituting the URL value with the location of your configuration file on the web host:

15 Save the file and then place it on the Android device within the \sdcard\Wavelink directory.

When TE is launched on the Android device, it references the .xml file and downloads the configuration file to apply any new changes.

Was this article useful?

The topic was:

Inaccurate

Incomplete

Not what I expected

Other