Overview
Overview
The ADK TMS Agent is part of the Application Development Kit (ADK), and is one of several components belonging to the ADK. ADK is a software abstraction layer that is between the hardware platform operating system and the device application. It provides a common interface for all applications to use. The ADK interface can be used to access and control the ADK TMS Agent.
ADK TMS Agent currently supports 3 different operating system (OS) platforms and various hardware platforms that run these OS types. The main hardware platforms currently supported by ADK TMS are the MX and VX platforms which each have various hardware models that belong to each of these platforms. The MX platforms supported by ADK TMS consist of the MX8xx and MX7xx series which run Verifone's RFS OS. The MX platforms also have the MX9xx series which runs Verifone's V/OS operating system. The VX platforms supported by ADK TMS run the Verix eVo OS. ADK TMS Agent is a component of the ADK and the ADK interface/APIs can be used to control and access ADK TMS functionality. The VX platforms also include the e-series mobile devices, e315, e335 and e355. These are mobile devices and their main communication interface is WiFi. The following table describes the various platforms, OS and ADK TMS versions:
Table 3 Agent Types and Support
| ADK TMS Agent Types | OS/Platform | Server | Release | Comment |
|---|---|---|---|---|
| 1 | RFS | ADK TMS | Rel7/8 | MX7, Mx8 |
| 2 | V/OS + ADK | ADK TMS, ETM8 Server | Rel 1/2, Rel8-11 (UX300), Rel8-11 (Vx) | MX9, UX, Vx, Raptor |
| 3 | Verix eVo + ADK | ADK TMS | Rel8-11 (non ADK); Rel7 (with ADK) | Vx ADK Apps |
- All three variations of ADK TMS Agent are generated from a single source code starting with release 2.7.x.
- RFS/MX7/MX8 support is limited only to field issues and there are no new planned development testing.
ADK TMS Agent supports 3 main architectures:
- The ADK TMS Agent ADK mode, which supports multiple ADK TMS communication interfaces such as ethernet, GPRS/3G, and dial-up.
- The ADK TMS Agent in non-ADK mode on a V/OS platform or RFS MX platform, which supports ethernet communication interface.
- The ADK TMS Agent on a Verix platform in ADK mode, with a non-ADK-based application in the device. This configuration with ADK TMS using ADK mode supports ethernet, GPRS/3G and dial-up for ADK TMS communication.
The following illustration shows ADK TMS Agent with ADK-COM.
Figure 1: ADK TMS Agent with ADK-COM
- ADK TMS Agent supports Ethernet, GPRS/3G and Dial-PPP modes.
The following illustration shows ADK TMS Agent with a V/OS or RFS MX platform
Figure 2: ADK TMS Agent with V/OS or RFS MX Platform
- ADK TMS Agent only supports Ethernet mode.
The following illustration shows ADK TMS Agent with a non-ADK application.
Figure 3: ADK TMS Agent with Non-ADK Application
- Supports Ethernet, GPRS/3G and Dial-PPP modes.
- This architecture is applicable for existing Payment Apps, whether they run in a single application environment or in a multiple application environment using common solutions like VMAC, etc., along with ADK TMS Agent.
- As EOS/CE on Verix platform will likely be shared between multiple networks, connectivity supporting components like ADK-COMs COM-DAEMON, VMAC or Direct Payment App platform using CE interface, the applications registering with ADK TMS Agent should follow these rules to avoid network resources conflict:
- When ADK TMS Agent requests connection permission (Go/No-GO), the application should reply with No-GO (report BUSY) if it's using the connection so that ADK TMS Agent waits for GO permission.
- Application should release EOS/CE resources directly or through their common solution components like VMAC before giving GO permission (report FREE) to ADK TMS Agent. This enables ADK TMS Agent as an application to get the resource when it tries for network connection from EOS/CE (through COM-DAEMON), without any conflict.
- For detail on GO permissions, refer to tms_setApplicationState().
Preface
The ADK TMS Agent is part of an Estate Management system called Verifone Estate Manager. It is a client side terminal application that communicates with the TMS server and runs in the background through its own communication channel. The ADK TMS Agent sends and receives various messages in performance of managing the device. It periodically sends a heartbeat message to indicate to the TMS Server the device is active and communicating. This document describes the functionality of ADK TMS Agent and provides the steps to install and configure for various supported platforms.