IBM MQ transport for SOAP sender
Sender classes are provided for Axis and .NET Framework 1 and .NET Framework 2. The sender constructs a SOAP request and puts it on a queue, it then blocks until it has read a response from the response queue. We can alter the behavior of the classes by passing different URIs from a SOAP client. For .NET Framework 3 use IBM MQ custom channel for Microsoft Windows Communication Foundation (WCF).
Purpose
The IBM MQ SOAP sender puts a SOAP request to invoke a web service onto an IBM MQ request queue. The sender sets fields in the MQRFH2 header according to options specified in the URI, or according to defaults.
If you need to change the behavior of a sender beyond what is possible using the URI options, write your own sender. Your sender can work with the IBM MQ transport for SOAP listeners, or with other SOAP environments. Your sender must construct SOAP messages in the format defined by IBM MQ. The format is supported by the IBM MQ SOAP listener, and also SOAP listeners provided by WebSphere Application Server and CICS®. Your sender must follow the rules for an IBM MQ requestor. The IBM MQ SOAP listener returns reply and report messages. See MQMD SOAP settings for details how to set the report options in the MQMD. The report options control the report messages returned by the IBM MQ SOAP listener.
Description
The IBM MQ SOAP Java sender is registered with the Axis host environment for the jms: URI prefix. The sender is implemented in the class com.ibm.mq.soap.transport.jms.WMQSender, which is derived from org.apache.axis.handlers.BasicHandler. If the Axis host environment detects a jms: URI prefix it invokes the com.ibm.mq.soap.transport.jms.WMQSender class. The class blocks after placing the message until it has read a response from the response queue. If no response is received within a timeout interval the sender throws an exception. If a response is received within the timeout interval the response message is returned to the client using the Axis framework. Your client application must be able to handle these response messages.
For Microsoft.NET Framework 1 and .NET Framework 2 services, the IBM MQ SOAP sender is implemented in the class IBM.WMQSOAP.MQWebRequest, which is derived from System.Net.WebRequest and System.Net.IwebRequestCreate. If .NET Framework 1 or .NET Framework 2 detects a jms: URI prefix it invokes the IBM.WMQSOAP.MQWebRequest class. The sender creates an MQWebResponse object to read the response message from the response queue and return it to the client.
com.ibm.mq.soap.transport.jms.WMQSender is a final class, and IBM.WMQSOAP.MQWebRequest is sealed. We cannot modify their behavior by creating subclasses.
Parameters
Set the URI to control the behavior of the IBM MQ SOAP sender in a web service SOAP client. The deployment utility creates web service client stubs incorporating the URI options supplied to the deployment utility.