Mendix supports connections to other apps and services through industry-standard interfaces and protocols such as REST, SOAP, JDBC, and OData. The platform offers many solutions for ensuring that new applications can both consume and expose data and services in heterogeneous environments.
What Is Mendix Vision for Integration?
How Can I Integrate with Mendix?
How Does Mendix Support Data Mapping?
Being able to easily and visually map external data formats to the entities used in your application is an important aspect of integration. Mendix helps you achieve this with its data mapping functionality that automatically maps incoming message structures (such as JSON, WSDL, or XML) in order to create domain models (if desired) and data mappings. Once the message structure is mapped, incoming data can then be transformed (if required) so it can be used inside your application models.
Read on in How Does Mendix Support Data Mapping?.
How Does Mendix Support REST & Web Services?
Mendix makes exposing and consuming REST and web services simple. To consume, map the incoming message responses from the API or service request using JSON or a WSDL, for example. Once mapped, microflow actions allow you to call the desired service from your logic and process the response directly into your app. Exposing your data and logic is also very simple. Using specific microflow actions, you can publish discoverable endpoints for your services, expose an API via a Swagger definition through microflows, or expose entities with a single click as OData resources.
Discover more in Service Consumption.
Key Components of Integration
Integration has always been an important part of application development, but the topic has not received much attention in the marketplace for developing apps until now.
Being able to easily map external data formats to the entities used in your application is an important aspect of integration.
Mendix will automatically determine the structure of your message and the applicable attribute types.
Most newer services use REST instead of web services, but using REST requires a small shift in the design of your services.
When using data acquired through integrations, you have two options for storing and using the data.
Data Hub Architecture Overview
The Data Hub Catalog acts as a phonebook or map to the data and capabilities provided by software in your organization.
External Entities Overview
External entities are representations of data provided by services in other applications.
Data Hub Catalog Overview
The Data Hub Catalog is a global multi-tenant store of metadata with each organization’s information stored separately.
The Data Hub connector framework is the core foundation for connecting external systems to Data Hub in both general and use case-specific ways.
Business events can be used by applications as a signal to inform other applications that something interesting has occurred.