You don’t need to install any plugins or components in your connected systems.
Model your processes precisely and unlimitedly across systems and increase your success. The Marini Integration Platform offers you all possibilities. Integrated processes increase your success significantly, because you can react much faster in the right moments and your data is available without a break.
Your processes are initiated via triggers, i.e. event-based. The trigger can be, for example, the call of a URL or the reaching of a certain score. As soon as the integration workflows have been triggered, the defined data in your process is transferred unidirectionally from system A to system B.
Bidirectional integration workflows ensure that your process does not end once data has been transferred from system A to system B – just like unidirectional integration workflows. After data has been transferred from system A, another action is triggered either directly or scheduled, so that new or modified data is sent back to system A.
The Marini Integration Platform allows you to integrate systems hosted in the cloud or on-premises. It doesn’t matter in which combination you want to set up the integration. You can easily implement pure cloud integrations, hybrid integrations or even on-premises to on-premises with the Integration Platform.
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.
You can route and orchestrate your processes and data via plans and conditions. It is possible to synchronize from any endpoint to any endpoint. You are not limited in terms of modules (if available via API) or fields. So you can model any of your processes – no matter how complex.
Of course, you can also control processes across any number of systems. For example, triggers that you define in system C can trigger actions so that data is transferred to system B. There, you can also define whether the data should be transferred directly or on a scheduled basis. Your requirements for orchestrating and routing across multiple systems can range in complexity from low to high – the Marini Integration Platform serves all your needs. There are no limits to the number of systems a process can be modeled across.
Cloud, hybrid, on-premises, all endpoints, uni- and bidirectional, unlimited, secure and GDPR compliant
Search your application, system or service in our complete public plan list.
The development of further integrations is no problem and can be realised quickly.
Integration workflows focus on processes that are steered across systems. You integrate two or more systems to be able to realize processes across them seamlessly. Triggers in one system trigger actions in another system. The logic can become arbitrarily complex across the systems. The necessary data is transferred between the systems appropriately.
Yes, many standard integrations are available for a jump-start via the Marini Integration Platform. The standards can be activated with just a few clicks. For example, known system combinations or connections from external data sources can be activated directly.
For the Integration Workflows you only need the HubEngine. You can map all use cases of the Integration Workflows using the HubEngine alone. If the complexity is higher, then a distributed platform with transformation logic is recommended.
When using the Marini HubEngine, no plugins or other components need to be installed in the connected systems. One API user is sufficient for using the Marini Integration Platform. The entire logic is handled by the HubEngine.
No, the use of integration workflows is not limited using the Marini HubEngine. Via the Marini Integration Platform all endpoints (also called tables, modules or custom objects) of the connected systems can be addressed and all data (also attributes and characteristics) can be used for the conditions of the triggers or via the mappings during synchronization.
A multitude of individual integration workflows can form a distributed platform. First, distributed platforms serve to bundle processes in your systems, their transformation logics and the routing of data. Second, the goal of a distributed platform is to make data available in all your relevant systems – in real time. Distributed platforms thus combine integration workflows with pure, non-process-driven synchronizations. Often the first step are single integration workflows, which grow in number and complexity. This usually results in a distributed platform. We speak here of the evolution of integration.
A centralized platform is generally process-independent. It is about collecting and linking the relevant customer data in one central place. This gives you a consistent and visible picture of your customer at one glance.