Integration Engine

The Integration Engine for Novacura Flow serves as a robust middleware component that facilitates seamless data exchange and workflow automation between various enterprise systems, applications, and databases utilizing the capability of Novacura Flow machine workflows and connectors.

Key Components and Features

1. Connectivity

   Support for various protocols and standards like REST, SOAP, FTP, SFTP, and IFS OData, to connect with different systems such as ERP (e.g., IFS, SAP, Infor), databases (e.g., SQL Server, PLSQL), and other legacy systems. List available here: Novacura Connectors.

2. Data Transformation & Mapping

   AI-assisted data transformation using a low-code transformation configuration for each integration. Support for Liquid and XSLT transformation.

3. Workflow Orchestration

   Design, execute, and monitor complex workflows that span across multiple systems and data sources using Novacura Flow.

4. Scaleability Architecture

   Ability to handle high volumes of data and transactions with low latency.

5. Monitoring

   Real-time monitoring of integration processes with dashboards and alerts for proactive issue resolution.

6. Deployment

   Cloud, On-premise, and Hybrid Deployments. Flexible deployment options to meet the specific needs of the organization.

7. Triggers & Queue

   Execute workflows with support for HTTP, and scheduled triggers, Execute each integration workflow using queuing that supports FIFO.

Benefits

• Enhanced Operational Efficiency: Streamlined processes and automated workflows reduce manual efforts and operational overhead.

• Improved Data Accuracy: Ensures consistent and accurate data across systems, minimizing errors and discrepancies.

• Faster Time to Market: Pre-built connectors and a low-code environment enable quicker deployment of integration solutions using Novacura Flow.

• Cost Savings: Reduced integration development and maintenance costs through reusable components and simplified management.

• Agility and Flexibility: Ability to quickly adapt to changing business needs and integrate new systems as the organization grows.

Disadvantages

• Processing Time: Depending on the complexity of the transformation rules, data routing, and volume of messages, the integration engines may introduce latency into data transactions. This can impact time-sensative workflows, especially in processes where real-time transactions are critical. In this use case, standard machine workflows are recommended.