Knowledge Base Academy Community My Tickets
Fabric 7.2
Fabric 8.0 Fabric 7.2 Fabric 7.1 Fabric 7.0 Fabric 6.5 Fabric 6.4

Fabric TDM Library

The TDM Library has all the utilities required for implementing a TDM project and for running TDM execution processes. It holds the following:

The TDM Library must be imported to the Fabric project created for TDM.

TDM Library - Shared Objects

TDM Web Services

Import and deploy all TDM Web Services (APIs) to the Fabric project. These Web Services are invoked by the TDM Portal application and they comprise the back-end layer of the TDM Portal application.

As the TDM categories contain the product's Web Services, it is recommended to add the project's Web Services into separate categories in order to simplify the TDM version upgrading.

Generic TDM Interfaces

Import and deploy the following interfaces into the project's Shared Objects:

  • DB_CASSANDRA - this is the connection to the Cassandra DB. This interface is used by TDM utilities. Edit the IP address according to the environment.

  • CASSANDRA_LD - a Cassandra Loader interface. This interface is used by the Reference upgrade script (upgrade to TDM 7.5.1).

  • POSTGRESQL_ADMIN - this is the admin connection to the TDM PosgreSQL DB. This interface is used by the TDMDB flow in the TDM LU to create the TDM DB in the PostgreSQL DB.

  • TDM - this is the connection to the TDM PosgreSQL DB. Edit the IP address according to the environment.

    Note that if you work on a PostgreSQL with an SSL connection, you must edit the custom connection string of the POSTGRESQL_ADMIN and the TDM interfaces as follows:

    • jdbc:postgresql://[ip address]:5438/TDMDB?stringtype=unspecified&ssl=true&sslmode=verify-ca&sslrootcert=[full path of the .crt file]
    • Example:
      • jdbc:postgresql://localhost:5438/TDMDB?stringtype=unspecified&ssl=true&sslmode=verify-ca&sslrootcert=C:\k2view\pgSSL\cert\k2v_CA.crt

  • FabricRedis - this is the Redis interface that connects to the environment's Redis storage. The Redis interface can be used for the sequence implementation. Edit the IP address and populate it with the IP address of the TDM server. Note that from Fabric 7.1 onwards, the sequence Actors can get the next sequence value from a newly created DB sequence in the sequence interface (the sequence interface can be the TDM DB). The sequence is created by the Actor, if it doesn't yet exist. It is therefore recommended to get the next value from a DB sequence instead of using the Redis.

    For more information, view the Sequence Implementation Guide.

  • TDM_APIDOC_JSON - this is a local file system interface, used for generating the JSON file of the TDM APIDOC if the APIDOC needs to be updated to include project custom APIs. Click here for more information about updating the TDM APIDOC.

    It is important to set the TDM_APIDOC_JSON interface as disabled in the Environments in order to prevent errors when running the test connection on the task's environment (the Fabric server has a different IP address than the local Windows machine and cannot connect to the local machine's directory).

Shared Globals

Import the list of shared global variables required for executing TDM in your project.

Shared Functions

TDM shared functions are saved in the TDM Logic file.

Import the TDM shared functions to your project. Note that since the TDM category contains the product's functions, it is recommended to add the project's shared functions to a separate category (Logic file) in order to simplify the TDM version upgrading.

TDM Library - MTables

TDM 8.1 replaces the previous TDM translation with MTables to support a development of the TDM on both Fabric Studios: Desktop-Studio and Web-Studio.

The following MTables have been added to the References in the TDM library. Note that you must deploy the Reference to Fabric after updating the MTables:

Item 

Description 

Instructions 

MigrateList

Define the query and interface name, or the Broadway flow to generate the entity list when running the extract task on all entities of each LU; one record per LU.

Populate this table for each Logical Unit. A separate record must be created for each Logical Unit in the Fabric project apart from TDM, TDM_LIBRARY and the dummy LU of the post-execution processes.  

If there is a need to define a query per source environment, populate the source environment name and create a separate record for each Logical Unit and source_env_name combination. Otherwise, leave the source environment empty.

Click here for more information on how to implement a Broadway flow to get the entities (populated in external_table_flow field of MigrateList table).

Example 1:

  • lu_name= ORDER
  • source_env_name = ENV1
  • interface_name = TDM
  • ig_sql = Select lu_type2_eid from tdm_lu_type_relation_eid where lu_type_2 = ‘ORDER’ and source_env = 'ENV1';

Example 2:

  • lu_name= CUSTOMER
  • source_env_name is empty
  • interface_name = CRM_DB
  • ig_sql = Select customer_id from customer limit 1000;

Example 3:

  • lu_name= CUSTOMER
  • source_env_name is empty
  • external_table_flow = getEntityListFlow

MigrateListQueryFormats

Supports special syntax for extract tasks when creating the LU instance query based on the MigrateList table. Each LUI consists of a concatenation of the source environment, IID, version name and version datetime.

Click to read more about LUI structure for TDM implementation.

This table is required for databases that do not support the standard ‘||’ syntax for concatenated strings, e.g., sqlServer.

Populate 2 records for each database, one record with version_ind ‘true’ and another with version_ind ‘false’. 

Example 1:

  • interface_type = sqlserver
  • version_ind = true
  • query_format = CONCAT(<source_env_name>,'_',<entity_id>,'_',<task_name>,'_',<timestamp>)

Example 2:

  • interface_type = sqlserver
  • version_ind = false
  • query_format = CONCAT(<source_env_name>,'_',<entity_id>)

RefList

Define the list of available reference tables for TDM tasks.

Click to read more about Reference implementation.

Populate this table for each reference table. A separate record must be created for each reference table. Set the LU name on each record.

PostProcessList

Define the list of post-processes to run at the end of the task's execution. For example, a process that sends a mail to notify the user when the task's execution ends.

Each process is implemented as a Broadway flow.

Populate the list of Broadway flows and the LU of the Broadway flow. The LU can be empty if the post processes are defined under Shared Objects, whereby the TDM task execution process sets the LU Name to TDM when running Batch commands to carry out post execution processes. Redeploy the LUs populated in this table, the TDM LU, and the Web-Services.

ChildLink

Mapping parent and child IDs. 

Click for more information about TDM business entities and how to support a hierarchy when implementing the LUs.

A record must be added to this table for each parent-child relationship. The parent_lu field must be populated with the name of the parent LU and child_lu field must be populated with the name of the child LU.

Both SQLs populated in child_lu_eid_sql and child_lu_tar_eid_Sql fields must run on the parent LU and get the source and target child IDs for each parent ID.

Example:
Customer LU is the parent of the Orders LU.
ChildLink of the Customer LU must be populated as follows:

  • parent_lu = CRM
  • child_lu = Orders
  • child_lu_eid_sql = select order_id from subscriber
  • child_lu_tar_eid_sql = select order_id from tar_subscriber

The parameters: tables, subscriber and tar_subscriber, must all be defined in the CRM LU schema.

LuParams

Translation for the population of the LU_PARAMS table. 

The COLUMN_NAME is populated by the name of the parameter and the SQL is populated by the SQL query that gets the values for the defined parameter.

Click for more information about handling parameters.

Broadway Generic Flows and Templates

The Fabric TDM library includes a set of built-in generic Broadway flows, defined for easy adaptation of a generic TDM implementation for a specific data model.

Click for more information about Generic TDM Broadway Flows.

TDM LU

The TDM Logical Unit must be deployed to the Fabric project. It has the following tasks:

  • Saves information about executed TDM tasks. The TDM Portal provides execution statistics and reports based on the data in the TDM LU. The LUI of the TDM LU is a unique task_Execution_id generated by the TDM Portal for each executed task.
  • Task execution jobs are included in the TDM LU.
  • The TDM cleanup job that cleans the TDM DB is defined under the TDM LU.
  • From TDM 7.6 onwards, the TDM Portal code is included in the TDM LU: the TDM Portal code is kept under the web sub-folder in the TDM LU. Note that the web directory can only be viewed using the Fabric web studio. If you use the desktop, you can right-click the TDM LU > Open Folder and view the web folder in the windows File Explorer.
  • TDM 7.6 and onwards includes the TDM DB upgrade scripts and a flow.

Set TTL (Time To Live) on the TDM LUIs

TDM enables setting TTL (Time To Live) on the TDM LUIs. The default TTL period is 10 days. The TDM LUI's TTL depends on the following shared Globals (imported from the TDM Library):

  • TDM_LU_RETENTION_PERIOD_TYPE - by default, it is populated by 'Days'. This Global can have one of the following values: Minutes, Hours, Days, Weeks or Years.
  • TDM_LU_RETENTION_PERIOD_VALUE - by default, it is populated by 10. Populate this Global with either a zero or an empty value to avoid setting TTL on the TDM LUIs.

TDM Cleanup Process

Item 

Description 

Instructions 

TDMCleanUp

 Define the list of the TDM DB tables to be cleaned up by the TDM cleanup process. This table defines the Delete statement on each table and a cleanup indicator indicates whether the table should be cleaned up by the TDM cleanup process. Set the cleanup_ind field to FALSE to remove a table from the cleanup process. TDM tables can be added and Delete statements can be edited.

​

TDM Deploy Flow

The deploy.flow process runs the following activities upon the TDM LU deployment:

  • Deployment of the project's environments to Fabric.
  • Creating the k2masking keyspace in Cassandra, if it does not already exist.
  • TDM 7.6 added a creation of the TDM PostgreSQL DB: the TDM deploy flow Creates the TDM DB tables, sequences, views and functions.
  • Notes:
    • You must set the BUILD_TDMDB Global to true (default is false) and the POSTGRESQL_ADMIN interface to be active in order to create the TDM DB by the TDM deploy flow.
    • TDM 8.0 added the environment's deployment if the TDM_DEPLOY_ENVIRONMENTS Global is true. This Global is false, by default. The environment's file is taken from the project directory. If you wish to deploy the environments to Fabric, set the TDM_DEPLOY_ENVIRONMENTS to true.

TDM LU Deployment

Deploy the TDM LU to Fabric. From TDM 7.6 onwards, the deployment of the TDM LU deploys the TDM Portal as well into the TDM web applications.

Notes:

  • Deploy the TDM LU to the local debug Fabric server using the soft deploy option, or stop the TDM jobs on the local Fabric before deploying the TDM LU to a remote Fabric, thus avoiding a parallel execution of TDM jobs on the same TDM DB.
  • The apps.json file in the TDM LU overrides the list of web applications in Fabric. Open the file and edit it before the TDM LU deployment, if needed.

TDM_LIBRARY LU

The TDM_LIBRARY LU holds utilities that must be copied to the project's LUs. These utilities are described below.

It is recommended to duplicate the TDM_Library LU and use it as a template when creating a new LU in a TDM project.

Globals

LU level Globals

  • Populate the ROOT_TABLE_NAME Global using the main source table/s. You can populate several tables, separated by a comma.

    Examples:

    • CUSTOMER
    • CUSTOMER, ACCOUNT

  • Populate the ROOT_COLUMN_NAME Global using the entity ID's column. These Globals are needed for setting the IS_INSTANCE_ID column correctly in TDM_SEQ_MAPPING TDM DB table. Note that the number and order of root column names must be aligned with the number and order of the tables that are populated in ROOT_TABLE_NAME.

    Examples:

ROOT_TABLE_NAME ROOT_COLUMN_NAME
CUSTOMER CUSTOMER_ID
CUSTOMER, ACCOUNT CUSTOMER_ID, CUSTOMER_ID
CUSTOMER, ACCOUNT_DATA CUSTOMER_ID, ACC_CUST_ID

LU Tables

  • FABRIC_TDM_ROOT - the Root table of each LU. This table contains the following columns:

    • K2_TDM_EID - populated by the LU instance ID.
    • IID - populated by the entity ID without the concatenation of the source environment, version name and version datetime.
    • SOURCE_ENV - populated by the source environment name of the TDM task.
    • TASK_NAME - version name, populated with a task name for a Data Versioning task.
    • TIMESTAMP - version datetime, populated by a Data Versioning task.

    Example:

K2_TDM_EID

IID

SOURCE_ENV

TASK_NAME

TIMESTAMP

PROD_1

1

PROD

 

 

PROD_1_copyCust_20201105090000

1

PROD

copyCust

20201105090000

  • LU_PARAMS - parameters table. Must be added to each LU schema even when it is not required for defining parameters in the LU. The LU_PARAM table holds only the ENTITY_ID and SOURCE_ENVIRONMENT fields.

    Click for more information about TDM parameters handling.

  • TDM_LU_TYPE_RELATION_EID and TDM_LU_TYPE_REL_TAR_EID - TDM relationship tables that map the parent to child IDs. Note that these tables are also created in the TDM DB.

    Click for more information about TDM Hierarchy implementation.

TDM_Reference LU

TDM 7.6 onwards stores the extracted Reference tables in a new LU - TDM_Reference - instead of storing them in Cassandra. Each Reference table is stored as a separate LUI. For more information see Reference Implementation.

Previous

Fabric TDM Library

The TDM Library has all the utilities required for implementing a TDM project and for running TDM execution processes. It holds the following:

The TDM Library must be imported to the Fabric project created for TDM.

TDM Library - Shared Objects

TDM Web Services

Import and deploy all TDM Web Services (APIs) to the Fabric project. These Web Services are invoked by the TDM Portal application and they comprise the back-end layer of the TDM Portal application.

As the TDM categories contain the product's Web Services, it is recommended to add the project's Web Services into separate categories in order to simplify the TDM version upgrading.

Generic TDM Interfaces

Import and deploy the following interfaces into the project's Shared Objects:

  • DB_CASSANDRA - this is the connection to the Cassandra DB. This interface is used by TDM utilities. Edit the IP address according to the environment.

  • CASSANDRA_LD - a Cassandra Loader interface. This interface is used by the Reference upgrade script (upgrade to TDM 7.5.1).

  • POSTGRESQL_ADMIN - this is the admin connection to the TDM PosgreSQL DB. This interface is used by the TDMDB flow in the TDM LU to create the TDM DB in the PostgreSQL DB.

  • TDM - this is the connection to the TDM PosgreSQL DB. Edit the IP address according to the environment.

    Note that if you work on a PostgreSQL with an SSL connection, you must edit the custom connection string of the POSTGRESQL_ADMIN and the TDM interfaces as follows:

    • jdbc:postgresql://[ip address]:5438/TDMDB?stringtype=unspecified&ssl=true&sslmode=verify-ca&sslrootcert=[full path of the .crt file]
    • Example:
      • jdbc:postgresql://localhost:5438/TDMDB?stringtype=unspecified&ssl=true&sslmode=verify-ca&sslrootcert=C:\k2view\pgSSL\cert\k2v_CA.crt

  • FabricRedis - this is the Redis interface that connects to the environment's Redis storage. The Redis interface can be used for the sequence implementation. Edit the IP address and populate it with the IP address of the TDM server. Note that from Fabric 7.1 onwards, the sequence Actors can get the next sequence value from a newly created DB sequence in the sequence interface (the sequence interface can be the TDM DB). The sequence is created by the Actor, if it doesn't yet exist. It is therefore recommended to get the next value from a DB sequence instead of using the Redis.

    For more information, view the Sequence Implementation Guide.

  • TDM_APIDOC_JSON - this is a local file system interface, used for generating the JSON file of the TDM APIDOC if the APIDOC needs to be updated to include project custom APIs. Click here for more information about updating the TDM APIDOC.

    It is important to set the TDM_APIDOC_JSON interface as disabled in the Environments in order to prevent errors when running the test connection on the task's environment (the Fabric server has a different IP address than the local Windows machine and cannot connect to the local machine's directory).

Shared Globals

Import the list of shared global variables required for executing TDM in your project.

Shared Functions

TDM shared functions are saved in the TDM Logic file.

Import the TDM shared functions to your project. Note that since the TDM category contains the product's functions, it is recommended to add the project's shared functions to a separate category (Logic file) in order to simplify the TDM version upgrading.

TDM Library - MTables

TDM 8.1 replaces the previous TDM translation with MTables to support a development of the TDM on both Fabric Studios: Desktop-Studio and Web-Studio.

The following MTables have been added to the References in the TDM library. Note that you must deploy the Reference to Fabric after updating the MTables:

Item 

Description 

Instructions 

MigrateList

Define the query and interface name, or the Broadway flow to generate the entity list when running the extract task on all entities of each LU; one record per LU.

Populate this table for each Logical Unit. A separate record must be created for each Logical Unit in the Fabric project apart from TDM, TDM_LIBRARY and the dummy LU of the post-execution processes.  

If there is a need to define a query per source environment, populate the source environment name and create a separate record for each Logical Unit and source_env_name combination. Otherwise, leave the source environment empty.

Click here for more information on how to implement a Broadway flow to get the entities (populated in external_table_flow field of MigrateList table).

Example 1:

  • lu_name= ORDER
  • source_env_name = ENV1
  • interface_name = TDM
  • ig_sql = Select lu_type2_eid from tdm_lu_type_relation_eid where lu_type_2 = ‘ORDER’ and source_env = 'ENV1';

Example 2:

  • lu_name= CUSTOMER
  • source_env_name is empty
  • interface_name = CRM_DB
  • ig_sql = Select customer_id from customer limit 1000;

Example 3:

  • lu_name= CUSTOMER
  • source_env_name is empty
  • external_table_flow = getEntityListFlow

MigrateListQueryFormats

Supports special syntax for extract tasks when creating the LU instance query based on the MigrateList table. Each LUI consists of a concatenation of the source environment, IID, version name and version datetime.

Click to read more about LUI structure for TDM implementation.

This table is required for databases that do not support the standard ‘||’ syntax for concatenated strings, e.g., sqlServer.

Populate 2 records for each database, one record with version_ind ‘true’ and another with version_ind ‘false’. 

Example 1:

  • interface_type = sqlserver
  • version_ind = true
  • query_format = CONCAT(<source_env_name>,'_',<entity_id>,'_',<task_name>,'_',<timestamp>)

Example 2:

  • interface_type = sqlserver
  • version_ind = false
  • query_format = CONCAT(<source_env_name>,'_',<entity_id>)

RefList

Define the list of available reference tables for TDM tasks.

Click to read more about Reference implementation.

Populate this table for each reference table. A separate record must be created for each reference table. Set the LU name on each record.

PostProcessList

Define the list of post-processes to run at the end of the task's execution. For example, a process that sends a mail to notify the user when the task's execution ends.

Each process is implemented as a Broadway flow.

Populate the list of Broadway flows and the LU of the Broadway flow. The LU can be empty if the post processes are defined under Shared Objects, whereby the TDM task execution process sets the LU Name to TDM when running Batch commands to carry out post execution processes. Redeploy the LUs populated in this table, the TDM LU, and the Web-Services.

ChildLink

Mapping parent and child IDs. 

Click for more information about TDM business entities and how to support a hierarchy when implementing the LUs.

A record must be added to this table for each parent-child relationship. The parent_lu field must be populated with the name of the parent LU and child_lu field must be populated with the name of the child LU.

Both SQLs populated in child_lu_eid_sql and child_lu_tar_eid_Sql fields must run on the parent LU and get the source and target child IDs for each parent ID.

Example:
Customer LU is the parent of the Orders LU.
ChildLink of the Customer LU must be populated as follows:

  • parent_lu = CRM
  • child_lu = Orders
  • child_lu_eid_sql = select order_id from subscriber
  • child_lu_tar_eid_sql = select order_id from tar_subscriber

The parameters: tables, subscriber and tar_subscriber, must all be defined in the CRM LU schema.

LuParams

Translation for the population of the LU_PARAMS table. 

The COLUMN_NAME is populated by the name of the parameter and the SQL is populated by the SQL query that gets the values for the defined parameter.

Click for more information about handling parameters.

Broadway Generic Flows and Templates

The Fabric TDM library includes a set of built-in generic Broadway flows, defined for easy adaptation of a generic TDM implementation for a specific data model.

Click for more information about Generic TDM Broadway Flows.

TDM LU

The TDM Logical Unit must be deployed to the Fabric project. It has the following tasks:

  • Saves information about executed TDM tasks. The TDM Portal provides execution statistics and reports based on the data in the TDM LU. The LUI of the TDM LU is a unique task_Execution_id generated by the TDM Portal for each executed task.
  • Task execution jobs are included in the TDM LU.
  • The TDM cleanup job that cleans the TDM DB is defined under the TDM LU.
  • From TDM 7.6 onwards, the TDM Portal code is included in the TDM LU: the TDM Portal code is kept under the web sub-folder in the TDM LU. Note that the web directory can only be viewed using the Fabric web studio. If you use the desktop, you can right-click the TDM LU > Open Folder and view the web folder in the windows File Explorer.
  • TDM 7.6 and onwards includes the TDM DB upgrade scripts and a flow.

Set TTL (Time To Live) on the TDM LUIs

TDM enables setting TTL (Time To Live) on the TDM LUIs. The default TTL period is 10 days. The TDM LUI's TTL depends on the following shared Globals (imported from the TDM Library):

  • TDM_LU_RETENTION_PERIOD_TYPE - by default, it is populated by 'Days'. This Global can have one of the following values: Minutes, Hours, Days, Weeks or Years.
  • TDM_LU_RETENTION_PERIOD_VALUE - by default, it is populated by 10. Populate this Global with either a zero or an empty value to avoid setting TTL on the TDM LUIs.

TDM Cleanup Process

Item 

Description 

Instructions 

TDMCleanUp

 Define the list of the TDM DB tables to be cleaned up by the TDM cleanup process. This table defines the Delete statement on each table and a cleanup indicator indicates whether the table should be cleaned up by the TDM cleanup process. Set the cleanup_ind field to FALSE to remove a table from the cleanup process. TDM tables can be added and Delete statements can be edited.

​

TDM Deploy Flow

The deploy.flow process runs the following activities upon the TDM LU deployment:

  • Deployment of the project's environments to Fabric.
  • Creating the k2masking keyspace in Cassandra, if it does not already exist.
  • TDM 7.6 added a creation of the TDM PostgreSQL DB: the TDM deploy flow Creates the TDM DB tables, sequences, views and functions.
  • Notes:
    • You must set the BUILD_TDMDB Global to true (default is false) and the POSTGRESQL_ADMIN interface to be active in order to create the TDM DB by the TDM deploy flow.
    • TDM 8.0 added the environment's deployment if the TDM_DEPLOY_ENVIRONMENTS Global is true. This Global is false, by default. The environment's file is taken from the project directory. If you wish to deploy the environments to Fabric, set the TDM_DEPLOY_ENVIRONMENTS to true.

TDM LU Deployment

Deploy the TDM LU to Fabric. From TDM 7.6 onwards, the deployment of the TDM LU deploys the TDM Portal as well into the TDM web applications.

Notes:

  • Deploy the TDM LU to the local debug Fabric server using the soft deploy option, or stop the TDM jobs on the local Fabric before deploying the TDM LU to a remote Fabric, thus avoiding a parallel execution of TDM jobs on the same TDM DB.
  • The apps.json file in the TDM LU overrides the list of web applications in Fabric. Open the file and edit it before the TDM LU deployment, if needed.

TDM_LIBRARY LU

The TDM_LIBRARY LU holds utilities that must be copied to the project's LUs. These utilities are described below.

It is recommended to duplicate the TDM_Library LU and use it as a template when creating a new LU in a TDM project.

Globals

LU level Globals

  • Populate the ROOT_TABLE_NAME Global using the main source table/s. You can populate several tables, separated by a comma.

    Examples:

    • CUSTOMER
    • CUSTOMER, ACCOUNT

  • Populate the ROOT_COLUMN_NAME Global using the entity ID's column. These Globals are needed for setting the IS_INSTANCE_ID column correctly in TDM_SEQ_MAPPING TDM DB table. Note that the number and order of root column names must be aligned with the number and order of the tables that are populated in ROOT_TABLE_NAME.

    Examples:

ROOT_TABLE_NAME ROOT_COLUMN_NAME
CUSTOMER CUSTOMER_ID
CUSTOMER, ACCOUNT CUSTOMER_ID, CUSTOMER_ID
CUSTOMER, ACCOUNT_DATA CUSTOMER_ID, ACC_CUST_ID

LU Tables

  • FABRIC_TDM_ROOT - the Root table of each LU. This table contains the following columns:

    • K2_TDM_EID - populated by the LU instance ID.
    • IID - populated by the entity ID without the concatenation of the source environment, version name and version datetime.
    • SOURCE_ENV - populated by the source environment name of the TDM task.
    • TASK_NAME - version name, populated with a task name for a Data Versioning task.
    • TIMESTAMP - version datetime, populated by a Data Versioning task.

    Example:

K2_TDM_EID

IID

SOURCE_ENV

TASK_NAME

TIMESTAMP

PROD_1

1

PROD

 

 

PROD_1_copyCust_20201105090000

1

PROD

copyCust

20201105090000

  • LU_PARAMS - parameters table. Must be added to each LU schema even when it is not required for defining parameters in the LU. The LU_PARAM table holds only the ENTITY_ID and SOURCE_ENVIRONMENT fields.

    Click for more information about TDM parameters handling.

  • TDM_LU_TYPE_RELATION_EID and TDM_LU_TYPE_REL_TAR_EID - TDM relationship tables that map the parent to child IDs. Note that these tables are also created in the TDM DB.

    Click for more information about TDM Hierarchy implementation.

TDM_Reference LU

TDM 7.6 onwards stores the extracted Reference tables in a new LU - TDM_Reference - instead of storing them in Cassandra. Each Reference table is stored as a separate LUI. For more information see Reference Implementation.

Previous

© Copyright 2024 K2VIEW