Database documentation for Exact Lightweight Integration Server (ELIS)
Introduction
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.
Table description
Server
This table stores all the servers for ELIS that are connected to the database.
Column
|
Description
|
ServerID
|
Unique identifier of the server
|
InstanceName
|
Logical name of the server
|
LinkedServers
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.
Column
|
Description
|
LinkedServerID
|
Unique identifier
|
InstanceName
|
Logical name of the server
|
Endpoint
|
Address of the endpoint
|
ServerID
|
ID of the server information and this column refers to the Server table
|
Products
This table stores the products that are installed in ELIS as extensions, for example, Exact Globe Next and Exact Synergy Enterprise.
Column
|
Description
|
ID
|
Unique identifier for each product
|
Code
|
Unique code to distinguish the different products, for example, Exact Synergy Enterprise and Exact Globe Next
|
Name
|
Product name
|
Description
|
Product description
|
Metadata
|
Metadata of the endpoint package that describes the contents of the package
|
CreationTime
|
The time the product is created
|
Clients
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.
Column
|
Description
|
ClientID
|
Unique identifier of the client
|
LogicalName
|
Unique logical name selected for the client
|
Release
|
Release version of the client
|
Active
|
Indicates whether the client has been activated
|
ProductID
|
Product ID of the client
|
Domain
|
Domain name indicating the location of the installed client
|
UserName
|
User name to connect to the client
|
Password
|
Password to connect to the client
|
Properties
|
Additional settings about the client in the XML format, whereby the format of these settings depends on the product that the client belongs
|
TenantID
|
ID of the tenant to which the client belongs
|
Solutions
This table stores the information of thesolutions.
Column
|
Description
|
SolutionID
|
Unique identifier of the solution
|
Name
|
Name of the solution
|
Description
|
Description of the solution
|
IsSpecificClientRelease
|
A flag to identify if the solution is release-dependent
|
Add-on
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.
Column
|
Description
|
AddonID
|
Unique identifier of the add-on
|
SolutionID
|
ID of the solution to which the add-on belongs
|
Version
|
Version number of the add-on
|
ServiceConfigID
|
Service configuration that is stored in the Files table
|
DefaultConfigID
|
Default configuration that is stored in the Files table
|
SDKVersion
|
SDK version of the add-on which is used to check the compatibility with the SDK version of the ELIS console
|
Extensions
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.
Column
|
Description
|
ExtensionID
|
Unique identifier of the extension
|
Name
|
Name of the extension
|
Description
|
Description of the extension
|
Version
|
Extension of the version
|
DefaultConfigID
|
ID of the extension configuration file that is stored in the Files table
|
Supports
This table indicates the product version that is supported by the add-on and the number of clients.
Column
|
Description
|
SupportID
|
Unique identifier of the support information
|
AddonID
|
ID of the add-on
|
ProductID
|
Product that is supported by the add-on, and this field refers to the Code in the Products table
|
Release
|
Product version that is supported by the add-on
|
Min
|
Minimum number of clients that are supported by the add-on
|
Max
|
Maximum number of clients that are supported by the add-on
|
SupportFiles
This table stores the files that are supported by the add-on.
Column
|
Description
|
SupportFileID
|
Unique identifier of the support file
|
SupportID
|
ID that is referring to the Supports table
|
FileID
|
File ID that is supported by the add-on, and this field refers to the Files table
|
Activations
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.
Column
|
Description
|
ActivationID
|
Unique identifier
|
AddonID
|
The add-on ID that is activated, and this field refers to the Addons table
|
ConfigFileID
|
ID of the configuration file for each activation
|
Name
|
Name of the activation
|
Description
|
Description of the activation
|
Active
|
Indicates whether the configuration is active
|
TenantID
|
ID of the tenant to which the client belongs
|
ActivationClients
This table stores the clients that are attached to the activation.
Column
|
Description
|
ID
|
Unique identifier
|
ActivationID
|
Activation that is linked to the client, and this field refers to the Activations table
|
ClientID
|
Client that is attached to the activation, and this field refers to the Clients table
|
Active
|
Indicates the status of the activation
|
Files
This table stores the files that are used by ELIS including the configurations, libraries, and other files.
Column
|
Description
|
FileID
|
Unique identifier
|
EntityID
|
The entity to which the file belongs, such as product, add-on, and others
|
Name
|
Name of the file
|
Binary
|
The file in binary format
|
EchoLog
This table stores the information of the messages so that the message echo will be blocked.
Column
|
Description
|
ID
|
Unique identifier
|
ActivationID
|
The activation ID that causes the echo, and this field refers to the Activations table
|
SourceSyncKey
|
Synchronization key that is generated at the source node
|
TargetSyncKey
|
Synchronization key that is generated at the target node
|
CreatedDate
|
The date the message was created
|
Monitors
This table stores the notification messages.
Column
|
Description
|
ID
|
Unique identifier of the monitor
|
CorrelationID
|
Unique identifier that is used to group the messages related to a particular operation
|
ClientID
|
ID of the client that triggered the operation, and this field refers to the Clients table
|
ActivationID
|
ID of the activation of the message, and this field refers to the Activations table
|
ProductLine
|
The product line of the message, and this field refers to the Products table
|
Message
|
The message received by ELIS
|
Reference
|
This is a reserved field for internal use
|
ProcesType
|
Indicates the components that are processing the message, whereby “0” is for ELIS and “1” is for the provider
|
Status
|
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
|
Remark that describes the additional information of the message
|
ReceivedDate
|
Date and time the message was received
|
ModifiedDate
|
Last date and time the message was modified
|
Retry
|
Number of times the message was processed
|
Entity
|
Entity on which the operation is performed
|
Action
|
Action to be performed, such as create, read, update, and delete
|
LogicalKey
|
Entity key
|
Logs
This table stores the information of theoperations that have been performed by ELISand the errors that occurred during the operations.
Column
|
Description
|
ID
|
Unique identifier of the log
|
ClientID
|
ID of the client that is involved in the operation
|
AddonID
|
ID of the add-on that is involved in the operation
|
Component
|
Component that performs the operation
|
Method
|
Method of performing the operation
|
Type
|
Type of log, whereby “0” is for the information and “1” is for the error
|
LogText
|
Text message of the log
|
StackTrace
|
Stack trace to find the sequence of the methods that are involved in the operations
|
Time
|
The time the log was created
|
Settings
This table stores the settings of ELIS. This table is currently used forSMTP server settings.
Column
|
Description
|
ID
|
Unique identifier
|
Name
|
Property name of the setting
|
Value
|
Value of the setting property
|
Level
|
Integer value that indicates the setting of the entity, such as ELIS, add-on, activation, and client
|
EntityID
|
ID of the entity
|
NotificationSettings
This table stores the information for thenotifications. Currently, only the recipient email address for each endpoint isstored.
Column
|
Description
|
ID
|
Unique identifier
|
Settings
|
Settings that separate the email addresses by commas
|
ClientID
|
ID of the client that is related to the setting, and this field refers to the Clients table
|
KeyLookupString, KeyLookupInt, KeyLookupGUID
This table stores the mapped entitiesbetween the various clients. This table facilitates the key lookup processduring data synchronization between the clients.
Column
|
Description
|
ID
|
Unique identifier
|
Source
|
ID of the source client, and this field refers to the Clients table
|
SourceKey
|
ID of the entity at the source node
|
Destination
|
ID of the destination node, and this field refers to the Clients table
|
DestinationKey
|
ID of the entity at the destination node
|
Entity
|
Entity that has to be mapped
|
Tenants
This table stores the information of thetenants.
Column
|
Description
|
TenantID
|
Unique identifier
|
Name
|
Name of the tenant
|
Description
|
Description of the tenant
|
ELISLicense
This table stores the ELIS license.
Column
|
Description
|
CustomerID
|
Unique identifier
|
Name
|
Name of the license
|
Type
|
Type of license
|
Number
|
License number
|
SequenceNumber
|
Sequence number
|
IssueDate
|
Issuing date of the license
|
ActivationDate
|
Activation date of the license
|
ExpirationDate
|
Expiry date of the license
|
CheckSum
|
Check sum
|
Division
|
Division ID
|
Certificate
|
License certificate
|
Jobs
This table stores the information of the jobs for the background task scheduler.
Column
|
Description
|
JobID
|
Unique identifier
|
Name
|
Name of the job
|
Description
|
Description of the job
|
ConfigurationUI
|
Details of the configuration UI
|
AllowConcurrentExecution
|
Allow concurrent execution flag
|
ContinueOnError
|
Continue execution if error flag
|
JobType
|
Type of job
|
EntityID
|
Entity unique identifier
|
JobActivations
This table stores the information of the job activations.
Column
|
Description
|
JobActivationID
|
Unique identifier
|
JobID
|
Unique identifier
|
Name
|
Name of the job
|
EntityID
|
Entity unique identifier
|
Configuration
|
Details of the configuration
|
LastExecuted
|
Date and time of the last execution
|
ExecutionCounter
|
Execution counter
|
Enable
|
Enable the flag
|
JobTasks
This table stores the information of the job tasks.
Column
|
Description
|
TaskID
|
Unique identifier
|
JobID
|
Unique identifier
|
Name
|
Name of the job
|
ExeIndex
|
Execution index
|
Isolated
|
Process isolation flag
|
[Assembly]
|
Assembly
|
JobTriggers
This table stores the information of the job triggers.
Column
|
Description
|
TriggerID
|
Unique identifier
|
JobActivationID
|
Unique identifier
|
Name
|
Name of the job
|
LastExecuted
|
Date and time of the last execution
|
NextExecution
|
Date and time of the next execution
|
Data
|
Job schedule data
|
TriggerType
|
Type of trigger
|
Related documents
Main Category: |
Support Product Know How |
Document Type: |
Online help main |
Category: |
On-line help files |
Security level: |
All - 0 |
Sub category: |
Details |
Document ID: |
26.181.483 |
Assortment: |
Exact Synergy Enterprise
|
Date: |
24-05-2016 |
Release: |
254 |
Attachment: |
|
Disclaimer |