You can set a device according to your requrements, export the *.db files from DataWedge and distribute the *.db files via a file sync rule.
Plese refer to the Auto Import section in the DataWedge Settings Manual.
Is there a way that this can be done without having to reset the device? We have placed the .db file in the autoimport directory according to the manual, but nothing happens until the device is reset. It would be just as easy for the user to go in and manually upload the db file if this is the case. We are looking for a better way to manage this parameter.
DataWedge configs can be set on the fly by using the intent API. However, neither MobiControl nor MX is capable of sending an intent with a nested bundle attached to it. The only way I see is to write a little app that does the job and apply it via MobiControl.
As I mentioned elsewhere ( Re: Datawedge and StageNow, TC55 GMS ) reset is needed probably due to file permissions ( DataWedge Settings - Zebra Technologies TechDocs ). "Zebra recommends applying explicit file permissions to the all .db files" - but don't explains how . If StageNow client was able to send nested intent it would save lifes in many times but for reasons I don't understand it's not.
2 of 2 people found this helpful
Here's how I have done this in the past with Soti
Deliver the file to /enterprise/device/settings/datawedge (not to the autoimport folder yet). Then add a post install script (pasted in below) that will set the permissions on the file, then copy to autoimport and also set the permissions on the new file under autoimport.
execute_shell chown system.system /enterprise/device/settings/datawedge/dwprofile_myprofile.db
execute_shell chmod 777 /enterprise/device/settings/datawedge/dwprofile_ myprofile.db
copy /enterprise/device/settings/datawedge/dwprofile_ myprofile.db /enterprise/device/settings/datawedge/autoimport/dwprofile_ myprofile.db
execute_shell chown system.system /enterprise/device/settings/datawedge/autoimport/dwprofile_ myprofile.db
execute_shell chmod 777 /enterprise/device/settings/datawedge/autoimport/dwprofile_ myprofile.db
del /enterprise/device/settings/datawedge/dwprofile_ myprofile.db
You just saved me lot of restarts thank you very much
Thanks, that would be awesome, but we are using Android+, and execute_shell does not seem to work.
I appreciate all of the help!
Did you tried the commands via the File Transfer Rule or directly via Send script or Package? Because via the Rule it's working for me
Appreciate for the post.
This helps a lot however it doesn't fully work in my environment.
I finally work it out by doing the followings, hope this can help someone who has the same issue like us.
I create a package and push datawedge.db to
Copy and paste the following scripts into Post-Install Scripts:
copy /sdcard/Android/data/com.symbol.datawedge/files/datawedge.db /enterprise/device/settings/datawedge/autoimport/datawedge.db
__chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db
If everything works as expected, you don't need to import DataWedge configuration manually.
This is very handy when you upgrading the application.
Here is my environment:
SOTI Android Enterprise Agent
This approach worked in our instance as well. I was looking to import a profile only. Export the profile you want from a device. It will be saved as dwprofile_<profilename>.db. Put that file into a package with the same Post-Install script as stated above (changing "datawedge.db" for "dwprofile_<profilename>.db").