Using the Mobile Client

RFgen Mobile Clients (also called a "Batch client") are mobile devices that function can collect data, run applications, and store data/updates while disconnected from the network. The resources for functioning when not connected to a server are stored on the device in a database. The mobile client can be implemented in three ways based on the Startup Mode configured:

1. Connected to the server as in a thin client.

2. Disconnected from the server where everything takes place on the device.

3. Roaming in and out of range of the server where database access is first attempted against the server, but if the client does not have a connection, the local database is used.

When the mobile client is configured to start in a connected state, it is in essence a thin client. The Batch Failover property will allow this mode to either switch over to a disconnected state or remain in a connected state and wait for connectivity to return when wireless coverage is lost.

When a mobile client is configured to start in a disconnected state, all aspects of the data collection operate on the device.

Applications, menus, users and others are loaded from the device, validation data on the local database is used for validation and completed transactions are queued on the device pending an upload to the server. Only an RFgen server can extract what was stored on the mobile device.

The one distinction between connected (or Thin Client) and disconnected is that an extra option must be provided to tell the mobile client to upload the data to the server when it is in range. See the Device object methods to accomplish this.

When a mobile client is configured to start in a roaming state, then the Batch Failover option has no effect.

If the client detects connectivity to the RFgen server, database-related commands, embedded procedures and macro calls / queuing are automatically redirected to the server.

If there is no connectivity to the RFgen server, all activity is directed locally just like a disconnected state.

To keep data integrity, it is recommended that the Server.SendQueue command be placed in the RFgen_OnConnect event.

That way all queued work will go to the server before more transactions can be performed that will automatically go to the server. It is also recommended that the Server.SyncApps command also be placed here to keep the applications, menus, users and others always up to date.

To install the authorization  certificate, see To Authorize Clients.

To connect to the server, the device must also be “checked” for authorized connections. Authorized connections apply to both Thin and Mobile Clients. See Device Management > Device Authorization for more details.