TDM - Reference Implementation
TDM enables users to extract Reference tables from several source environments and to save them into the Cassandra DB. Additionally, it enables saving different versions of a Reference table and source environment into the Cassandra DB. Lastly, TDM enables the creation and execution of TDM load tasks to copy reference data from the Cassandra DB into the target environment.
Note: The TDM Reference solution is not based on Fabric Reference tables and the tables are saved in Cassandra.
A TDM implementation has the following steps:
Step 1 - Populate trnRefList Translation
The list of Reference tables available for TDM extract tasks is populated in the trnRefList translation object. Populate trnRefList with the list of available Reference tables for each LU. The following settings should be populated for each record:
- lu_name - populated by the LU name.
- ID - populated by a sequence.
- reference_table_name - populated by the Reference table in the source env.
- schema_name - populated by the source DB schema name that stores the Reference table.
- interface_name - the Reference table's source interface.
- target_ref_table_name - this is an optional parameter. It can be populated when the Reference table names are different in the source and target. If empty, the target table name will be taken from the reference_table_name field.
- target_schema_name - populated by the target DB Schema's name that stores the Reference table.
- target_interface_name - name of the Reference table's target interface.
Example:
Note: It is also possible to populate the list of target's PK fields in trnRefList. These fields can be later used to customized the load flow to run an Upsert on the target reference table.
Step 2 - Create and Execute TDM Extract Tasks
TDM extract tasks store the selected Reference data in the related Cassandra DB table.
Click for more information on how the TDM stores Reference tables in the Cassandra DB.
Step 3 - Create and Execute TDM Load Tasks
The TDM GUI enables the creation of TDM load tasks in order to copy Reference tables that have been successfully extracted into the Cassandra DB. The execution of a load task runs the TDMReferenceLoader Broadway flow to copy the task's reference tables to the target environment.
Click for more information about generic TDM Broadway flows.
TDM - Reference Implementation
TDM enables users to extract Reference tables from several source environments and to save them into the Cassandra DB. Additionally, it enables saving different versions of a Reference table and source environment into the Cassandra DB. Lastly, TDM enables the creation and execution of TDM load tasks to copy reference data from the Cassandra DB into the target environment.
Note: The TDM Reference solution is not based on Fabric Reference tables and the tables are saved in Cassandra.
A TDM implementation has the following steps:
Step 1 - Populate trnRefList Translation
The list of Reference tables available for TDM extract tasks is populated in the trnRefList translation object. Populate trnRefList with the list of available Reference tables for each LU. The following settings should be populated for each record:
- lu_name - populated by the LU name.
- ID - populated by a sequence.
- reference_table_name - populated by the Reference table in the source env.
- schema_name - populated by the source DB schema name that stores the Reference table.
- interface_name - the Reference table's source interface.
- target_ref_table_name - this is an optional parameter. It can be populated when the Reference table names are different in the source and target. If empty, the target table name will be taken from the reference_table_name field.
- target_schema_name - populated by the target DB Schema's name that stores the Reference table.
- target_interface_name - name of the Reference table's target interface.
Example:
Note: It is also possible to populate the list of target's PK fields in trnRefList. These fields can be later used to customized the load flow to run an Upsert on the target reference table.
Step 2 - Create and Execute TDM Extract Tasks
TDM extract tasks store the selected Reference data in the related Cassandra DB table.
Click for more information on how the TDM stores Reference tables in the Cassandra DB.
Step 3 - Create and Execute TDM Load Tasks
The TDM GUI enables the creation of TDM load tasks in order to copy Reference tables that have been successfully extracted into the Cassandra DB. The execution of a load task runs the TDMReferenceLoader Broadway flow to copy the task's reference tables to the target environment.
Click for more information about generic TDM Broadway flows.
