Integration tools
No integration project is the same, and no customer is alike. That is true even for packaged applications, such as SAP CRM or Microsoft Dynamics, due to the multitude of customization options each offers.
There are following scenarios to consider:
- Pushing data from the system of record into a Liquid Platform community.
- Transactions routed by the Liquid Platform to the system of record.
A number of options exist for integration, not limited to the following examples.
Custom code
In this scenario, the integration development team builds out custom code that extracts and transforms data between Liquid and system of record and vice versa. This custom component can be written in any language the integration developer is familiar with.
This wiki refers to examples in Python and JavaScript.
ESB
A number of tools exist that implement Enterprise Integration Patterns that can help speed up the integration development. Many of these tools come with pre-built connectors to popular enterprise systems such as SQL databases, HTTP REST endpoints, SOAP, OData, SAP and Microsoft software, etc.
The following are examples of what some of our customers have chosen to use1:
The challenge of integration is that ultimately the transformation and extraction code requires customization. While they simplify the job of the integrator, these tools do require some development expertise and understanding of Enterprise Integration Patterns.
1. Not an exhaustive list, just a few examples ↩