Database Overview
Before connecting to the mobile database, ensure you have updated your SQL Management Studio, current working version is 20.2.37.0. Take note to tick the checkbox option that says: Trust Server Certificate, when trying to connect. The IP address for the server is 172.30.0.6 and database credentials can be found at https://vault.zoho.com/. Below is a breakdown of some important tables that can be found in the database and their purpose:
| Table Name | Description | |
| [dbo].[mobileAppSettings] | This contains basic information required for the mobile app to run. It points the mobile app to a web service which is responsible for handling database operations and business logic. The service URL is specified in a field called, "WebServiceURL". Each mobile app must also be assigned a unique company id, which is stored in a field called, "CompanyName"; The format for this field must be as follows: CODE@GUID |
Google Play Store
In order to deploy an android application on the Google Play Store you'll need the following: (credentials can be found on ZOHO).
URL: https://play.google.com/console/developers
Username: innovation@ebsphere.com
In Visual Studio, we need to configure / update the android manifest with the following information: (The manifest can be found at ebapp.android > properties > androidmanifest.xml)
| Property Name | Example | Description |
| Application name | MWPF | Short alphabetic code which represents the client |
| Package Name | com.globalkinetic.mineworks | Reverse domain name |
| Version Number | 160 | Numeric value which increments at each deploy, not shown to the user |
| Version Name | 3.3 | Version number which is displayed to the user |
Important! Ensure the following has been configured before rebuilding and deploying the application. The MainActivity class requires an "Activity" attribute with details that are specific to the client to are doing the deployment for. We also need to change the "appsettings.release.json" file to include a reference to the client record stored on the "dbo.mobileAppSettings" table mentioned previously; this is the reason the company code must be unique.