Implement outbound integration

What you'll be learning about:

  • How to set up an outbound integration endpoint on the Mobilengine Cloud

  • How to generate and configure a WDX-compliant web service to receive integration messages from the Mobilengine Cloud

You've set up the integration messages to carry the data across the integration solution all right. Just like you did with the inbound solution, now's the time to set up and configure an integration endpoint. Since there's a URL involved, this is a bit different than its inbound counterpart. When the outbound endpoint is in place to expose the statusUpdate dacses, you're ready to set up the web service that receives them at the other end.

Getting a WDX-compliant web service up and running is a three-step process:

  1. Download the WSDL web service contract that the mebt generates based on the published workflow solution.

  2. Use a dedicated tool to generate the web service contract code, the basic shell of your web service-to-be (a.k.a contract-first web service creation).

  3. Add some C# code to implement the operations declared by the interface in the contract code. The implementation described here is a very low-key proof of concept, and so all the web service will do is write the incoming dacses to the console at the receiving end. Once you hand over the integration solution, the Rocky Jupiter devs can tweak the implementation to fit their business logic.

As a Mobilengine solution developer, your job ends when you implement a WDX-compliant web service that listens for integration messages from the Mobilengine Cloud. However, you'll need to test whether the dacses reach the web service, and whether you didn't mess up the web service contract code. Your real-life clients will probably host the web service that you deliver themselves, but the easiest way for you to test the web service is self-hosting.

The code in this tutorial presents a functional self-hosted integration, and you can read up on how to do this for yourself, but your mileage may vary. When in doubt, consult your network administrator.