Component Roles During Data Exports - Access Module
Teradata® Tools and Utilities Access Module Reference - 20.00
- Deployment
- VantageCloud
- VantageCore
- Edition
- Enterprise
- IntelliFlex
- Lake
- VMware
- Product
- Access Module
- Release Number
- 20.00
- Published
- October 2023
- ft:locale
- en-US
- ft:lastEdition
- 2024-05-14
- dita:mapPath
- cya1691484517272.ditamap
- dita:ditavalPath
- obe1474387269547.ditaval
- dita:id
- hjf1479308836950
- lifecycle
- latest
- Product Category
- Teradata Tools and Utilities
- For export jobs, the sender is the Teradata Access Module for JMS, which is responsible for the following:
- Formatting a data message that is defined by the Teradata export utility. The data message type can either be a simple text message (Type TextMessage) or a stream of bytes (Type ByteMessage).
- Performing a JNDI lookup to retrieve JMS-administered objects from the naming space.
- Establishing communication with the JMS provider.
- Placing a data message on a specified queue/topic.
- Sending a control message (zero-length message) to indicate the end of the message stream.
- For export jobs, the receiver can be the Teradata Access Module for JMS or any other JMS-enabled application. The receiver is responsible for the following tasks:
- Performing a JNDI lookup to retrieve JMS-administered objects from the naming space.
- Establishing communication with the JMS provider.
- Retrieving the data message from the queue/topic.
- Copying the data message to a fallback file for checkpoint and restart.
- Passing the data message to the Teradata load utility, which then processes and loads the data into a JMS-enabled application.
- Continuing to fetch data messages from the queue or topic until a control message (zero-length message) is received or a timeout that signals the end of the message stream is received.