The transmit configuration defines how the application on the Agentry Clients can communicate with the Agentry Server. It can define what application-level data definitions to synchronize and the address and port number of an Agentry Server. It also defines whether to log a user out of the Server when a transmit has completed, or to keep them connected to provide real-time communications functionality.
A transmit configuration is defined for an available communications method on the client device. As an example, if a wireless LAN connection will be available to client devices in the deployment, a transmit configuration for this connection should be defined. If a wireless WAN connection is also available, a transmit configuration should also be defined for this connection type.
Each transmit configuration defined in the application will be listed in the built-in screen called the Transmit Dialog on the Agentry Client. For this reason it is important to consider the proper setting for each transmit dialog’s Display Name, as it is this value that will be listed to the user.
Each of these connection types perform communications using the TCP/IP protocol. The connection type refers to the type of connection in the context of the application to be used when the transmit configuration is selected by the user on the client application.
Syclo recommends the ANGEL connection for all applications developed going forward. Applications developed using versions of the Agentry Mobile Platform prior to 4.4 being upgraded to the latest platform should be modified so that all transmit configurations use the ANGEL connect type. The Midstation and unencrypted Network Connection types are still available for the purposes of backwards compatibility and will be deprecated in a future release of the platform.