The WDX protocol specifies the following SOAP messages to transfer and acknowledge the receipt of data packages between the Mobilengine Cloud and an integrated system.
A SOAP message from the initiating system to the receiving system that contains a new data package to be transferred.
<EnqueueDacs xmlns="http://schemas.mobilengine.com/Wdx">
<dacs
dacsid="dacsid"
dtu="dtu"
meta="meta">
<Key>API-key</Key>
<Content>
data-package
</Content>
</dacs>
</EnqueueDacs>
| Parameter | Description |
|---|---|
| dacsid (required) | The string type package identifier that uniquely identifies the data package across the solution. |
| dtu (required) | The dtu date when the transfer was initiated. |
| meta (required) | The meta
of the integration message schema that determines the structure and contents of the data
package.
|
| API-key (required) | The API key that authenticates the initiating system in the integration solution. |
| data-package (required) | The data to be transferred, in XML format. Its structure and contents must conform to the integration message schema specified by the meta parameter. |
An empty SOAP message from the receiving system to the initiating system to acknowledge the receipt of a data package.
A SOAP fault from the receiving system to the initiating system that reports that a data package has been rejected and should not be resubmitted.
<EnqueueDacsFail dacsid="dacsid" xmlns="http://schemas.mobilengine.com/Wdx" <Message>error-message</Message> </EnqueueDacsFail></
| Parameter | Description |
|---|---|
| dacsid (required) | The string type package identifier of the data package that the response refers to. |
| error-message (required) | The error message detailing the reason for the failed delivery. |
The Mobilengine Cloud implements the following three types of error messages:
-
unauthorizedwhen the API key is missing or invalid in the data package -
integration endpoint disabledwhen the endpoint that would receive the data package is disabled -
unknown metaschema-metawhen the specifiedmetais not configured for the given endpoint in the configuration file