ad15761_.htm |
Last updated Friday, 21 July 2017Files and other objects are created by the WSDL Generator.
This topic is relevant only if you are using a message set to contain your message models. If you are using an application or library, you can create a new WSDL file by using the WSDL editor.
The default file and definition element names are shown in the following table. Message Set is the supplied message set name and <Definition Name> is the supplied Definition Name solicited by the wizard.
| 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_SetService | wsdl | <Definition Name>Service |
| Binding File | Message_SetBinding | wsdl | <Definition Name>Binding |
| Interface File | Message_Set | wsdl | <Definition Name> |
If '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'.
The WSDL generator appends the result of the generation operation to a report file, listing all errors which occurred. The file name is:
Message_Set.wsdlgen.report.txtThe following tables show the element or 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, because this section 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 values shown in the following table apply to the WSDL definition as a whole.
| Element | Attribute | Value |
|---|---|---|
| definitions | xmlns | Assign namespace prefixes. |
| definitions | targetNamespace | The WSDL Namespace solicited by the wizard, defaulting to http://tempuri.org/<Message Set>. |
| message | name | <operation>_<role> where <operation> is the operation name and <role> is in, out, or fault |
| part | name | The 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. |
| portType | name | Message_SetPortType |
| binding | name |
|
| soap:binding | style | From the value of Style set in the wizard. |
The following values apply to each individual WSDL operation:
| 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 |
|
| soap:header, soap:fault, soap:body | use | This element is set to literal. |
The message set provides the basis for many important broker features, including mapping support and ESQL code completion at development time, and validation at run time.
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 IBM® Integration Toolkit.
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.
Last updated Friday, 21 July 2017