Overview

Dynamics Mobile Agent is a light-weight ASP.NET application deployed on prem. Following list of standard hardware and software requirement.

​

Dynamics Mobile Agent Server Machine

• OS: Windows Server 2012 R2 (or newer)

• Internet Information Services 7

• Provisioned SSL certificate for secure communication over SSL from public certification authority

• .NET/ASP.NET 4.5

• Windows Domain

• (optional) Open port 443 to the public internet to allow external communication with devices.

• CPU: 4 x Xeon Cores, 32 Gb RAM

• HDD: 500 Gb free space, 80 Mb/sec write

Dynamics Mobile Agent (running in Internet Information Services and as Windows Service) must be able to make requests towards the ERP end point ( AX2012 AIF, D365 ODATA). It needs to use dedicated ERP credentials. User credentials. All calls are carried out from a single dedicated ERP (AX, NAV, D365) User, who should be able to:

• write/read from DMSyncLog table in the ERP for off-line apps (VAN Sales)

• read access to all ( or predefined ) ERP tables used in the mobile app

Windows Domain

The machine, where Dynamics Mobile Agent is deployed is recommended to stay in DMZ out of Windows domain. Dynamics Mobile Agent connects to the ERP (AX2012, D365, NAV, BC) via the ERP's native API ( AIF, ODATA, ... ) requests and authenticates by using dedicated ERP user - e.g. there must be a dedicated Dynamics Mobile user defined in the ERP.

SSL Certificate

Dynamics Mobile app, which runs on the mobile devices can communicate via SSL with Dynamics Mobile Agent. This option however, requires the organization to issue SSL Certificate for the public DNS address or IP where Dynamics Mobile Agent is published from a public certification authority.