Sending Operational Metadata to TMSM
Teradata Multi-System Manager (TMSM) is the monitoring and control facility for a variety of Dual Active Solutions. The users of this facility include Enterprise Data Warehouse (EDW) users or anyone who needs to monitor and control processes including, but not limited to, Teradata Load and Unload Utilities, Teradata SQL, ETL tools, and Teradata Database.
To integrate with TMSM, Teradata PT has been enhanced to collect operational metadata and event data from operators. To do this, Teradata PT obtains the Unit of Work ID (UOW ID) from TMSM for a job, and sends it to TMSM using the send event interface. By default, a Teradata PT job sends events to TMSM as long as TMSM is active. If TMSM is not active, the job runs without sending events to TMSM. For more information about the send event interface, see the TMSM Event System API Reference.
Teradata PT allows the following Teradata PT operators, which can be regarded as resource types from the TMSM point of view, to be monitored:
|
TMSM Predefined Resource Types |
Teradata PT Operators |
|
TMSM_RESOURCETYPE_TPT_EXPORT |
Export Operator |
|
TMSM_RESOURCETYPE_TPT_UPDATE |
Update Operator |
|
TMSM_RESOURCETYPE_TPT_LOAD |
Load Operator |
|
TMSM_RESOURCETYPE_TPT_STREAM |
Stream Operator |
|
TMSM_RESOURCETYPE_TPT_INSERT |
Schema Mapping Operator |
Simple ETL process monitoring tracks a process from the start to the end. A process can include multiple steps, each of which represents an activity or event to be monitored. For example, a Teradata PT load job can be regarded as such a process.
TMSM requires the following Teradata PT flow:
1 Obtain a system-generated UOW ID from TMSM for a Teradata PT job.
2 Send a “start” event to TMSM along with the UOW ID.
3 (Option) Send one or more “step” events to TMSM along with the UOW ID.
4 Send an “end” event to TMSM along with the UOW ID.