In the AdapLink Framework Data Exchange Configuration application performs the functions of ETL(Extract, Transform, and Load).
Using AdapLink DX Configuration you can perform the following:
- Tabular Mapping - (Also Called Column Based Mapping / direct One-to-One Mapping)
In this migration kind, the transform stage applies a series of business rules or functions to the extracted data at each column level from the source, to derive meaningful set of data for loading into the end target..
- Rules Based Mapping : (Also called Row Based Mapping / RBA Projects)
In this migration kind, the transform stage applies a series of business rules or functions to the extracted data at each row level from the source, to derive meaningful set of data for loading into the end target.
An easy way to understand AdapLink DX Configuration is to consider a scenario. Here we will consider a simple scenario on transferring Data from an Excel Spreadsheet (Source) to MS-SQL Database(Target). In this example, we will walk through the different components of the AdapLink DX Configuration.
An Overview of the AdapLink DX Screen
As shown in the screen-shot above, following are the important fields in AdapLink DX profile Editor:
Note
Find below step-by-step instructions for AdapLink DX flow to transfer data from excel file to database.
A pop-up screen will appear as shown above to create a new DX-Profile.
In this section, we configure the Data-Source for the scenario. In this case its an Excel file.
In this section, we configure the Target-System for the scenario. In this case its a MS-SQL Database.
Note
In this section, we establish the relationship between the source and the target.
In AdapLink-DX Context, we call this as TS-PAIR Mapping.
Some of the important fields in the TS-Pair Header Attributes, are listed below
Note
TS-PAIR header information for this scenario
| Field names | Explanation |
|---|---|
| Migration_Kind | Its of 2 kind.
In this example we choose Tabular, because its direct column level mapping. |
| Update_Mode | Update Mode has 3 modes.
|
| Package_Size | This sets the batch size for Selecting source data and writing target data in Batch size. (0 means no Batch-size) |
| Max_Record | This Sets the Maximum output records. For Example, if you set this to 10, then only 10 records are written to the Target) |
| Insert_Hidden_Cols | All the columns which does not have target mapping will be inserted with default values. (0 for integer , and “” for Strings,Text etc.) |
| Update_Statistics | This calls the “Update Statistics Query” where applicable. (For example in MS-SQL, this calls the Update Statistics query for better performance) |
| TS-Pair_Name | In a profile, as you can have multiple TS-Pairs, each should have a Unique name |
In this section, we define more attributes of the source-system.
Source-File Details
Note
Lets take a look at the source-file. This will help to configure source-meta section.
Configure Source-Meta based on the source-file above
In this section, we define more attributes of the Target-meta details.
Note
Lets take a look at the target System. In this case its a database table Employee_Master created under demo database.
Configure Target-Meta based on the target-database table above
In this section, we configure one-to-one column mapping between the source-meta and target-meta that were defined/configured in the above steps.
Note
In the Tabular mapping, the convention that is followed for column mapping is Left part of (<-) indicator is the Target and Right part is the source.
| Field names | Explanation |
|---|---|
| Target_Field | This field is actual column name in the target database table |
| Source_Field | This field is actual column name in the source file |
| Default_Value | This field is used in many ways.
|
| Target_Length | This field is used ONLY WITH FIXED WIDTH files. It specifies the width of output Column |
| Data_Type | This field is used to set the Target field data type. Currently there are following data-types available
|
| Target_Format | |
| Source_Format | |
| Skip_if_Empty |
In this section, we configure selection-criterion for the source-data. In AdapLink-DX Context we call it as Source-Selection.
This concept is similar and can be compared to Simple where clause in SQL Context.
Note
Lets take an example, to understand how to configure Source-selection in AdapLink-DX.
For the scenario, lets bring only those records where city = Lakeland as shown below.
Lets configure Source-section in AdapLink-DX from the source-file above
This completes the steps for configuring AdapLink-DX profile.