A Web Services Description Language (WSDL) document specifies the interface to a Web service, and enables a Web service client to invoke it. A WSDL document that is generated from a message set defines Web service requests and responses in terms of the messages that you have defined in that message set.
Use message definition files with target namespaces when you generate WSDL. If you do not, WebSphere Message Broker defaults the target namespace to the WSDL target namespace.
Before you run the WSDL generator, you must create one or more message category files for your message set. Set the Message Category Kind to wsdl for each category file. Include one or more messages in each category file and assign a role type of wsdl:input, wsdl:output, or wsdl:fault. Each category corresponds to a WSDL operation in the generated WSDL document.
For each message definition file in the message set, one XML Schema file is generated. Within the main WSDL document, operations are defined in terms of logical messages, which are themselves defined in terms of the elements and types defined in these XML Schema files. The WSDL operations and messages are based on the broker messages that you previously specified in the supplied category files.
WSDL operations are grouped into a logical interface or portType, and are then associated with a binding which defines the physical format of the messages. You can select only one of the following bindings when you generate WSDL:
A WSDL service definition specifies the endpoint where the service is available. You can elect to have the service, binding, and portType definitions generated as a single file or as separate files, but the XML Schema files are always generated separately. Tools that consume WSDL are typically more tolerant of the single-file format.