TDM 7.2 Demo Project - Setup and Implementation Guidelines

Databases Setup

The TDM demo project is aligned with TDM V7.2 and is based on PostgreSQL databases:

The target DBs are empty and the source DBs are populated with customers.

Creating the Demo DBs in the Local PostgreSQL DB

1. Download the SQL script and the DB backup files from the Demo DBs directory.

2. Create the demo databases in PostgreSQL:

   Windows PostgreSQL Installation

   • Go to the script's directory and open a powershell window.

   • Then run the following command to run the script and create the CRM, Billing, Orders, and Collection DB users and schemas on the PostgreSQL DB:

     & "[PostgreSQL DB exe file full path]" -Upostgres --host [PG ip address] --port [DB port] -f "create_resources.sql"

     Example:

   & "C:\Program Files\PostgreSQL\9.6\bin\psql.exe" -Upostgres --host localhost --port 5432 -f "create_resources.sql"

Docker PostgreSQL Installation

• Copy the create_resources.sql script to the docker container:

   docker cp create_resources.sql [docker name]:path 
  

  • Run the script to create the Demo DBs and DB users:

   psql -h localhost -p 5432 -U postgres -d postgres -f /usr/local/create_resources.sql
  

1. Open pgAdmin 4 and start restoring the databases from backup files. It is recommended to chek the Clean before restore option when restoring the backup file.

Note that TDM DB must be created in PostgreSQL as a part of the TDM Installation.

Fabric Implementation

1. Open the Fabric Studio 6.5.1 and create a new project.
2. Download the TDM Demo project export file (format .k2export) and import it to your project. All of the characteristics of the TDM Demo project will appear.
3. The interfaces and of the TDM Demo project might need some modification, edit them if needed (you might be working locally or remotely, for example). Note that the Server setting must be populated by localhost when using local DBs or dockers for the DBs.
4. Open the DB_CASSANDRA interface, and check if the k2masking keyspace exits. If it does not exist, create it using the masking-create-cache-table.flow from the library of Broadway examples or create_masking_cache_table.sql of the TDM Library.
5. Edit the SRC and TAR environments:
   • If you use a Fabric docker and a local PG DBs, populate the Server setting of the PG interfaces with host.docker.internal.
   • If you use a docker for the PG and Cassandra DBs, populate the Server setting with the docker's internal IP address (run hostname -I command in the docker to get the internal IP address).
6. Deploy the Environments to Fabric.
7. Deploy the LUs and Web-Services to Fabric. Note that you must deploy the Environments before running Data Viewer on the LUs, since the main Target LU table sets the target ("TAR") environment to be the active environment.

TDM GUI Definitions

1. Create a Customer Business Entity (BE) that includes the following LUs:

   • Customer
   • Billing
   • Orders
   • Collection

   Below is the BE's structure:

   

2. Create the following products:

   • CRM product. Attach the Customer LU to this product. You can populate the product_version by any String.
   • BILLING product. Attach the Billing LU to this product. Note that PAYMENT table of TAR_BILLING_DB has an additional column: PAYMENT_METHOD. The load flow of PAYMENT table supports two product versions - PROD and DEV - and populates a default value in PAYMENT_METHOD when the product version is 'DEV'. Add two product versions to the BILLING product -PROD and DEV - to test this implementation.
   • ORDERS product. Attach the Orders LU to this product. You can populate the product_version by any String.
   • COLLECTION product. Attach the Collection LU to this product. You can populate the product_version by any String.

3. Create the following environments:

   • SRC:

     • Set Environment Type setting to Source.
     • Set Fabric Environment Name setting to SRC.
     • Add the products to this environment.
     • Set the version of the BILLING product to PROD.

   • TAR:

     • Set Environment Type setting to Both to enable running Data Flux tasks on this environment.
     • Set Fabric Environment Name setting to TAR.
     • Add the products to this environment.
     • Set the version of the BILLING product to DEV.

​

See instructions on how to work with the TDM GUI in the following link.

Now you are ready to create and execute TDM tasks based on the TDM Demo implementation.