Interface with a JMS Provider
The Teradata Access Module for JMS uses Java Message Service (JMS) to access a JMS
provider. The JMS is a Java API that allows applications to create, send, receive,
and read data messages between software components.
Following are the main parts of the Teradata Access Module for JMS that interface
with JMS providers:
JNDI Naming Service – looks up naming and directory services by setting up initial context.
Queue or Topic Connection Factory – creates queue or topic connections with a JMS provider.
Queue or Topic Connection – creates queue or topic session objects.
Queue or Topic Session – creates queue receiver, topic subscriber, queue sender, or topic publisher objects.
Queue Receiver or Topic Subscriber – receives messages that are delivered to a queue or topic during a load job.
Queue Sender or Topic Publisher – sends messages from a queue or topic session during an export job.
Message Receiver – processes messages from a queue receiver or topic subscriber during a load job.
Message Sender – processes messages from a queue sender or topic publisher during an export job.
Figure 12 shows an overview of the Teradata Access Module for JMS processing.
Figure 12: Interface Components
