TDM Implementation Flow

A TDM implementation involves several steps. The following illustration displays the main ones:

A TDM implementation begins with a Fabric Implementation, followed by Fabric Credentials setup, and finally setting TDM definitions in the TDM Portal.

Notes:

The TDM Portal retrieves and adds LUs to the BE, but can only do so with LUs that have already been deployed. Therefore, you must complete the implementation in Fabric and deploy the LUs to Fabric before setting TDM definitions via the TDM Portal.
It is recommended to migrate a large sub-set of entities of each LU into Fabric to populate the TDM relation (tdm_lu_type_relation_eid) and the LU Parameters TDM table before the creation and execution of TDM load tasks. This will enable the user to create load tasks based on selected parameters.

TDM Implementation Flow

A TDM implementation involves several steps. The following illustration displays the main ones:

A TDM implementation begins with a Fabric Implementation, followed by Fabric Credentials setup, and finally setting TDM definitions in the TDM Portal.

Notes:

The TDM Portal retrieves and adds LUs to the BE, but can only do so with LUs that have already been deployed. Therefore, you must complete the implementation in Fabric and deploy the LUs to Fabric before setting TDM definitions via the TDM Portal.
It is recommended to migrate a large sub-set of entities of each LU into Fabric to populate the TDM relation (tdm_lu_type_relation_eid) and the LU Parameters TDM table before the creation and execution of TDM load tasks. This will enable the user to create load tasks based on selected parameters.