WebSphere
MQ Web Services Transport connects
Web services and clients that use the HTTP protocol for messaging.
WebSphere Message Broker allows Web service providers
and their clients to communicate with:
- each other
- other applications using different protocols
through message flows in a broker. The topics linked below describe the
WebSphere
MQ Web Services Transport. Web service
applications can also use other transports as described in
Web services, WSDL and message flows.
Tip: You can create your own WSDL files, or generate WSDL files
from message set definitions that you have created in the
Message Broker Toolkit,
and use these files with tools such as
Rational Application Developer or
Microsoft Visual Studio .NET to build Web services applications that connect
to
WebSphere Message Broker. When you generate the WSDL
file, you can specify one or more of the following bindings to be created:
- SOAP over HTTP (using WebSphere
MQ Web Services Transport)
- SOAP over JMS (using WebSphere MQ Real-time Transport)
For more detail on WebSphere
MQ Web Services Transport,
refer to the following topics:
For more information, follow the Web services link on the developerWorks Web
site.
For help with using HTTPS see Implementing SSL authentication
.