Developer Documentation

The Mobilengine Cloud is the platform service portion of the Mobilengine SDK that compiles, stores, and manages your workflow solutions. The Mobilengine Build Tool (MEBT) is the command-line interface to the Mobilengine Cloud; developers with a personal or company Mobilengine SDK account can upload, download, update, or delete solution artifacts they have created, or create and publish workflow solutions that are built up from their solution artifacts.

There are, in fact, not one, but two separate Mobilengine Clouds: the Mobilengine Development Cloud, a limited sandbox for developers to try out their in-development solutions, and the Mobilengine Production Cloud, the actual high-performance cloud instance that serves Mobilengine SDK developers' clients workflow solutions, and manages live business data.

All Mobilengine SDK developers who sign up for an account get access to the Mobilengine Development Cloud; access to the Production Cloud needs to be applied for on a per-client basis.

Below is a list of Mobilengine solution artifacts that are compiled and uploaded to the Cloud when publishing a solution.

fls files declare workflow solution forms.

rfs scripts process the data that arrives to the backend from mobile users, through an integration solution, or as part of a synchronization event.

refem files describe the schema of relational reference tables to store workflow-related reference data in the Mobilengine backend.

dacsem files define the schema of the XML messages that an integration solution transfers between the Mobilengine Cloud and your external system. These so-called integration message schema files also define how the XML messages and the objects that the workflow scripts processing them can operate on.

evem files declare synchronization events tables that you can use to make your workflow solutions react to specific users' mobile clients syncing their database snapshots with the server.

An intconf.xml file configure the integration endpoints that you have set up on the Mobilengine backend, and specify the integration message schemas allowed through them.

You need to compile and package solution artifacts that make up a workflow solution before you can publish them as a live or in-development workflow solution to the Mobilengine Cloud.

Compiling checks the artifacts for syntax errors, type errors, and broken references in the artifacts, and, if no errors are found, outputs a compiled solution file. A compiled solution includes all the input solution artifacts apart from host-specific data such as reference table input data.

You need to package input data for the reference tables in the solution to a compiled solution file before you can publish the resulting deployment package to the Cloud.

Publishing makes the mobile forms and webforms in a workflow solution available to the users registered with an account on the Mobilengine Cloud. However, for the users to actually access the forms in a published solution, you need to assign the forms to one or more appropriate users on the Backoffice site. See the relevant tutorial for more details.

The MEBT allows the retrieval and manipulation of potentially business-critical data; only authenticated users are allowed to access the Cloud using it. To use it, you will need to supply your Mobilengine developer account username and password, as well as the service URL that you received when your developer account was registered.