Getting Started with MCL-Net v4 > MCL-Net v4 Workflow

Overview

As a communications tool, MCL-Net v4 has an important role on the overall communication architecture of the MCL project implementation.

MCL-Net v4 is used to synchronize data between concurrent mobile devices and one or more servers.

If it becomes necessary for your mobile devices to access your own databases, MCL-Net v4, alongside MCL-Bridge, ensures a secure and reliable connection between your mobile device and those external systems.

When implementing your MCL-Net v4 network, consider your business needs and what the desired workflow should be.

Below are MCL-Net v4 workflow examples:

Mobile Device Data Synchronization with one (1) Local Server

MCL-Net v4 is installed in one location.

MCL-Net v4 ensures file exchange with the host (send file/receive file).

Concurrent mobile devices communicate with the MCL-Net Server via Ethernet, USB, WiFi and/or LAN/WAN (GPRS/UMTS/4G/5G). The type of communication is interchangeable. For instance, an operator may communicate with an MCL-Net server via WiFi and, then, switch to a GPRS communication.

This workflow can be repeated for multiple sites.

Mobile Device Data Synchronization with more than one Server and between Servers

More than one MCL-Net Server, each installed in a different location, ensure file exchange with the host (send file/receive file).

This setup is useful when customer sites/locations are isolated from each other.

MCL-Net Server Communication with External Databases

The MCL-Net server uses MCL-Bridge to communicate with the customer's databases and/or ensure file exchange (send file/receive file).

See MCL-Net v4 Use Cases. This topic provides concrete examples of MCL-Net v4 use in simple and complex project implementations. For instance, the basic workflow for a single store or the more complex workflow that is required when you have multiple depots communicating with a cloud based data center.