This document describes the database structure design of Exact Lightweight Integration Server (ELIS). The relationship between the tables and how the tables are linked to each other will be explained.
This table stores all the servers for ELIS that are connected to the database.
Unique identifier of the server
Logical name of the server
This table is used for multi-tenancy whereby multiple ELIS are linked to one database. The information of the servers is stored in this table.
Address of the endpoint
ID of the server information and this column refers to the Server table
This table stores the products that are installed in ELIS as extensions, for example, Exact Globe Next and Exact Synergy Enterprise.
Unique identifier for each product
Unique code to distinguish the different products, for example, Exact Synergy Enterprise and Exact Globe Next
Metadata of the endpoint package that describes the contents of the package
The time the product is created
This table stores the clients that are registered for each product, for example, different versions of a product that is installed in the same domain or different domains and machines. Every client is connected to the product by the ProductID.
Unique identifier of the client
Unique logical name selected for the client
Release version of the client
Indicates whether the client has been activated
Product ID of the client
Domain name indicating the location of the installed client
User name to connect to the client
Password to connect to the client
Additional settings about the client in the XML format, whereby the format of these settings depends on the product that the client belongs
ID of the tenant to which the client belongs
This table stores the information of thesolutions.
Unique identifier of the solution
Name of the solution
Description of the solution
A flag to identify if the solution is release-dependent
This table stores the information of the ELIS add-ons. Each add-on is related to a solution based on the SolutionID. The add-on binary files are stored in the Files table and accessible based on the DefaultConfigID and ServerConfigID fields.
Unique identifier of the add-on
ID of the solution to which the add-on belongs
Version number of the add-on
Service configuration that is stored in the Files table
Default configuration that is stored in the Files table
SDK version of the add-on which is used to check the compatibility with the SDK version of the ELIS console
This table stores the information of the ELIS extensions. However, this table is currently not in use because there is no interface in the ELIS management console to register the extensions. This table is related to the Files table based on the DefaultConfigID field.
Unique identifier of the extension
Name of the extension
Description of the extension
Extension of the version
ID of the extension configuration file that is stored in the Files table
This table indicates the product version that is supported by the add-on and the number of clients.
Unique identifier of the support information
ID of the add-on
Product that is supported by the add-on, and this field refers to the Code in the Products table
Product version that is supported by the add-on
Minimum number of clients that are supported by the add-on
Maximum number of clients that are supported by the add-on
This table stores the files that are supported by the add-on.
Unique identifier of the support file
ID that is referring to the Supports table
File ID that is supported by the add-on, and this field refers to the Files table
Each add-on will be activated based on a different set of clients with different configurations. This table stores all the add-ons that have been activated and the information of the configurations.
The add-on ID that is activated, and this field refers to the Addons table
ID of the configuration file for each activation
Name of the activation
Description of the activation
Indicates whether the configuration is active
This table stores the clients that are attached to the activation.
Activation that is linked to the client, and this field refers to the Activations table
Client that is attached to the activation, and this field refers to the Clients table
Indicates the status of the activation
This table stores the files that are used by ELIS including the configurations, libraries, and other files.
The entity to which the file belongs, such as product, add-on, and others
Name of the file
The file in binary format
This table stores the information of the messages so that the message echo will be blocked.
The activation ID that causes the echo, and this field refers to the Activations table
Synchronization key that is generated at the source node
Synchronization key that is generated at the target node
The date the message was created
This table stores the notification messages.
Unique identifier of the monitor
Unique identifier that is used to group the messages related to a particular operation
ID of the client that triggered the operation, and this field refers to the Clients table
ID of the activation of the message, and this field refers to the Activations table
The product line of the message, and this field refers to the Products table
The message received by ELIS
This is a reserved field for internal use
Indicates the components that are processing the message, whereby “0” is for ELIS and “1” is for the provider
An integer value that indicates the status of the message, whereby “0” is for received, “1” for pending, “2” for processing, “3” for successful, “4” for failed, "5" for re-trying, "6" for echo, and "7" for skipped
Remark that describes the additional information of the message
Date and time the message was received
Last date and time the message was modified
Number of times the message was processed
Entity on which the operation is performed
Action to be performed, such as create, read, update, and delete
This table stores the information of theoperations that have been performed by ELISand the errors that occurred during the operations.
Unique identifier of the log
ID of the client that is involved in the operation
ID of the add-on that is involved in the operation
Component that performs the operation
Method of performing the operation
Type of log, whereby “0” is for the information and “1” is for the error
Text message of the log
Stack trace to find the sequence of the methods that are involved in the operations
The time the log was created
This table stores the settings of ELIS. This table is currently used forSMTP server settings.
Property name of the setting
Value of the setting property
Integer value that indicates the setting of the entity, such as ELIS, add-on, activation, and client
ID of the entity
This table stores the information for thenotifications. Currently, only the recipient email address for each endpoint isstored.
Settings that separate the email addresses by commas
ID of the client that is related to the setting, and this field refers to the Clients table
This table stores the mapped entitiesbetween the various clients. This table facilitates the key lookup processduring data synchronization between the clients.
ID of the source client, and this field refers to the Clients table
ID of the entity at the source node
ID of the destination node, and this field refers to the Clients table
ID of the entity at the destination node
Entity that has to be mapped
This table stores the information of thetenants.
Name of the tenant
Description of the tenant
This table stores the ELIS license.
Name of the license
Type of license
Issuing date of the license
Activation date of the license
Expiry date of the license
This table stores the information of the jobs for the background task scheduler.
Name of the job
Description of the job
Details of the configuration UI
Allow concurrent execution flag
Continue execution if error flag
Type of job
Entity unique identifier
This table stores the information of the job activations.
Details of the configuration
Date and time of the last execution
Enable the flag
This table stores the information of the job tasks.
Process isolation flag
This table stores the information of the job triggers.
Date and time of the last execution
Date and time of the next execution
Job schedule data
Type of trigger