Skip to main content

Integration Rules

Integration Rules are work-flows of data that combine Integration Framework objects in logical data management chains, used to integrate activity between different systems. Using Integration Rules, you can build an integration path in a smart and graphical way, and configure only the steps you need for the data integration. The path is formed by a sequence of steps, each identified by one Dataset. The sequence can be configured using the following options:

  • STRAIGHT PATH: A standard integration rule sequence where there is one input dataset and one output dataset. Input & output datasets can have either the same or a different structure.
  • MERGE PATH: In this Case the sequence merge 2 or more input Dataset into a unique output one. The structure of the output could be defined by the user
  • FORK PATH: In this Case the sequence accepts one input Dataset and 2 or more output systems. Each system can be populated independently (system can share some data or can be completely separated)

Each Integration Rule has a starting-point where the Dataset reads the data from the source system and an ending-point, where a terminator targets the destination system for that data. In between the starting and ending points there can be intermediate steps to prepare, validate, aggregate, manipulate and process the data according to the integration to be done. Since the integration among two or more systems heavily depends on the specifications of the integration, there is no unique way in which to define the integration, and there are multiple ways to obtain the same results. You can customize all the aspects of the integration from the graphical display to the data managed inside.

Note: Integration rules can contain any kind of object with the exception of a connector.

Integration Rules can contain the following objects:

  • Dataset (any kind) for managing data
  • End-Points for managing the mapping between source data and external systems
  • Scripts for advanced customizations
  • Parameters for dynamic and parametric rules

Integration Rule paths have no limitations on the number of objects, splitting/merging actions, number of steps or the sequence order. Each sequence is built graphically, starting from the Dataset/steps without inputs through the end-points. If there are multiple end-points, you can sort them, in order to provide a precedence.

Caching and scheduling Service Support​

Integration Rules support caching service (in order to speed-up the tasks) and scheduling services (in order to run the Integration Rule in unattended mode).

Integration Rule Logging and Error Tracking​

Integration rules support an advanced log/trace feature so that you can review executions and errors.

There are two types of executions:

  • Standard-mode: The Integration Rule runs based on the scheduling system.
  • Preview-mode: The Integration Rule runs in attended mode through a specific function.

Each step of an Integration Rule can be debugged and previewed independently so that you can review the execution before scheduling the final execution through scheduling services.