Saturday, 21 September 2013

1.4 Types of TPT operators, INMOD and OUTMOD , Access Modules

Operator Types in TPT:

Following are the 4 types of Operators in Teradata  Parallel Transporter.

Operator Type
Description with Type definitions.(Type definitions are required when writing the TPT job)
Producer Operator
Read from Source and puts data on Data Stream.


Following are producer Operators:

  • Export operator (Type Definition:  TYPE EXPORT)
     
  • SQL Selector operator(Type Definition: TYPE SELECTOR)
     
  • DataConnector operator, when reading data:  (Type Definition: TYPE DATACONNECTOR PRODUCER)
Directly from a flat file
Through an access module that reads data from an external source
 
  • FastLoad INMOD Adapter operator (Type Definition: TYPE FASTLOAD INMOD)
     
  • MultiLoad INMOD Adapter operator (Type Definition: TYPE MULTILOAD INMOD)
     
  • ODBC operator (Type Definition: TYPE ODBC)

Consumer Operator
Read from Data Stream and put it Targets.

  • Load operator (Type Definition: TYPE LOAD)

  • Update operator (Type Definition: TYPE UPDATE)

  • Stream operator (Type Definition: TYPE STREAM)

  • SQL Inserter operator (Type Definition: TYPE INSERTER)

  • DataConnector operator, when interfacing an access module that writes data to an external - destination (Type Definition: TYPE DATACONNECTOR CONSUMER)

  • FastExport OUTMOD Adapter operator (Type Definition: TYPE FASTEXPORT OUTMOD)

Filter Operator
Read Data from Data Streams, perform Data .

Although Teradata PT does not include any specific filter operators, the following filter
operations can be accomplished using Teradata PT:
  • Teradata PT job scripts can invoke user-written filter operators that are coded in the C or C++ programming languages. For more information about creating customized operators, see Teradata Parallel Transporter Operator Programmer Guide.

  • Teradata PT includes the MultiLoad INMOD Adapter filter-type operator.

  • Teradata PT supports several filtering capabilities, specifically the WHERE clause and CASE DML expressions in APPLY statements. These can handle most filtering operations.


Standalone Operators
Processing that does not involve receiving data from or sending data to the data stream.


 
Standalone operators can perform the following functions:
  • Execute DDL and other self-contained SQL statements
  • Execute host operating system commands
  • Execute a DELETE task on the Teradata Database

Teradata PT includes the following standalone-type operators:
 
  • OS Command operator (Type Definition: TYPE OS COMMAND)
     
  • DDL operator (Type Definition: TYPE DDL)
     
  • The Update operator, when it is executing the Delete Task and if no data is required (Type Definition: TYPE UPDATE deletetaskatrtribute)

Custom Operators: Teradata PT allows us to create custom operators using Teradata API.
They should follow requirements of Teradata PT operator instance. They must be written in C or C++














Explain INMOD and OUTMOD Adapter Operators:

  1. INMOD Adapter Operators

An INMOD routine cannot send data directly to Consumer Operator.
The INMOD routine and the INMOD adapter operator can together act as a produce operator to pass data to the Load or Update operators.

Input modification (INMOD) adaptor operators are user-written INMOD routines that can preprocess data before it is sent to the Load or Update operator and then to the Teradata Database.


 2.   OUTMOD Adaptor Operators

An OUTMOD routine cannot be directly invoked by the Teradata PT Export operator.
Rather, OUTMOD routines are invoked by the Teradata PT FastExport OUTMOD adapter operator, which acts as a consumer operator to read data from the Export operator.

Output modification (OUTMOD) adaptor operators are user-written routines that process extracted data prior to delivering the data to its final destination.











Explain Access Modules:

Access modules are software modules that encapsulate the details of access to various data stores, for example, CD-R, CD-RW, tape (via DataConnector or FastLoad OUTMOD Adapter operators), subsystems (such as Teradata Database servers, IBM’s WebSphere MQ)

Access modules provide Teradata PT with transparent, uniform access to various data sources.

Access modules can be used with the DataConnector operator to read from different types of external data storage devices.

These access modules support only reading (importing) of data, not writing

Named Pipes Access Modules:
Allows use of Teradata PT to load data into the Teradata Database from a UNIX named pipe.
WebSphere MQ Access Module
Allows use of Teradata PT to load data from a message queue using IBM’s WebSphere MQ (formerly known as MQ Series) message queuing middleware.
JMS Access Module
Allows use of  Teradata PT to load data from a JMS-enabled messaging system using JMS message queuing middleware.
Custom Access Modules
We can create custom access modules to use with the DataConnector operator for access to specific systems.

1 comment: