A Business Entity (BE) represents the main entity of the data to be provisioned by TDM. A BE can have multiple LUs with either a flat or a hierarchical structure. For example, a Customer BE can have Customer Care, Billing, Ordering and Usage LUs. Each LU can be attached to multiple BEs.
The Business Entities window displays a list of all BEs defined in the TDM. Only Admin users can create, edit or delete a BE. Other users can open BEs for viewing purposes only.
The Business Entity window displays information about a selected BE. It has 3 main sections:
The following is an example of a Customer Business Entity window:
The General Information section consists of the BE Name and Description. The Name setting is mandatory. Note that each active BE should have a specified Name. An error is displayed when an attempt is made to create several BEs with the same name.
To use a BE in a TDM task, it must have one or more LUs assigned to it.
Do either:
Check All Logical Units to attach all LUs that are deployed to Fabric and that are not attached to the BE. The LUs are attached to the BE in a flat structure whereby the Parent LU is empty. When needed, the LUs can be edited to populate the Parent LU and the Data Center settings.
Check Select and select an LU from the Logical Unit drop-down list:
Click ADD LOGICAL UNITS to add the selected LUs to the BE.
Notes:
Click or to edit or delete the LU from the BE. Note that the LU is deleted from the BE in the TDM DB.
Click for more information about TDM DB tables that hold the BE and LU relationship.
These tabs enable adding pre and post execution processes. The pre-execution processes run at the beginning of the task's execution, before all the related LUs have been executed. The post-execution processes run at the end of the task's execution, after all the related LUs have been executed.
Examples:
The pre and post execution processes are Broadway flows defined in Fabric by the TDM implementor. The relationship between a pre or post execution process and a BE is many-to-many. That is, a BE can have several pre/post execution processes, and a pre/post execution process can be attached to multiple BEs. Note that a given flow can be attached as both - pre and post execution process - to a BE.
The task execution process executes the BATCH command on each pre and post execution process attached to the task. The execution order is set according to the execution order defined in the BE.
The pre and post execution processes are optional: a BE can be defined without any post-execution processes.
Note that the pre and post execution processes must be populated in the PostAndPreExecutionProcess MTable object to be displayed by the BE window.
Open the Pre Execution Processes or Post Execution Processes tabs and click Add Pre Execution Processes or Add Post Execution Processes to open a dialog box.
Click the Process Name and select a flow from the drop-down list that holds all pre/post execution processes deployed to Fabric.
Populate the Execution Order field with a numeric value to set the execution order. Processes with Execution Order 1 run first, followed by processes with Execution Order 2, etc. Note that an execution order can be set for several processes that are executed simultaneously.
Populate the Description field (optional).
Click ADD PRE/POST EXECUTION PROCESS to add the process to the BE.
Repeat steps 1-5 to add additional pre/post execution processes, if needed.
Click here for more information about the BE TDM DB tables and about the BE and the pre/post-execution processes relationship.
A Business Entity (BE) represents the main entity of the data to be provisioned by TDM. A BE can have multiple LUs with either a flat or a hierarchical structure. For example, a Customer BE can have Customer Care, Billing, Ordering and Usage LUs. Each LU can be attached to multiple BEs.
The Business Entities window displays a list of all BEs defined in the TDM. Only Admin users can create, edit or delete a BE. Other users can open BEs for viewing purposes only.
The Business Entity window displays information about a selected BE. It has 3 main sections:
The following is an example of a Customer Business Entity window:
The General Information section consists of the BE Name and Description. The Name setting is mandatory. Note that each active BE should have a specified Name. An error is displayed when an attempt is made to create several BEs with the same name.
To use a BE in a TDM task, it must have one or more LUs assigned to it.
Do either:
Check All Logical Units to attach all LUs that are deployed to Fabric and that are not attached to the BE. The LUs are attached to the BE in a flat structure whereby the Parent LU is empty. When needed, the LUs can be edited to populate the Parent LU and the Data Center settings.
Check Select and select an LU from the Logical Unit drop-down list:
Click ADD LOGICAL UNITS to add the selected LUs to the BE.
Notes:
Click or to edit or delete the LU from the BE. Note that the LU is deleted from the BE in the TDM DB.
Click for more information about TDM DB tables that hold the BE and LU relationship.
These tabs enable adding pre and post execution processes. The pre-execution processes run at the beginning of the task's execution, before all the related LUs have been executed. The post-execution processes run at the end of the task's execution, after all the related LUs have been executed.
Examples:
The pre and post execution processes are Broadway flows defined in Fabric by the TDM implementor. The relationship between a pre or post execution process and a BE is many-to-many. That is, a BE can have several pre/post execution processes, and a pre/post execution process can be attached to multiple BEs. Note that a given flow can be attached as both - pre and post execution process - to a BE.
The task execution process executes the BATCH command on each pre and post execution process attached to the task. The execution order is set according to the execution order defined in the BE.
The pre and post execution processes are optional: a BE can be defined without any post-execution processes.
Note that the pre and post execution processes must be populated in the PostAndPreExecutionProcess MTable object to be displayed by the BE window.
Open the Pre Execution Processes or Post Execution Processes tabs and click Add Pre Execution Processes or Add Post Execution Processes to open a dialog box.
Click the Process Name and select a flow from the drop-down list that holds all pre/post execution processes deployed to Fabric.
Populate the Execution Order field with a numeric value to set the execution order. Processes with Execution Order 1 run first, followed by processes with Execution Order 2, etc. Note that an execution order can be set for several processes that are executed simultaneously.
Populate the Description field (optional).
Click ADD PRE/POST EXECUTION PROCESS to add the process to the BE.
Repeat steps 1-5 to add additional pre/post execution processes, if needed.
Click here for more information about the BE TDM DB tables and about the BE and the pre/post-execution processes relationship.