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
Access modules provide Teradata PT with transparent, uniform access to various data
sources. Access modules isolate Teradata PT from the following:
Device dependencies, for example, disk versus tape (only on mainframe) (embedded into
the Teradata standalone utilities today)
Data source/target location, for example, local versus remote
Data store specifics, for example, sequential file versus indexed file versus relational
Access modules can be used with the DataConnector operator to read from different
types of external data storage devices.
The following access modules are supported. These access modules support only reading
(importing) of data, not writing:
Named Pipes Access Module for Teradata PT allows you to use Teradata PT to load data into the Teradata Database from a UNIX system named pipe. A pipe is a type of data buffer that certain operating systems
allow applications to use for the storage of data.
WebSphere MQ Access Module for Teradata PT allows you to use 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 for Teradata PT allows you to use Teradata PT to load data from a JMS-enabled messaging system using JMS message queuing middleware
Custom Access Modules. You can also create custom access modules to use with the DataConnector operator
for access to specific systems.
For more information about creating and using custom access modules, see the Teradata Tools and Utilities Access Module Programmer Guide.