IBM MQ 7.5 was EOS 30th April 2018. Click EOS notice for more details

SOAP reference

WebSphere MQ transport for SOAP reference information arranged alphabetically.

amqwSOAPNETListener: IBM WebSphere MQ SOAP listener for .NET Framework 1 or 2
Syntax and parameters for the WebSphere MQ SOAP listener for .NET Framework 1 or 2.
amqswsdl: generate WSDL for .NET Framework 1 or 2 service
amqswsdl takes a Web service written for .NET Framework 1 or 2, and generates the WSDL for the class, inserting the URI you provide for the WebSphere MQ transport for SOAP into the generated WSDL.
amqwclientconfig: create Axis 1.4 Web services client deployment descriptor for WebSphere MQ transport for SOAP
amqwclientconfig creates the client-config.wsdd Axis 1.4 client deployment descriptor file.
amqwdeployWMQService: deploy Web service utility
The deployment utility prepares a service class for use as a Web service using WebSphere MQ as the transport.
amqwRegisterdotNet: register IBM WebSphere MQ transport for SOAP to .NET
Register IBM WebSphere MQ transport for SOAP to the global assembly cache on .NET.
Apache software license
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/
MQMD SOAP settings
The IBM WebSphere MQ SOAP sender and IBM WebSphere MQ SOAP listener create a message descriptor (MQMD). The topic describes the fields you must set in the MQMD if you create your own SOAP sender or listener.
MQRFH2 SOAP settings
The IBM WebSphere MQ SOAP senders and listeners create or expect to receive an MQRFH2 with the following settings.
runivt: WebSphere MQ transport for SOAP installation verification test
An installation verification test suite (IVT) is provided with IBM WebSphere MQ transport for SOAP. runivt runs a number of demonstration applications and ensures that the environment is correctly set up after installation.
Secure Web services over IBM WebSphere MQ transport for SOAP
You might secure Web services that use the IBM WebSphere MQ transport for SOAP in one of two ways. Either create an SSL channel between the client and server, or use Web services security.
SimpleJavaListener: IBM WebSphere MQ SOAP Listener for Axis 1.4
Syntax and parameters for the IBM WebSphere MQ SOAP listener for Axis 1.4.
WebSphere MQ SOAP listeners
A WebSphere MQ SOAP listener reads an incoming SOAP request from the queue specified as the destination in the URI. It checks the format of the request message and then invokes a Web service using the Web services infrastructure. A WebSphere MQ SOAP listener returns any response or error from a Web service using the reply destination queue in the URI. It returns WebSphere MQ reports to the reply queue.
IBM WebSphere 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. You can alter the behavior of the classes by passing different URIs from a SOAP client. For .NET Framework 3 use WebSphere MQ custom channel for Microsoft Windows Communication Foundation (WCF).
Transactions
Use the -x option when starting the listener, to run Web services transactionally. Select the integrity of messages by setting the persistence option in the service URI.
URI syntax and parameters for Web service deployment
The syntax and parameters to deploy a IBM WebSphere MQ Web service are defined in a URI. The deployment utility generates a default URI based on the name of the Web service. You can override the defaults by defining your own URI as a parameter to the deployment utility. The deployment utility incorporates the URI in the generated Web service client stubs.
W3C SOAP over JMS URI for the WebSphere MQ Axis 2 client
Define a W3C SOAP over JMS URI to call a Web service from an Axis 2 client using WebSphere MQ JMS as the SOAP transport. The Web service must be provided by a server that supports WebSphere MQ JMS and the W3C SOAP over JMS candidate recommendation for the SOAP/JMS binding.
Supported Web services
Code that has been written to run as a Web service does not need to be modified to use the IBM WebSphere MQ transport for SOAP. You do need to deploy services differently to run with the IBM WebSphere MQ transport for SOAP rather than using HTTP.
IBM WebSphere MQ transport for SOAP Web service clients
You can reuse an existing SOAP over HTTP client with IBM WebSphere MQ transport for SOAP. You must make some small modifications to the code and build process to convert the client to work with IBM WebSphere MQ transport for SOAP.

Parent topic: Developing applications reference