Integration core principles

Applying our five core integration principles a Mobile Application Integration use case typically involves the following:

Transformation Since we are going to consume this interface from a mobile application, the best choice for the data format is JSON, which is a protocol that is very easy to work with both in a mobile application and in Mule. In this case the challenge will be to transform the JSON data being received from our mobile device into a format that is can be loaded in SFDC. A simple JSON data object is presented below, which indicates the type of data being received from our Mobile App.
Transportation Transport protocol negotiation between a REST (HTTP) based service that interacts with our Mobile Application and in our use case, with the SFDC system over HTTP and an additional email connection that uses the SMTP protocol.
Orchestration Composing several underlying components into a single higher order composite service. In this use case we are aggregating an update with SFDC with a simple email service and presenting it as a REST-based Mobile Application using a simple Mule integration flow to wire everything together.
Mediation Mediation will be useful here over time as it becomes necessary to support multiple versions of this service for a wide range of consumers. Additionally, it is possible (if required) to provide an additional SOAP interface for this REST-based service by simply adding the mediation components to marshal between SOAP/XML & JSON.
Non-functional consistency These requirements are by nature generic and include providing a common implementation of security, logging, deployment, management of run-time components, and more.
+

Esta página está disponible en español

Ver en español