DataWedge Auto Import Using StageNow and SOTI MobiControl

Assumptions: 

• The user has installed StageNow version 5.1 or greater.
• The user has Zebra Android devices with MX 9.2 or greater.
• The user is familiar with and knows how to configure SOTI MobiControl.
• The user knows how to configure, export, and download to the PC the DataWedge database from the device.

Procedure: 
 

1. Export the DataWedge setting (datawedge.db) or custom profile. In this demonstration, the name is Redspot. When exported, it is saved with the name dwprofile_Redspot.db.
2. Save the DataWedge profile on the Windows PC. 
3. Transfer the Datawedge profile either manually to a device or use StageNow File Mgr CSP, i.e., path on the device: /sdcard/dwprofile_Redspot.db
4. Create a new StageNow profile using MX 9.2 or higher and Xpert Mode. In this example, it is called Import_Datawedge.
5. Add DataWedgeMgr.

5. Enter the device's path to the DataWedge .db file and select the button to turn Automatic configuration import to ON.
   
   
    

6. Select the Continue button.
7. Select the Complete Profiles button.  
8. Select the Export for MDM button to save the configuration as an XML file.

9. Select Save to save the file as an XML on your Windows PC.
   
    
    

10. In MobiControl, you can use either a FileSync rule or a Package to send the StageNow .XML and the DataWedge setting (datawedge.db) or custom profile (example, dwprofile_Redspot.db), to the internal /sdcard location on the device.

In MobiControl, in the FileSync rule or the Package, add a postscript command pointing to the StageNow .XML (mxconfig <path to XML on the device>), which is case-sensitive.
 

mxconfig /sdcard/Import_Datawedge.xml 

NOTE  The Datawedge database filename is always - datawedge.db A Datawedge profile filename always needs to use a preceding " dwprofile_ " followed by the profile name, i.e., dwprofile_MyAppName.db As explained in TechDocs, Do not rename the exported file or manually edit the database file contents. Doing so will result in errors and import failure.

MobiControl will send the XML and the DataWedge .db file to the /sdcard location, and then the postscript will launch the XML to trigger the import of the DataWedge database .db file.

NOTE Due to the /enterprise folder not being remotely accessible on Android 11 due to Google's enforcement of protected scoped storage, this is the recommended method to auto-import DataWedge configurations on Android 11.

Helpful Information:

• TechDocs: DataWedge settings
• Support and Downloads: StageNow
• Deploy DataWedge Configuration via OEMConfig
• Deploy DataWedge for Android Configuration Using SOTI MobiControl