DataWedge configurations can be deployed to devices either manually or via mass deployment. There are 2 methods for secure mass deployment: StageNow or EMM (Enterprise Management Mobility).
Generate DataWedge configuration file(s) as follows:
- Configure DataWedge as desired on a device.
- Create a DataWedge profile, specifying how to acquire, process, and output data.
- To distribute DataWedge configurations including multiple profiles and settings, export the config file (
- To distribute a single DataWedge profile, export the profile (
dwprofile_[profilename].db, where [profilename] is the name of the profile).
After fulfilling the prerequisites to generate the DataWedge configuration file(s), select one of the following methods of deployment.
To deploy the DataWedge configuration file manually:
- Copy the DataWedge configuration file to the target device, e.g. the SD card folder.
- Import the file by browsing to the folder location and selecting the file.
There are 2 methods for mass deployment of DataWedge configurations:
- Using StageNow - create a StageNow profile and generate the barcode to scan and deploy the configuration:
- Host the DataWedge configuration file on an FTP or HTTP server.
- Create a StageNow profile to:
A. Select one of the following:
(a) If using auto import, copy the configuration file from the host server to the auto import folder on the device as follows: Using File Manager CSP, specify the source file path, the path of the configuration file on the host server. Specify the target file path, using the Auto Import feature:
(b) If using a specific folder location, copy the configuration file from a specific location accessible by DataWedge as follows: Using File Manager CSP, specify the source file path, the path of the configuration file on the host server. Using DataWedge Manager CSP, import the configuration file from a specified path.
B. Generate the staging barcode.
- Scan the generated barcode with StageNow client on the device.
- Using EMM - select one of the following methods:
- Push the DataWedge configuration file to the auto import file path
/enterprise/device/settings/datawedge/autoimporton the device to automatically import the configuration.
- Use StageNow to export for EMM:
- Select one of the following:
A. If using auto import, copy the configuration file from the host server to the auto import folder on the device as follows: Using File Manager CSP, specify the source file path, the path of the configuration file on the host server. Specify the target file path, using the Auto Import feature:
B. If using a specific folder location, copy the configuration file from a specific location accessible by DataWedge as follows: Using File Manager CSP, specify the source file path, the path of the configuration file on the host server. Using DataWedge Manager CSP, import the configuration file from a specified path.
- Export the .XML for EMM.
- Push the .XML generated to devices using EMM.
- Push the DataWedge configuration file to the auto import file path
Note: Zebra Managed Configurations provides a single interface to configure Zebra Android device hardware and software.
DataWedge Manager CSP (Configuration Service Provider) securely enables mass configuration deployment with the underlying MX framework, an XML-based communications platform that serves as a common interface for managing capabilities and behaviors of Zebra Android devices. The CSP is an MX plug-in that can set or query a particular configuration, allowing DataWedge to receive and process XML files. This lets device administrators utilize StageNow to create profiles specific to configuring DataWedge and deploy through StageNow or an EMM. Features that can be configured include:
- Control access to intent APIs
- Enable/Disable DataWedge UI
- Enable/Disable configuration file import via intent API
- Enable/Disable auto import of configuration file
- Import configuration file from specified path
- Import NextGen SimulScan Templates
See DataWedge Manager CSP for more information.
Note: When StageNow profiles are used to configure DataWedge Manager CSP, profiles created with MX 10.1 can result to a failure in some devices running DataWedge 8.1 and 8.2. Instead, select MX 10.0 when creating the StageNow profile with DataWedge Manager CSP. This is resolved with DataWedge 8.2.62 or higher. Until DataWedge is updated to 8.2.62, features specific to DataWedge Manager CSP with MX 10.1 may not be functional.
- DataWedge 8.1 - New Control Access to Intent APIs
- DataWedge 8.0 - New Import NextGen SimulScan Templates
- DataWedge 7.5 - DataWedge Manager CSP support introduced, requires at minimum MX v9.2 and StageNow v3.5.
Restrict app access to DataWedge, preventing unauthorized configuration changes, by controlling whether DataWedge APIs are accessible from all apps or only whitelisted apps. DataWedge APIs are categorized as follows:
- Configuration APIs - Intent APIs related to retrieving, setting or removing DataWedge configuration (e.g. SetConfig, GetConfig, etc.).
- Notification APIs - Intent APIs related to retrieving status for the DataWedge scanner, profile or configuration (e.g. Scanner Status, Configuration Change, etc.).
- Query APIs - Intent APIs related to retrieving DataWedge information or enumerating scanners (e.g. Enumerate Scanners, Get Active Profile, etc.).
- Runtime APIs - Intent APIs related to DataWedge runtime configuration changes (e.g. Switch To Profile, Switch Scanner Params, etc.).
Refer to the Control Access to Intent APIs guide for more details.
Note: Supported only on devices with DataWedge 8.1 or later.
Controls whether the DataWedge user interface is accessible to the device user, determining the ability to change DataWedge configuration settings on the device. If disabled, DWDemo profile settings can still be modified for demonstration purposes.
Controls whether configuration files can be imported by apps via DataWedge Import Config intent API.
Controls whether DataWedge configuration files are auto-imported when located in the
/enterprise/device/settings/datawedge/autoimport folder on the device.
Specifies the full path and file name to import the configuration file (
datawedge.db) or profile (by default,
dwprofile_<profilename>.db). Can be used instead of the default Auto-Import (
/enterprise/device/settings/datawedge/autoimport) folder. The file name must adhere to the existing DataWedge file naming convention:
- Config file is always named
- Profile naming convention:
With the introduction of scoped storage restriction on Android 11 devices, EMM (Enterprise Mobile Management) systems cannot copy files to DataWedge folders on internal or external storage (e.g.
/storage/emulated/x/Android/data/com.symbol.datawedge/file, where "x" is a digit). Instead, Zebra recommends to use either of the following folders by updating the file paths in the deployment configuration (such as OEMConfig, Managed Configurations or StageNow configuration):
Import NextGen SimulScan Templates for document capture by using StageNow. After importing the template, it populates Document Selection under NextGen SimulScan Configuration. Contact your local Zebra Sales Representative for assistance in creating the template. Refer to NextGen SimulScan Template in DataWedge Manager CSP for more information.
Steps to deploy and import a Document Capture/NextGen SimulScan template to a device:
- Generate the template as an .XML file with Template Builder.
- Copy the .XML file to the device (e.g. /sdcard).
- On a host system, open StageNow to create a profile.
a. Click on Create New Profile.
b. Select MX 10.0 or higher and select Xpert Mode. Click Create.
d. Enter a profile name. Click Start.
e. Select DataWedgeMgr and click on +. DataWedgeMgr is added to the list on the right. Click Add.
f. For NextGen SimulScan template, select Add/Replace a template. For Template file, enter the file path where the template is located (e.g. /sdcard/template.xml). Click Continue.
g. Click Complete Profile.
- Select the desired deployment method:
- StageNow - Generate the barcode. Open StageNow on the device and scan the barcode.
- EMM - Click on Export for MDM to export the .XML file to deploy via EMM.
- DataWedge Manager CSP - describes DataWedge Manager CSP usage
- MX Management System - explains MXMS framework
- Control Access to DataWedge APIs - explains how to control access to DataWedge intent APIs to prevent unauthorized use
- Profiles/Plug-Ins - discusses DataWedge profiles and plug-ins
- DataWedge profile - explains how to create a DataWedge profile