mprodigy technical specification
The architecture of B2M’s mprodigy mobile device management suite includes:
- The mprodigy Server which runs on a Microsoft Windows Server. mprodigy requires an SQL Server which may be hosted on the mprodigy Server or on a separate SQL Server.
- The mprodigy Communications Gateway which runs on a Microsoft Windows Server. It can be hosted on the mprodigy Server or a separate mprodigy Communications Server which can be situated in the DMZ (the intermediate network with a direct connection to insecure external networks).
- The mprodigy Device Client which runs on Windows CE / Windows Mobile based devices.
- The mprodigy Management Console will run on any Microsoft Windows Desktop operating system. Multiple mprodigy Management Consoles can be located where required on your network.
There are a number of different mechanisms for commissioning your devices. This will give you the flexibility you need for your organisation and allow zero touch application deployment and device configuration. These include ActiveSync commissioning, SD Card commissioning and web-based commissioning.
mprodigy supports both field-based and depot/store based operation and can be configured for optimal utilisation of your resources, e.g. in a depot-based environment device files can be distributed and stored on local file servers to minimise the amount of WAN traffic and optimise network bandwidth utilisation.
mprodigy can be configured into any GPRS, WLAN and LAN network. Please see this example of how mprodigy might be configured into your organisation.
mprodigy is supplied with installation tools to provide you with a straightforward and structured installation process. Details of the installation tools can be viewed here.
For more information regarding your specific requirements, please call +44 (0)1235 432753
or email customerservice@b2m-solutions.com
