15.10 - Exporting from an ODBC-Compliant Data Source (Using Teradata PT) - Access Module

Teradata Tools and Utilities Access Module Reference

prodname
Access Module
vrm_release
15.10
category
Programming Reference
featnum
B035-2425-035K

Exporting from an ODBC‑Compliant Data Source (Using Teradata PT)

The Teradata Access Module for JMS can also be transparently used with any Teradata Parallel Transporter (PT) producer operator, such as the ODBC Operator, through the Teradata PT DataConnector Operator. Figure 9 on page 102 is an overview of the data flow between any ODBC‑compliant data source and a JMS client application using the Teradata Access Module for JMS. In general, the process is as follows:

  • Teradata PT ODBC Operator connects to an ODBC‑compliant data source, for example, Oracle, SQL Server, or DB2.
  • The operator reads data close to the sources (from the same machine where Teradata PT is running, as opposed to across a network).
  • The operator feeds the data (via data stream) to Teradata PT Data Connector.
  • Teradata PT Data Connector transfers the database records to the Teradata Access Module for JMS.
  • The Teradata Access Module for JMS uses the JMS connection calls to access configured JMS administered objects, and connects to the JMS server.
  • The Teradata Access Module for JMS composes database records into messages (the export utility defines the database record format), and sends the messages to a JMS server.
  • The JMS server puts the messages on a specified queue or a certain destination, called a topic.
  • The JMS server stores the messages until any other JMS‑compliant application reads and removes them.
  • Figure 9: Exporting from ODBC‑Compliant Data Sources