About communications
You can change communications settings in Mobile Client.
To activate communications, a conversation is started by the device. If the conversation cannot be started, communications are regarded as inactive.
The following are possible reasons communications become inactive.
-
Communication Agent is stopped.
-
Hardware components are disconnected.
-
A serial device is not in its docking station when the device tries to transmit records.
-
RF traffic is heavy.
-
There is RF interference.
-
The distance between the access point antenna and the device is too great.
Response time-out
The response time-out limit is the amount of time a device waits for a response from the application server before it sends the application server a transaction request. This is also used when the device tries to establish a connection with the application server when Mobile Client is first started.
We recommend a response time-out of 5-15 seconds, based on your organization's requirements.
Communications time-out
The communications time-out limit is the amount of time the device waits for a transaction request to complete. This is also used when the device sends a request to the application server for data replication.
The communications time-out should be based on the maximum amount of time it may take to complete a transaction or data replication request. This will vary based on your organization's requirements.
For example, if an API call is the slowest process you want to use, you may need to set a 30-60 second time-out. Alternatively, if you plan to use full data replication you must set a longer time-out value. Full data replication of a 100MB local database could require a 300 second time-out.
Loading...
There was a problem loading this topic