Introduction

Totalmobile is designed to enable customers to present out their Enterprise-wide back-office applications onto a range of mobile devices. Using Web Services; Totalmobile authenticates, verifies and transmits any data down to the required devices; securely and efficiently.

There are 3 basic server roles that are key to any Totalmobile installation:

  • Database Server - This is where Totalmobile stores all data within the system.

  • Integration Server - This acts as the entry and exit point of Totalmobile into the back-office systems, as well as processing the internal Totalmobile messages.

  • Web Server - This presents the relevant Web Services needed for Totalmobile devices to operate, along with webservices for external integration.

At least one server from each of the roles above is required for a single instance of Totalmobile, where an “instance” is defined as Live, Test, Train, Dev etc – from a support perspective we would always install at least a Live and Test environment to isolate “Production” from “Non-production” services. How the servers are ultimately deployed will be dependent on each customer’s requirements in terms of scale of the solution (how many servers of each type are required based on the number of devices) and other factors such as external security requirements.

There are also two optional components that can be included in a Totalmobile installation. These are dependent on the type of installation & services required:

  • Mendel Engine – This is the scheduling engine required to automatically schedule work, based on applied metrics for efficiency.

  • On-Prem Integration – This is installed on a client site, providing on-site integration via a local TotalMobile integration service and allows integration into a particular back-office application.

As mentioned previously, Totalmobile supports ‘instances’ whereby multiple Totalmobile installations can be completed to allow for separate Live, Test, Training or Development environments. This allows the production services to be kept clean & stable, whilst allowing for staff training or new feature releases to be implemented via the test/dev instances before committing to the production grade Live environment.