Figure 6 shows how the Teradata WebSphere MQ Access Module imports data to a Teradata Database through a client load utility, such as BTEQ, FastLoad, MultiLoad, or TPump. Although the figure shows the data producer, the queue manager, and the load utility on separate systems, these entities can be on the same system. If you are using the Teradata PT version of the WebSphere MQ Access Module, the term DataConnector in this figure and throughout this chapter refers to the Teradata PT DataConnector operator.Figure 6: Importing Data through WebSphere MQ with Load and Unload Utilities
The flow of data between a data producer, such as an eBusiness application, and a table in Teradata begins as the data producer does the following:
1 Establishes a network connection with a WebSphere MQ queue manager using standard WebSphere MQ interfaces
2 Composes database records into messages (the load utility defines the database records’ format)
3 Sends the messages to a message queue under control of the queue manager
At this point, the queue manager stores the incoming messages until the load utility reads and removes them through the following sequence of events:
1 The WebSphere MQ Access Module establishes a connection to the queue manager.
2 The WebSphere MQ Access Module reads messages from the message queue when directed to do so by the Data Connector.
3 The WebSphere MQ Access Module delivers the data to the Data Connector.
4 The Data Connector delivers the data to the load utility.
5 The load utility loads the data into a table within Teradata.
Note: If the load utility is on the same system as the queue manager, the queue manager can be configured to trigger the load utility.