Tutorial Scenario Resolution - Part 1: Simple model

For this first part of the tutorial, we will use the case explained here Tutorial Scenario, but we will focus on a basic model with 1 Hub and 1 Satellite.

In order to reproduce this model,

1. Create a Project “dFakto Cars”

2. Create an Environment

3. Integrate the source system HR

4. Create a Hub Employee

5. Create the mapping for the hub and the satellite

6. Deploy Version

7. Load data in the datavault
   

Resolution

1. Create a Project “dFakto Cars”

   1. Select the projects dropdown list

   2. Create a new project and name it “dFakto_Cars_Tuto”
      

      

      
      

2. Create an Environment “main”

   1. Go to the “⚙️ Configure Project” section

   2. Click on the “+Create Environment” button

   3. Set the environment name as “main”

   4. Check the box “Use for Modelling”

   5. Select the database server type “POSTGRESQL”

   6. Click on Save
      

      

      You will know that your environment has been successfully created when the following wizard appears on the top right of the screen:

      

      
      

3. Create Source System “HR” in Sources Management

   1. Go to the “Sources Management” section

   2. Click on the “+Create a Source System” button

   3. Define the Name as “HR”

   4. Define the Code as “s01”

   5. Click on the “Save” button
      

      

      You will know that your source system has been successfully created when the following wizard appears on the top right of the screen:

      

   6. Click on the “+Create a Data Package“ button

   7. Define the name as “hr_employee”

   8. Click on the “Save” button
      

      

      You will know that your data package has been successfully created when the following wizard appears on the top right of the screen:

      

      
      

   9. Create a new staging table by clicking on the “+Create a Staging Table“ button

   10. Select the option “Create a new table”

   11. Select the creation method “Import a file (CSV,Excel)”

   12. Click on the “Next” buttonhr_employee” by importing a file in your environment
       

       

   13. Define the table name as “hr_employee”

   14. Click on the “+Browse” button to retrieve the excel file “hr_extract”

   15. Define the Sheet Name as “employee” (this corresponds to the name of the tab in the excel file)

   16. Click on the “Save” button
       

       

       You will know that your staging table has been successfully created when the following wizard appears on the top right of the screen:

       

       
       

       Impact in the database:

4. 

   Create a Hub “Employee”

   1. Go to the Modelization section, to the Entities tab (note that this is also feasable through Network graph tab).

   2. Go to Hubs tab

   3. Create a new hub by hitting the “+Create Hub” button

   4. Set the hub name as “Employee”

   5. Set the Business Key Length as “25”

   6. Click on the “Save” button
      

      

      You will know that your Hub has been successfully created when the following wizard appears on the top right of the screen:

      

      
      

5. Mapping for the Hub Employee

   1. Go to the Sources Management Section

   2. Edit the staging table to access the mapping “section”
      

      

   3. in the Hubs tab, hit the “+Create a New Mapping” button
      

      

   4. Set the mapping name as “EmployeeBk” (follow the convention “HubName” + “Bk”)

   5. Select an existing hub (here Employee)

   6. Check the box “Invalidate data”

   7. Select the column containing the business key

   8. Click on the “Save” button
      

      

      You will know that your hub mapping has been successfully created when the following wizard appears on the top right of the screen:

      

      
      

   9. Create a satellite by hitting the “+Create a New Mapping“ button in the Satellites tab

   10. Set the satellite name as “hr_info” (following the convention “source-name_info”)

   11. Set the mapping name hEmployee (hHubName or lLinkName for satellites of links)

   12. Attach to the mapping of the Hub Employee.

   13. Select columns that are not bk or fk

   14. Click on “Save”
       

       

       You will know that your satellite has been successfully created when the following wizard appears on the top right of the screen:

       

       Your model should now look like the scheme below
       

       

       
       

6. Deploy the version

   1. Go to the “🚀 Releases Management” section

   2. Create a new version

   3. Name it 1.0

   4. Click on Save
      

      

   5. Deploy the version you just created

   6. Select the right environment

   7. Deploy
      

      

   8. a summary wizard will pop-up showing you all tasks ready for execution

   9. Click on Deploy

      

      
      

7. Load data into the datavault by executing the state machine related to the data package employee on the Orchestrator

   1. Go to the Orchestrator (States)

   2. Go to the State Machines tab

   3. Find the state machine related “dFakto_Cars_Tuto-main-hr_employee” and click on the eye button to open details
      

      

      
      

   4. Launch a new execution (in principles, nothing else is required, if you can’t successfully launch the execution, try the command: {} )

   5. 

      

      Data are now available in the datavault schema in the database.
      

      

Naming Convention

• for Hub

  • mapping Name: “Name of concept” + “Bk” (ex: for the concept employee, mapping name = “EmployeeBk”).

• for Satellites

  • Satellite name: “Source Name” + “_info” → (ex: for the satellite of hub employee from source CRM → satellite name = “crm_info”

  • hHubName if the satellite refers to a hub and lLinkName if it’s a link. → mapping name = “hEmployee”
    or
    Mapping name: “Concept Name” + “Source Name” → (ex. for the hub employee of source crm → mapping name = “employee_crm”