Data Sink Configuration

Data clients can be configured to receive extraction results (linkage map data) for specific data sources, or for all data from the server. For the latter, LinXmart must be configured to allow the data client to receive all of this data.

For a specific data source, the LinkageMapSink property defines the details of where extraction results are stored. For the general receive-all, a LinkageMapSink property can be defined at the same level as the DataSources property. Either way, the configuration settings are the same for both, but are located in different areas within the appsettings.json file.

The properties of a data sink are described below:

Property	Description
Type	The LinXmart Data Client supports one connection type for data sinks: SQL Server (Microsoft SQL Server)
Properties	These are properties specific to the data source type: ConnectionString - the full connection string to the data source in the format required by the Type CredentialsName - (optional) if a username/password combination is required for the connection string, you can instead specify the name of the credentials stored in the service account user's credential store - it will add these to the connection string at runtime Table - the name of the table to write data AppendProjectCodeToTable - flag indicating if the table name should have the project code appended CreateTableIfRequired - flag indicating if the table should be created if it doesn't exist DeleteExisting - flag indicating if existing data for the extraction project and event type should be deleted before new data is written
ColumnMapping	A mapping of linkage map properties to column names in the destination. The following mappings are mandatory: ProjectCode EventTypeCode SourceUniqueId PersonKey The following are optional. If they are omitted from the appsettings.json configuration, they will be ignored: SourcePersonId ExtractionProjectId LinkageProjectPersonKey

info

PostgreSQL and ODBC are not currently supported as data sinks.

If you want to create a compatible table yourself, an example creation script for SQL Server for all fields is shown below.

CREATE TABLE [dbo].[LXM_Extraction_Results] (
    [ProjectCode] [nvarchar](50) NULL,
    [EventTypeCode] [nvarchar](50) NULL,
    [SourceUniqueId] [nvarchar](100) NULL,
    [SourcePersonId] [nvarchar](100) NULL,
    [PersonKey] [nvarchar](100) NULL,
    [ExtractionProjectId] [nvarchar](100) NULL,
    [LinkedProjectPersonKey] [nvarchar](100) NULL
);