Transports and Interfaces: Siebel Enterprise Application Integration > EAI Transports and Interfaces Overview > About EAI Transport Methods >

Inbound Methods for a Transport Business Service

Available inbound methods depend on the transport business service in use, such as EAI MSMQ Transport. The inbound methods monitor a specified queue and upon receipt of a message, dispatch it to another service.

There are three inbound methods that can be used to receive requests from another application:

• Receive. Receives an inbound request message and returns it to the caller of the transport.
• Receive and Execute (ReceiveDispatch). Receives an inbound request message and calls another service with the inbound message as input. This called service is known as the Dispatch Service, and the method that is called is known as the Dispatch Method.
• Receive, Execute, and Send (ReceiveDispatchSend). This is a request/response method. It receives an inbound request message, calls another service with the inbound message as input, and then sends the output of the called service as a response. To suppress the response, you can create an output property, on the dispatch service, of type EmptyResponse and set it to True.

  NOTE:  To receive a message and send a reply using the ReceiveDispatchSend method, you must use the <Value> process property in dispatched workflows to hold the message.

NOTE:  There are server components (called receivers) on top of the inbound methods that run as Siebel Server tasks. When running an EAI receiver such as the SAP IDOC Receiver, MQSeries Server, or MSMQ Receiver (using the methods ReceiveDispatch or ReceiveDispatchSend), if the dispatch service has an error, the receiver shuts down. Check the Status column on the Component Tasks for details about the cause of the error.

CAUTION:  Do not set the OM - Preload SRF Data parameter to True for single-threaded Application Object Manager components, which include EAI receivers, such as MQSeries Server Receiver. If OM - Preload SRF Data is True, the Siebel Server will try to initialize the EAI receiver twice, causing the EAI receiver to fail.