WSDL generation

This topic defines the objects created by the WSDL Generator.

Generated Files

The default file and definition element names are shown in the table below. <Message Set> is the supplied message set name and <Definition Name> is the supplied Definition Name solicited by the wizard.

Start of change
Table 1. WSDL File Naming Convention
File File Name File Extension Value of name attribute on WSDL <definitions> element
Service File (single-file format) <Message Set> wsdl <Definition Name>
Service File (multi-file format) <Message Set>Service wsdl <Definition Name>Service
Binding File <Message Set>Binding wsdl <Definition Name>Binding
Interface File <Message Set> wsdl <Definition Name>
End of change

Start of changeIf 'Deployable WSDL' is generated, no additional XML schema (xsd) files are generated, and the WSDL refers directly to the broker message definition (mxsd) files; otherwise, separate XML schema (xsd) files are generated, unless you selected 'inline schema'.End of change

Report File

The WSDL generator appends the result of the generation operation to a report file, listing any errors which occurred. The file name is:

<Message Set>.wsdlgen.report.txt

WSDL Content

The tables below show the element / attribute values to be set in the generated WSDL. The elements are described top-down as they appear in a conventionally ordered WSDL document. The <schema> section of the WSDL definition is not shown since this corresponds directly to the broker message definitions.

Element names are from the WSDL 1.1 namespace except where prefixed by soap: for the WSDL SOAP namespace. Operation elements occur in both the binding and portType sections, so operation is qualified as necessary – for example, portType / operation.

The following values apply to the WSDL definition as a whole:

Table 2. WSDL objects
Element Attribute Value
definitions xmlns assign namespace prefixes.
Start of changedefinitionsEnd of change Start of changetargetNamespaceEnd of change Start of changeThis is the WSDL Namespace solicited by the wizard, defaulting to http://tempuri.org/<Message Set>.End of change
Start of changemessageEnd of change Start of changenameEnd of change Start of change<operation>_<role> where <operation> is the operation name and <role> is in, out, or faultEnd of change
part name name of the broker message. If Style is set to rpc, the body parts are defined using the type attribute. If not, the body parts are defined using the element attribute.
Start of changeportTypeEnd of change Start of changenameEnd of change Start of change<Message Set>PortTypeEnd of change
binding name
  • ”<Message Set>SOAP_HTTP_ Binding”
  • ”<Message Set>SOAP_JMS_ Binding”
Start of changesoap:bindingEnd of change Start of changestyleEnd of change Start of changeFrom the value of Style set in the wizard.End of change

Start of changeThe following values apply to each individual WSDL operation:End of change

Table 3. WSDL <operation> objects
Element Attribute Value
operation name The name of the operation specified in the wizard.
soap:operation style From the value of Style set in the wizard.
input, output, fault name <operation>_<role>, where <operation> is the operation name, and <role> is Input, Output, or Fault.
soap:body namespace
  • If Style has been set to rpc then it is the namespace of the corresponding broker message.
  • If Style has been set to document the attribute is not generated.
soap:header, soap:fault, soap:body use This is set to literal.
Start of change

Message Set

The message set provides the basis for many important broker features, including mapping support and ESQL code completion at development time, and validation at runtime.

Therefore, the WSDL that you use in the broker at development time (for example, when configuring SOAP nodes) is integrated with the message set, and references the broker message definitions (mxsd) rather than ordinary Schema (xsd) files. This is referred to as deployable WSDL and is displayed under the category Deployable WSDL in the workbench.

Deployable WSDL is generated when you specify your Message Set Folder (the immediate child of your Message Set Project) as the destination directory for your WSDL.

Otherwise, regular WSDL is generated, along with separate XML schema (xsd) files if these were requested. Regular WSDL cannot be used to configure SOAP nodes, but is suitable for consumption by external applications such as .NET.

Assuming that you are generating deployable WSDL for use in a message flow, the flow typically needs to be able to parse and validate the runtime SOAP messages described by that WSDL. The WSDL generator, therefore, adds additional definitions to your message set:
  • For rpc-style WSDL, additional definitions for the WSDL operations themselves are added to your message set
  • For the version of the SOAP Envelope used by the WSDL an mxsd file is added – this will be soapenv11.mxsd or soapenv12.mxsd.
  • For use by ESQL Content assist and the Mapping editor primarily, a definition of the SOAP_Domain_Msg tree.
End of change
Related concepts
Message modeling
The message model
Related tasks
Developing message models
Working with a message definition file
Working with message model objects
Generating a WSDL definition from a message set
Related reference
Message model reference information
Message model object properties
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:15

ad15761_