Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Configuring the JMS Transport >

About the JMS Receiver

The JMS Receiver is a Siebel Server component that makes it possible for the JMS Transport to be invoked asynchronously. The JMS Receiver listens for messages arriving on a JMS Queue or Topic and takes action whenever a message arrives. The JMS Receiver repeatedly invokes a single method of the JMS Transport: ReceiveDispatch, ReceiveDispatchSend, or SubscribeDispatch.

An instance of the JMS Receiver is configured with the parameters of a JMSSubsys named subsystem, which fix the queue or topic to listen to, as well as the action to be taken.

The JMSReceiver task has the following three parts:

• ReceiverConnectionSubsystem is the named subsystem.
• ReceiverDataHandlingSubsystem dispatches the message from the ReceiveQueue to the workflow previously defined.
• ReceiverMethodName is the EAI JMS Transport business service method invoked.

The following is an example of how an instance of the JMS Receiver could be configured and run by using the Siebel Server Manager command-line interface:

create named subsystem MyJMSConnSubsys_SR for subsystem JMSSubsys with
ConnectionFactory="weblogic.examples.jms.QueueConnectionFactory",
ReceiveQueue="weblogic.examples.jms.exampleQueueReceive",
SendQueue="weblogic.examples.jms.exampleQueueSend",
ReceiveTimeout=3000

create named subsystem SiebelEcho for subsystem EAITransportDataHandlingSubsys with
DispatchService="Workflow Utilities",
DispatchMethod="ECHO"

start task for comp JMSReceiver with
ReceiverConnectionSubsystem=MyJMSConnSubsys_SR,
ReceiverDataHandlingSubsystem=SiebelEcho,
ReceiverMethodName=ReceiveDispatchSend

For a detailed workflow example using a JMS Receiver, see Receiving, Dispatching, and Sending JMS Messages.

For a discussion of named subsystems for Siebel EAI, see EAI Transports and Interfaces Overview.

For more information on administering named subsystems, see Siebel System Administration Guide.