The MDA Android client can be configured using Java-style .properties files in the directory at.iteg.mda.com/config/ under whatever andoroid.os.Environment.getExternalStorageDirectory() returns, i.e. usually on the SD card.
The application reads all *.properies files in arbitrary order, with the latest occurrence of conflicting options winning over earlier occurrences.
We recommend to use our default file name and content scheme, like described below.
device-id.properties
This file contains the MDA device-id of the device and should be unique within all the devices of an organisation. Therefore it is different for every single device and should not be copied around.
It looks like this:
# deviceId: id of the device, must comply with device list in server # must be set manually when rolling out a device # format: free text up to 255 characters (a-z, A-Z, 0-9, _, -) deviceId=FOOVALLEY-01
server.properties
This file contains the URLs of the MDA application server and of the Webspace providing new MDA.apk files for MDA's self-update feature. It usually looks the same for all MDA devices in an organisation and can be copied around without too much thought.
The default file, configurating the app to use an imaginary mda.mycompany.foobar, looks like this:
# serverBaseURL: base URL of application server with trailing / # i.e. https://mda-demo.iteg.at/mda.impl/ serverBaseURL=https://mda.mycompany.foobar/mda-impl/ # apkUpdatesBaseURL: base URL for APK updates, with trailing / # i.e. https://mda-demo.iteg.at/mda-updates/ apkUpdatesBaseURL=https://mda.mycompany.foobar/mda-updates/