Senders

For Axis web services, a sender is implemented in the final class com.ib.mq.soap.transport.jms.WMQSender which is derived from the org.apache.axis.handlers.BasicHandler class. For Microsoft .NET services, a sender is implemented in the sealed class IBM.WMQSOAP.MQWebRequest. This class is derived from System.Net.WebRequest and System.Net.IwebRequestCreate.

The supplied SOAP/WebSphere MQ sender puts a SOAP request for invocation of a service to a WebSphere MQ request queue. The sender sets fields in the WebSphere MQ MQRFH2 header according to options specified in the URI, or according to defaults. The options that can be specified in the URI are detailed in Specifying the URI; all the fields in the MQRFH2 are described in . If we need to change the behavior of a sender beyond what is possible using the URI options, you will have to write your own senders. See .

The Java sender blocks after placing the message until it has read a response from the response queue. If no response is received within a given timeout interval the sender throws an exception. If a response is received within the timeout interval the response message is returned to the client via the Axis framework. Your client application must be able to handle these response messages.

The .NET sender creates an MQWebResponse object to read the response message from the response queue and return it to the client.