Semarchy Convergence for DI Architecture

Architecture Overview

Semarchy Convergence for DI is composed of three components:

The Runtime Engine

Overview

A runtime is a Java component in charge of executing the data integration flows.
Execution reports (session logs) as well as schedules handled by the runtime are saved in a database.

Runtime Engine Services

The runtime exposes different services:

Runtime Engine Ports

The runtime may open several ports on startup:

Depending on the configuration and the runtime engine usage, these ports should be accessible from the network, and the network should be configured accordingly.
Changing the default value for these ports is explained later in this document.

Configuring the Runtime

By default, the runtime stores session logs and schedules in an embedded H2 database.

The various parameters of the runtime are store in files in the properties sub-folder.

The engineParameters.xml file refers to other configuration files, including:

When modifying these files, the runtime must be restarted. The parameters available in these files are described later in this document.

Configuring Debug Logs

The runtime also stores debug logs in the log folder. Logging uses Apache Log4J and is configured via the log4j.xml file. By default, the debug log files are rotating, which means that the log folder cannot exceed a certain size.

Debug Logs configuration may be changed by the administrator, or when Semarchy support requests it

Semarchy Convergence for DI Analytics

The Semarchy Convergence for DI Analytics component runs in an Application Server such as Apache Tomcat.

It is used to:

Semarchy Convergence for DI Analytics is provided as a WAR file to deploy in the application server.

Note: For more information about installing and configuring Semarchy Convergence for DI Analytics refer to this product’s documentation.