Using the SOAP domain to parse a SOAP web service

Use the SOAP parser to create a common WSDL-based logical tree format for working with web services.

Before you begin

Read the concept information in SOAP parser and domain.

About this task

To use the SOAP domain to parse your SOAP web service, complete the following steps:

Procedure

  1. Create an application or library. Alternatively, you can create a message set, or locate an existing message set.
    If you are likely to reuse your imported WSDL for multiple solutions, use a shared library.
  2. If you are using a message set, indicate that the message set supports the SOAP domain by either setting the default message domain project to SOAP, or select the SOAP check box (under Supported message domains).
  3. To create a message root (in an application or library) or a message definition file (in a message set), import your WSDL file into the application, library, or message set.
    Message roots or message definition files for the SOAP envelope and the SOAP logical tree are also added to the application, library, or message set automatically.
  4. Add the application, library, or message set to a BAR file.

    If the WSDL file is in an application or library, the WSDL files and XSD files appear directly inside the .appzip, .shlibzip, or .libzip file inside the BAR file. If the WSDL file is in a message set, the required XML schema and WSDL files are generated in a file with the extension .xsdzip.

  5. Deploy the BAR file.

Results

If you associate your WSDL with a SOAP node in your message flow, the Message domain property on the node is automatically set to SOAP and cannot be changed. If you are using a message set, the Message model property is automatically set to the name of the message set that contains the WSDL and cannot be changed. If you are using an application or library, the Message model property is empty and cannot be changed.

You can use a WSDL file in a shared library to configure a message flow in another container (an application, for example). However, that container must reference the shared library that contains the WSDL file. If you use a WSDL file from a shared library to configure a SOAP node, the Message model property contains the name of the shared library in braces, {}. The WSDL file name property also contains the name of the shared library.