Access modules are dynamically attached software components of the Teradata standalone load and unload utilities. Some access modules are usable with Teradata PT and provide the input/output interface between operators and various types of external data storage devices. Any operator that uses access modules can interface with all available access modules.
Be careful to specify the Teradata Parallel Transporter version of any access module you use.
The following access modules can be used as part of a job to move data from an external data source to Teradata Database.
|Teradata Access Module for JMS||Provides access to any JMS-enabled messaging system. Reads JMS transaction messages and sends the data to the DataConnector producer operator for transfer to a Teradata Database.
Teradata Access Module for JMS caches the message throughput data stream in a fallback data file that supports checkpoint and restart functions.
|Teradata Access Module for Named Pipes||Provides access to data from a named pipe and sends it to a DataConnector producer operator.
The Teradata Access Module for Named Pipes also caches the data input from a pipe in a fallback data file that supports checkpoint and restart functions.
This access module is not available on z/OS platforms.
|Teradata Access Module for OLE DB||Provides read access to data from an OLE DB provider application, such as Connix or SQL Server, which can access flat files, spreadsheets, and databases in an external data store.|
|Teradata Access Module for WebSphere MQ||Provides access to transactional data from IBM WebSphereMQ.
The Teradata Access Module for WebSphere MQ also caches the output message stream in a fallback data file that supports checkpoint and restart functions.