You often face the challenge of routing your data from multiple endpoints into one endpoint. From system B, data is transferred from two endpoints into the same endpoint in system A. The synchronization can be uni-directional or bidirectional.
Process routing is characterized by the fact that the integration is used to model a process within data must be routed. The simplest case consists of two systems that are synchronized with each other via the HubEngine. In this case, data should be routed from one end point (system A) to one of two end points in system B. The data should be routed from one end point to the other. Two HubEngine plans are required for this. As a rule, these plans are mutually exclusive. This is because the data should be routed to either one endpoint or the other endpoint. This is achieved by mutually exclusive conditions in both plans.
By connecting the right points of all your systems via one platform, you get seamless data availability. Route data through the platform to the relevant endpoints and keep your systems’ data in constant, real-time sync. The Enterprise Data Platform serves as a routing and ETL instance to ensure that your data is properly transformed, if necessary, and gets to the right endpoint.
We differentiate data routing from process routing in the respect that in data routing the data still has to be transformed during routing. For this purpose, we use the DataEngine as an ETL layer. This means that the main part of the routing logic and the entire transformation logic are moved to the DataEngine. One HubEngine plan is required per connected module or endpoint. As a rule, all data is routed from one system to another via the DataEngine. Any number of systems and endpoints can be synchronized into the DataEngine as well as any number of target systems and endpoints can be setup. Here, data from system A is routed via the DataEngine to systems B and/or C.
With its components, HubEngine and DataEngine, the Marini Integration Platform offers a wide range of options for routing your processes and data. Depending on the use case you need either only the HubEngine or both.