System (Product) Windows

A TDM system (product) represents a system or application installed in a source or target environment. For example, the UAT1 environment contains CRM and Billing systems. Each system can have multiple data sources (interfaces). For example, the Billing system has the Billing and Usage DBs.

A TDM system has the following components:

  • Name, a logical name that identifies the system. For example, CRM.

  • Versions, the system's versions as defined in testing environments. For example, Production and Development.

  • Logical Units (LUs).

  • Related Interfaces: This optional setting was introduced in TDM 9.5. You can attach zero, one, or multiple Interfaces to a System. Attached interfaces inherit the default affinity and/or the maximum number of workers from the task’s environment when creating table-level tasks.

BE and LU System Relationship

Each BE and LU combination can be attached to one system only. However, a system can have LUs belonging to different BEs.

The following example displays the relationship between a BE, LU and a system:

be-prod-lu

Systems List Window

The Systems window displays a list of all systems defined in the TDM. Only Admin users can create, edit, or delete a system. Other users can open systems for view only purposes.

  • To create a new system, click Add System.
  • To open a selected system, click its Name.
  • To delete a system, click delete in the right corner of the System window.

System Window

The System window displays information about a selected system. It has two main sections:

  • General Information.
  • Logical Units.

General Information

The General Information section has the following settings:

  • Name: populated by the system name.

  • Vendor and Description: optional settings.

  • Versions: system's versions which enable the TDM implementation to support multiple versions of the system.

    • Each system version may have a different data source structure. For example, a development environment may have new tables and fields that are not in the production environment.
    • At least one version must be set for a system. Multiple system versions can also be set.
    • The relevant system version must be selected when adding a system to an Environment.

​ To add a version to a system, click delete next to the Versions setting and enter the version's value, which is the logical identifier of the system's version. For example: 1, 1.5, dev, or prod. The values must be aligned with the TDM Fabric implementation.

Click for more information about supporting multiple system versions via TDM.

Starting with TDM 9.5, you can configure affinity and the maximum number of workers at both the environment level and the task level. These settings provide greater control over resource allocation and workload distribution, and apply to both:

  • Entity-based tasks
  • Table-level tasks

Default Configuration

Default values for affinity and maximum number of workers are defined at the environment system level.

Interface Inheritance

When you attach interfaces to a system, the system inherits the default affinity and maximum number of workers from the associated table-level task environments.

Adding Interfaces to a System

To add or remove interfaces:

  • Click the interface field to open the dropdown list
  • Select one or more interfaces
  • Repeat to add additional interfaces
  • To remove an interface, click the X next to it

Logical Units

How Do I Add an LU to a System?

Click Add Logical Unit to open the dialog box:

Add lu to System

  • The Business Entities setting displays a list of BEs with available LUs that are not attached to the system.

  • The Logical Unit Name setting displays a list of available LUs that are not attached to the system and that belong to the selected BE.

How Do I Delete an LU from a System?

Click be_delete to delete the selected LU from the system.

Click for more information about product related TDM DB tables.

Previous

System (Product) Windows

A TDM system (product) represents a system or application installed in a source or target environment. For example, the UAT1 environment contains CRM and Billing systems. Each system can have multiple data sources (interfaces). For example, the Billing system has the Billing and Usage DBs.

A TDM system has the following components:

  • Name, a logical name that identifies the system. For example, CRM.

  • Versions, the system's versions as defined in testing environments. For example, Production and Development.

  • Logical Units (LUs).

  • Related Interfaces: This optional setting was introduced in TDM 9.5. You can attach zero, one, or multiple Interfaces to a System. Attached interfaces inherit the default affinity and/or the maximum number of workers from the task’s environment when creating table-level tasks.

BE and LU System Relationship

Each BE and LU combination can be attached to one system only. However, a system can have LUs belonging to different BEs.

The following example displays the relationship between a BE, LU and a system:

be-prod-lu

Systems List Window

The Systems window displays a list of all systems defined in the TDM. Only Admin users can create, edit, or delete a system. Other users can open systems for view only purposes.

  • To create a new system, click Add System.
  • To open a selected system, click its Name.
  • To delete a system, click delete in the right corner of the System window.

System Window

The System window displays information about a selected system. It has two main sections:

  • General Information.
  • Logical Units.

General Information

The General Information section has the following settings:

  • Name: populated by the system name.

  • Vendor and Description: optional settings.

  • Versions: system's versions which enable the TDM implementation to support multiple versions of the system.

    • Each system version may have a different data source structure. For example, a development environment may have new tables and fields that are not in the production environment.
    • At least one version must be set for a system. Multiple system versions can also be set.
    • The relevant system version must be selected when adding a system to an Environment.

​ To add a version to a system, click delete next to the Versions setting and enter the version's value, which is the logical identifier of the system's version. For example: 1, 1.5, dev, or prod. The values must be aligned with the TDM Fabric implementation.

Click for more information about supporting multiple system versions via TDM.

Starting with TDM 9.5, you can configure affinity and the maximum number of workers at both the environment level and the task level. These settings provide greater control over resource allocation and workload distribution, and apply to both:

  • Entity-based tasks
  • Table-level tasks

Default Configuration

Default values for affinity and maximum number of workers are defined at the environment system level.

Interface Inheritance

When you attach interfaces to a system, the system inherits the default affinity and maximum number of workers from the associated table-level task environments.

Adding Interfaces to a System

To add or remove interfaces:

  • Click the interface field to open the dropdown list
  • Select one or more interfaces
  • Repeat to add additional interfaces
  • To remove an interface, click the X next to it

Logical Units

How Do I Add an LU to a System?

Click Add Logical Unit to open the dialog box:

Add lu to System

  • The Business Entities setting displays a list of BEs with available LUs that are not attached to the system.

  • The Logical Unit Name setting displays a list of available LUs that are not attached to the system and that belong to the selected BE.

How Do I Delete an LU from a System?

Click be_delete to delete the selected LU from the system.

Click for more information about product related TDM DB tables.

Previous