MultiLoad EcoSystem Manager Integration - MultiLoad

Teradata® MultiLoad Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
MultiLoad
Release Number
20.00
Published
October 2023
Language
English (United States)
Last Update
2024-03-18
dita:mapPath
lji1691576359330.ditamap
dita:ditavalPath
kju1619195148891.ditaval
dita:id
sga1478609868891
Product Category
Teradata Tools and Utilities

Teradata EcoSystem Manager (previously Teradata Multi-System Manager, TMSM) monitors and analyzes the relationships of the applications, servers, jobs, tables, and software daemons that comprise it. The centralized interface helps you troubleshoot and determine the impact of any failure in your ecosystem. The expected users of this facility are administrators of the Enterprise Data Warehouse (EDW) such as database administrators, ETL maintenance staff, systems administrators, or anyone who needs to monitor and control processes that include, but are not limited to, Teradata Load and Unload Utilities, Teradata SQL, ETL tools, and Vantage.

To integrate with EcoSystem Manager, MultiLoad has been enhanced to collect operational metadata and event data, obtain the Unit of Work ID (UOW ID) from EcoSystem Manager for a job, and send such data to EcoSystem Manager for monitoring purposes using the “send event” interface as described in the EcoSystem Manager Event System API Reference. By default, a MultiLoad job will send events to EcoSystemManager as long as EcoSystem Manager is active. If EcoSystem Manager is not active, the job will continue to run, except that no events will be sent to EcoSystem Manager.

Simple ETL process monitoring requires the tracking of the “start” and “end” of the process, which can include multiple “steps”, each of which represents an activity or event of the process to be monitored. In terms of MultiLoad, a load job can be regarded as such a process.

MultiLoad follows the flow required by EcoSystem Manager:

  1. Obtain a system-generated UOW ID from EcoSystem Manager for a MultiLoad job
  2. Send a “start” event to EcoSystem Manager along with the UOW ID
  3. Optionally send one or more “step” events to EcoSystem Manager along with the UOW ID
  4. Send an “end” event to EcoSystem Manager along with the UOW ID

Below are examples of how MultiLoad job sends event messages to EcoSystem Manager in order for the job to be monitored:

Start Event -- "Connecting sessions" message which contains a MultiLoad job ID, a TDPID.
Step Event --  "Task n: Acquisition begins" message
Step Event --  "Task n: Checkpoint completes" message
Step Event --  "Task n: Acquisition completes" message

For MultiLoad Import Task:

Step Event --  "Task n: Application completes" message which contains the number of rows inserted into each of the target tables (1 message per table)

Step Event --  "Task n: Application completes" message which contains the number of rows that were updated against each of the target tables (1 message per table)

Step Event --  "Task n: Application completes" message which contains the number of rows that were deleted from each of the target tables (1 message per table) 
For MultiLoad Delete Task:
Step Event -- "Task n: Application completes" message which contains the
number of rows that were deleted from each of the target tables (1
message per table)

End Event -- "Job terminating" message

For detailed information on setting up the EcoSystem Manager environment, refer to the Teradata® Ecosystem Manager Installation, Configuration, and Upgrade Guide for Customers (B035-3203).