Vector graphic of osapiens HUB engines - osapiens.

The Problems you solve with our iPaaS & DataHub Engine

Enterprises today:

have not 1 but many different systems
require different views and slices of the same data
have lots of data records that need to be shared with customers and suppliers

But, enterprises:

already have too much load in their existing ERP backend systems (e.g. SAP ERP)
have different field structures in target systems and hence need translation and mappings
do not have capability to scale throughput dynamically and lack Monitoring and reprocessing capabilities

The iPaaS & DataHub Engine Highlights

Our iPaaS & DataHub engine solves this problem thanks to the following features:

DataHub sync, replication & subscription

Bi-directional, real-time and smart integration of the DataHub with existing business processes and systems via APIs and the unique “fingerprinting” technique

API Management

Create, manage and govern inbound and outbound APIs with automated security and thread protection at all layers

Business user interaction and mappings

Primary source of key data elements. Exposes user-friendly interfaces for data authoring, data consumption, search and offers drag & drop mapping capabilities

Delta-Update Handling

Bi-directional, real-time and delta data synchronisation is enabled by the unique “fingerprinting” technique. This technique requires data stating and persistence in order to efficiently serve existing channels subscribed to the relevant business data objects

Vector example image of iPaaS and datahub engine - osapiens.

Multi-threading config by tenant

Multi-thread engine configurable by tenant based on the number of workers. Number of workers define the number of parallel threads to be handled by the DataHub for a particular tenant

Example vector of the iPaaS and datahub engine - osapiens.

Establish complex conversion rules

In the DataHub mapping workbench, it is possible to define and run on-the-fly conversions. Tenants can program their own conversion routines with javascript to ensure that even extremely complex mappings work as required

Example screenshot vector of the iPaaS and datahub engine - osapiens.

Easy onboarding of new target or source systems

Onboarding of new target or source systems is hugely simplified thanks to the engine dynamic configuration capabilities for business objects and for connected external systems

Easy drag & drop data mapping workbench

Multi-thread engine configurable by tenant based on the number of workers. Number of workers define the number of parallel threads to be handled by the DataHub for a particular tenant

Example vector screenshot of osapiens HUB iPaaS and datahub engine - osapiens.

Detailed Monitoring Capabilities

Fully integrated error handling, re-processing of failed requests and real time statistics of success/failed/fingerprint messages

Routines to reprocess data

The engine comes with routines that enable the possibility to reprocess single data records. It also allows the reprocessing of mass records without load in the customer backend system (e.g. ERP)

Outbound API