Alternate solution to provide read, write, execute to file in AE.
The device doesn't have to be completely rebooted, only DataWedge needs to be relaunched, which the reboot is effectively doing. What if you were to script a kill of DataWedge then relaunch it and then call a different application like the SOTI Lockdown to the foreground so that you hide DataWedge again?
With that said, I tried looking for an elegant solution to this problem in the past before I realized that a required reboot is really not that bad. I typically just have the end users reboot or script a reboot. I'd almost rather that be the case so that you can ensure that the device is not in use while the DataWedge changes are being applied. Otherwise if you were to successfully push the .db into the autoimport directory with the correct permissions I feel like there'd be a chance for the DataWedge configuration to change on an end user while in use.
I know its a really old post but i stumbled across this one while doing research on autoimport too (wasnt working for me).
You can use the following script as post-install and the procedure should work without reboot:
__chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db
"__" is important
Just to help others looking for a solution :)
Kind Regards John
Good call! I have also moved to the __chmod 777 script for the AEDO device deployments and it works perfectly. DataWedge configures itself without a reboot.