Using WSDL with the SOAPAsyncRequest node

A SOAPAsyncRequest node must be associated with a WSDL file unless it is operating in gateway mode.

About this task

In WSDL mode, when you select a WSDL file for the WSDL file name field on the SOAPAsyncRequest node, the WSDL file is validated to ensure that it is WS-I compliant. If the WSDL file uses a SOAP/JMS transport URI, it is not WS-I compliant, but by default no error is shown. To enable strict WS-I validation and display a warning when a SOAP/JMS transport is used, click Window > Preferences > Integration Development > WSDL > Validation and clear the WS-I BP 1.1: Allow SOAP/JMS as transport URI check box.

After a valid WSDL file is selected, the project that contains the WSDL file is added as a referenced project to the corresponding application or library, if the reference does not exist. To use a WSDL file in a shared library, the container that contains your message flow must reference that shared library. If the WSDL file is not valid, or an incorrect file name is entered, an error message is displayed in the Properties view and all WSDL properties are blank.

If the SOAPAsyncRequest node is created by dragging a WSDL file onto the Message Flow editor, this property is preset to the name of the WSDL file. If the name of the WSDL file is not preset, you can set this property in one of the following ways.

• If you have Deployable WSDL, you can select from the Deployable WSDL files by clicking Browse.
• If you have WSDL definitions, but no message set, then you can create a message set:
  1. Click Browse to open the WSDL Selection window.
  2. Click Import/Create New to open the Import WSDL file wizard.
  3. Enter the message set name and message set project name. Click Next.
  4. Select the relevant option:
     • If your WSDL file exists in your workspace, select Use resources from the workspace, and select the WSDL file.
     • If your WSDL file is in the file system, select Use external resources. Select the WSDL file. Click Next.
  5. Select the WSDL bindings to import. Any warnings or errors are displayed in the wizard banner.
  6. Click Finish. Result: Creates a new message set project and message set, with message definitions. The WSDL definitions are added to the Deployable WSDL folder.
  7. You can now select the WSDL file from the WSDL Selection window. Click OK.
• If you have a message set but no WSDL definition, you must generate a WSDL definition. See Message Sets: Generating a WSDL definition from a message set.
• Drag a WSDL file from a message set onto the node.
• Type in a file name that is relative to the message set project in which the deployable WSDL file exists.

Results

When you save the flow file, it is validated that the WSDL file name exists in the message set. If it is does not, an error is generated, and you will not be able to add a flow that contains this SOAPAsyncRequest node to the BAR file.