IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Message Sets: Generating a WSDL definition from a message set

To ensure the highest interoperability of your Web services, use the document style of WSDL whenever possible. If rpc style WSDL is necessary, use literal encoding.

Before you start you must already have completed the following tasks:

Replace any deprecated constructs before generating WSDL representations of your message models.

To generate a WSDL definition:

Switch to the Integration Development perspective.
In the Application Development view, right-click the folder that contains the message set file from which you want to generate a Web service definition, and select Generate > WSDL Definition. This starts the Generate WSDL wizard.
Step through the wizard completing the details as required. Some of the panels and options are subject to settings that you make within the wizard and might not always be shown. Also, some fields in the wizard might be greyed out. This happens when a field has a mandatory setting, or when the field is not used because of settings that have already been made in other fields.
By default, the wizard creates the WSDL in the message set project. If you are going to use the WSDL to configure a SOAP node, create the WSDL in the message set, not the message set project.

On completion of the Generate WSDL wizard, you have generated a WSDL definition. The file extension for WSDL files is .wsdl, and the file extension for any imported schema files in multi-file mode (where the WSDL definition is split over a number of files) is .xsd.

This following is an example of the WSDL that is generated for a JMS binding:

<wsdl:service name='HTTP'>
  <wsdl:port binding='tns:JMSSoapBinding' name='HTTP'>
    <wsdlsoap:address
       location='jms:/queue?destination=jms/MyQueue&amp;
                 connectionFactory=jms/MyCF&amp;
                 priority=5&amp;
                 targetService=GetQuote'/>
  </wsdl:port>
</wsdl:service>

Note: The various parts of the location string are broken over separate lines for clarity, but are generated as a continuous string without additional white space.

ad18211_.htm |

Last updated Friday, 21 July 2017