Bookshelf v7.5: Transport Methods

Transports and Interfaces: Siebel eBusiness Application Integration Volume III > EAI Transports and Interfaces Overview > EAI Transports >

Transport Methods

The method on a transport adapter's business service controls the action to be performed by the transport. There are two outbound methods and three inbound methods available for EAI Transports. Not every method is available on every transport.

For each method, there are a number of common parameters, as shown on Table 4, as well as transport-specific parameters that are discussed in the respective chapter for each transport.

Outbound Methods

Available outbound methods depend on the transport business service in use, such as EAI MQSeries AMI Transport or EAI MSMQ Transport. The business service sends messages from the Siebel application using the appropriate communications protocol, such as MQSeries, MSMQ, HTTP, and so on. There are two outbound methods that you use to send requests from a Siebel application to another application:

Send. Sends a message from a Siebel application when the Siebel application does not need a response. This is an asynchronous (with the exception of the EAI HTTP Transport which expects a correct HTTP response) request method, because the Siebel application does not need to wait for a response before continuing with the process.

Send and Receive. Sends a message from the Siebel application when the Siebel application needs to receive a response before continuing. This is a synchronous request and response method, because it requires a response before the Siebel application can continue.

Inbound Methods

Available inbound methods depend on the transport business service in use, such as EAI MQSeries AMI Transport or 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, Send (ReceiveDispatchSend)

This is a request/response method. 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: 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, MQSeries AMI Receiver, 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.

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, Send (ReceiveDispatchSend)	This is a request/response method. 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.

Transports and Interfaces: Siebel eBusiness Application Integration Volume III
Published: 23 June 2003