Agentry: Android Branding Client

[Former Member]

Hi all,

I understand that the android branding client supports three different ways of customization.

1. Replace anything that is called a "Resource" in Android development. This includes icons, images and strings. Differentiation by language is possible.
2. Change the application's name and package id via build-android-common.xml
3. Provide an exported Agentry.db file which contains a full application including complex tables preset server and user data.

Is there a way to modify the Agentry.db file in such a way that it contains only the application and a pre set server but no user data? We want the user to be forced to log in the first time he starts the application with no pre set user name. We are currently using Agentry 6.1.4.179.

Any ideas?

Thanks,

Christoph

[bill_froelich]

The user will always be forced to login to the server the first time to authenticate their credentials.  Even if you are using the same username that the prebuilt database was created with you will still need to connect to the server the first time.

Android currently does not have an option to only define the server connection string in branding like you can for iOS or WPF.  You will need to include the Agentry.db.  I would suggest just trying the branding including the pre-built db and test to confirm it is meeting your expectations.

--Bill

[Former Member]

Hi Bill,

we already tried the Android branding client and this was actually something we were missing. Is there any documentation of the Agentry.db database structure? E.g. we would like to manipulate the server address after creation of the db file etc.

Regards,

Christoph

[bill_froelich]

Christoph,

The intention with the pre-built database is you connect an android client to the production server you are building the installer for.  This ensures that the application definitions in the Agentry.db are valid for the server you are connecting to.

Sorry to say but the Agentry.db structure is not documented as you should not be modifiying the contents directly.

Why are you trying to change the server address?  Are you not able to connect to the actual server that the client will connect to?

--Bill

[Former Member]

Hi Bill,

no, we are not able to connect to the actual server of the customer production system.

We have to build the branding client before the rollout of the new Agentry app version. Your way presumes that the version is already published to the production system.

Best regards

Dirk

[Former Member]

Changing the server address of the database file wouldn't work unless unless the server you build the pre-build client db file shares the same encryption key.

Yes, this way does expect the logic to be published to server.

Are you rolling up just an update version, or setting up a new server?

If it a new server, I would believe you would want to make sure the server is up and running before trying to put users on it, this would give you time to pre-build the clients

If you are rolling a new version, are there so many to the changes to the application that the expected to take a long time to download all the changes?

Stephen