Semarchy Convergence for DI Architecture | ||
---|---|---|
Previous | Next | |
Preface | System Requirements |
Semarchy Convergence for DI is composed of three components:
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.
The runtime exposes different services:
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.
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.
properties\engineScheduler.properties
defines the schedule storage location. This file is optional.
properties\engineParameters.xml
contains the other parameters of the runtime.
The
engineParameters.xml
file refers to other configuration files, including:
properties\engineParameters.xml
properties\engines\commonParameters.xml
properties\engines\engineParameters42000.xml
properties\logs\logH2.xml
When modifying these files, the runtime must be restarted. The parameters available in these files are described later in this document.
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
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.
Previous | Top | Next |
Preface | System Requirements |