Developer Documentation

The intconf.xml file is usually a tiny little XML that you have to publish along with the workflow solution that you want to integrate. It gives the endpoint a name, specifies whether it is inbound (for messages coming from the client IT system) or outbound (for messages going towards the client IT system), and specifies the type of messages that will be accepted by the endpoint by listing the message schema names.

Name your endpoint AstroIn, since it's an inbound endpoint that communicates with the Astro ERP.

Refer to the intconf reference to make sure you get your endpoint-mapping right.

Save the file among the rest of your solution artifacts, and publish. Sure, you still need to implement the web service client on the Rocky Jupiter end to push the integration messages to the Cloud, but you've got your integration messages and your endpoint set up, so this should work, right?

c:\RockyJupiter>mebt run . reftab.xlsx
mobilengine srv 22.0 (Release) v22.0.157.14908
Executing run (compile and deploy to server):
Service url: https://tutorial.mobilengine.com/services/comex/v1/
User: petar.hoyt@gmail.com
adding 'assignments.refem'
adding 'cargoTypes.refem'
adding 'dashboard.form.xml'
adding 'drivers.refem'
adding 'intconf.xml'
adding 'newPO.dacsem'
adding 'newTask.rfs'
Import dacsem 'newPO'
No changes for reference table 'assignments'
No changes for reference table 'cargoTypes'
No changes for reference table 'drivers'
Import integration settings
Error executing step "Import integration settings"
missing iep 'AstroIn'
                  

Lesson learned: Every integration endpoint that you configure in the intconf.xml file must already exist on the cloud.

An endpoint is the interface between the Mobilengine Cloud and the Wire Data Exchange-protocol web service that drives an integration solution. It is basically a network address at which the Cloud exposes the integration data, or from which the integration data are sent. Creating an endpoint is therefore a cloud operation on the Backoffice site, available to you on the Dev console → Integration screen. Choose the Add inbound endpoint command because with this particular solution, the Mobilengine Cloud will be receiving integration messages.

Take note of the generated key that protects against unauthenticated integration messages coming through: all dacses have a <key> element, and to enforce data security, the Cloud will reject integration messages without the appropriate endpoint key.

The Mobilengine Cloud offers built-in support for sending an acknowledgement message back across the wire for each incoming integration message. If you have an outbound integration solution set up, you can select its outbound endpoint in the Asynchronous ACK drop-down to make it transfer the automated acknowledgement messages.

Enter the name of the endpoint, and click OK, then Save Configuration on the next screen to store the endpoint details.

You can go ahead and publish the solution now: the mebt can't complain any more that it can't find the AstroIn endpoint that you reference in the intconf.xml file. When the solution is published to the cloud, the Dev console → Integration → Edit inbound endpoint screen will include a Download Wsdl link with the generated WSDL file.

Be sure to download the WSDL. It's the contract for the web service that drives Mobilengine integration solutions - you'll need it in the next section, when you tackle configuring the web service client that pushes the newPO dacses to the AstroIn endpoint.