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

Importing from WSDL

You can import a WSDL file into an application or library, or import a WSDL file into a message set.

The following sections describe how to import from WSDL.

Importing a WSDL file into an application or library
Importing a WSDL file into a message set

Importing a WSDL file into an application or library

Before you start:

Ensure that you have completed the following tasks:

Read concept information in Applications and libraries.
Create an application or library by following the instructions in Creating an application or Creating a library.

When you import a WSDL file into an application or library, all the WSDL files that are referenced are imported into the specified folder. If there are multiple WSDLs with the same name but with different paths, then the files are suffixed with an increasing index number. For example: If there are multiple files that are named my.wsdl in the context of import, then these files are renamed to my1.wsdl, my2.wsdl, my3.wsdl, and so on, in the specified folder.

To import a WSDL file into an application or library, complete the following steps.

In the Application Development view, right-click an application or library, then click New > Message Model.
The New Message Model wizard opens.
Select SOAP XML, then click Next.
Select I already have WSDL for my data, then click Next.
The name of the application or library that you selected in step 1 is shown. You can choose another application or library to contain your WSDL file, or you can create a new one by clicking New.
Optional: Specify a root destination folder. Click Browse to select an existing folder or create a new one.
The imported WSDL and schema files are placed under the root folder with the same organization as the source files. The files are not placed in directories that match the namespace of the WSDL or schema files.
Optional: Specify an XML schema file. This field is completed automatically when you select a file from your workspace or your file system. By default, the XML schema file shares the name of the imported file.
Select the WSDL file to import from your workspace, or from an external URL, then click Next.
Select the bindings to import, then click Finish.
For each binding that you import, a message root is created for every global element that is used by a part in the operations of the binding.

Files are created and are shown under the selected application or library in the Application Development view.

Next:

Configure an existing SOAP node by dragging a deployable WSDL file onto the node. Alternatively, you can create a Web service based on WSDL in your workspace, and implement the operations as separate subflows. For more information, see Creating an integration service based on WSDL.

Importing a WSDL file into a message set

Before you start:

Ensure that you have completed the following tasks:

The wizards for message set development have been provided for compatibility with previous versions of the product. To develop message sets in WebSphere Message Broker Version 8.0, you must activate the message set development wizards by completing the following steps.

Click Window > Preferences.
Expand Integration Development and click Message Sets.
Select Enable menus for Message Set development, then click OK.

The following steps describe how to create a new message definition file, or overwrite the contents of an existing file.

In the Application Development view, right-click the message set project, then click New > Message Definition File From > WSDL file.
The New Message Definition File wizard opens.
Step through the wizard, completing the details as required.
You must choose whether the WSDL file, or files, that you want to import are in the current workspace in the IBM Integration Toolkit or are outside the workspace.
Select the appropriate check boxes to control the following behavior:
- Copy the source file (or files) into a directory of the message set project. By default, this check box is cleared.
- Add the SOAP and XMLNSC domains to your message set so that you can use the SOAP nodes. By default, this check box is selected.
The panels and options that are available in the wizard depend on the settings that you select. Some fields in the wizard might not be available, because the field has a mandatory setting, the field has only one possible value, or the field is not being used as a result of other settings that have been made.

When you have finished importing the WSDL file or files, complete the following steps.

Check carefully for any errors in the report that is created when the file is imported. You can find this report in the log directory in the project that contains the message definition that you have created. The report has a <wsdl-file-name>.wsdl.report.txt file descriptor, where <wsdl-file-name> is the name of the WSDL definition that you are importing.
Review the messages that are shown in the IBM Integration Toolkit task list to check whether any new warnings or errors are shown.

Required SOAP Envelope and SOAP encoding message definitions are automatically added to your message set during the import. If required, you can also import these definitions manually by using the New Message Definition File wizard, by selecting the new option IBM supplied message.

ad30500_.htm |

Last updated Friday, 21 July 2017