Contents x
    Data Exchange Settings
    • 23 Aug 2024
    • 2 Minutes to read
    • Dark
      Light
    Contents

    Data Exchange Settings

    • Updated on 23 Aug 2024
    • 2 Minutes to read
    • Dark
      Light
    Article summary

    General

    The data exchange functionality can be used to improve monitoring. When enabled, Mail & Deploy will write all execution information and logs into a database.

    Managing Data Exchange Settings

    To configure data exchange settings you have to connect to the Management Service of Mail & Deploy, click the Settings item in the main menu, and then click the Data Exchange tile.

    Properties

    You can set the following properties:

    Name

    		Description
    Datasource TypeThe type of database to write exchange data to.

    (None). If you select this option the data exchange feature is deactivated.

    Local SQLite Database. When you select this option, Mail & Deploy writes all execution logs into an  SQLite Database located in the Data\Exchange\Database.s3db file. You can find ODBC drivers required to create ODBC connections to SQLite database in the Data\Exchange directory. The file sqliteodbc.exe installs 32bit ODBC drivers, the file sqliteodbc_w64.exe installs 64bit ODBC drivers.

    Microsoft SQL Server. If you select this option you can specify details of a Microsoft SQL Server database to which exchange data will be written (see below for the required tables in that database).

    MySQL. If you select this option you can specify details of a MySQL database to which exchange data will be written (see below for the required tables in that database).
    LanguageThe language in which log files will be written to the database.

    Microsoft SQL Server Database Structure

    If you select a Datasource Type of Microsoft SQL Server you need to make sure that the database specified contains the following two tables:

    Executions

    CREATE TABLE [dbo].[Executions](
    [ExecutionId] [nvarchar] (36) NOT NULL,
    [StartDateTimeUtc] [datetime] NULL,
    [EndDateTimeUtc] [datetime] NULL,
    [Result] [nvarchar] (50) NULL,
    [ExecutionType] [nvarchar] (255) NULL,
    [ExecutionTrigger] [nvarchar] (255) NULL,
    [WorkspaceName] [nvarchar] (255) NULL,
    [TaskName] [nvarchar] (255) NULL,
    [ReportName] [nvarchar] (255) NULL,
    [ExportDatasource] [nvarchar] (255) NULL,
    [ExportDatasourceObject] [nvarchar] (255) NULL,
    [SubscriptionType] [nvarchar] (255) NULL,
    [SubscriptionName] [nvarchar] (255) NULL,
    [SubscriptionUser] [nvarchar] (255) NULL,
    [AlertName] [nvarchar] (255) NULL,
    [AlertUser] [nvarchar] (255) NULL,
    [RequestedByUser] [nvarchar] (255) NULL,
    [NumberOfCreatedReportDocuments] [int] NULL,
    [JobNumber] [int] NULL)

    ExecutionLogEntries

    CREATE TABLE [dbo].[ExecutionLogEntries](
    [ExecutionLogEntryId] [nvarchar] (36) NOT NULL,
    [ExecutionId] [nvarchar] (36) NULL,
    [Order] [int] NULL,
    [DateTimeOfOccurrenceUtc] [datetime] NULL,
    [Type] [nvarchar] (50) NULL,
    [Message] [text] NULL,
    [AdditionalInformation] [text] NULL,
    [StackTrace] [text] NULL)

    MySQL Database Structure

    If you select a Datasource Type of MySQL you need to make sure that the database specified contains the following two tables:

    Executions

    CREATE TABLE `Executions` (
    `ExecutionId` VARCHAR(36) NOT NULL COLLATE 'utf8mb3_general_ci',
    `StartDateTimeUtc` DATETIME NULL DEFAULT NULL,
    `EndDateTimeUtc` DATETIME NULL DEFAULT NULL,
    `Result` VARCHAR(50) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `ExecutionType` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `ExecutionTrigger` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `WorkspaceName` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `TaskName` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `ReportName` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `ExportDatasource` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `ExportDatasourceObject` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `SubscriptionType` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `SubscriptionName` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `SubscriptionUser` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `AlertName` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `AlertUser` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `RequestedByUser` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `NumberOfCreatedReportDocuments` INT(11) NULL DEFAULT NULL,
    `JobNumber` INT(11) NULL DEFAULT NULL,
    PRIMARY KEY (`ExecutionId`) USING BTREE)

    ExecutionLogEntries

    CREATE TABLE `ExecutionLogEntries` (
    `ExecutionLogEntryId` VARCHAR(36) NOT NULL COLLATE 'utf8mb3_general_ci',
    `ExecutionId` VARCHAR(36) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `Order` INT(11) NULL DEFAULT NULL,
    `DateTimeOfOccurrenceUtc` DATETIME NULL DEFAULT NULL,
    `Type` VARCHAR(50) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
    `Message` TEXT NULL DEFAULT NULL COLLATE 'utf8mb4_general_ci',
    `AdditionalInformation` TEXT NULL DEFAULT NULL COLLATE 'utf8mb4_general_ci',
    `StackTrace` TEXT NULL DEFAULT NULL COLLATE 'utf8mb4_general_ci',
    PRIMARY KEY (`ExecutionLogEntryId`) USING BTREE)

    Was this article helpful?
    What's Next