Start of change
WebSphere Message Brokers
File: ac56190_.dita
Writer: Kate Hostler

Reference topic

This build: July 31, 2007 21:21:27

SOAPRequest node

This topic describes the SOAPRequest node.

Purpose

Use the SOAPRequest node to send a request. The node is a synchronous request and response node and blocks after sending the request until the response is received.

The SOAPRequest node is contained in the Web Services drawer of the message flow node palette, and is represented in the workbench by the following icon:

SOAPRequest node icon

Using this node in a message flow

The SOAPRequest node can be used in any message flow that needs to accept messages in files. Look at the following sample to see how to use this node:
  • SOAPRequest sample

You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.

Configuring the SOAPRequest node

When you have put an instance of the SOAPRequest node into a message flow, you can configure it. For more information, see Configuring a message flow node. To display its properties, either double-click the node, or right-click the node and click Properties. All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.

  1. Optional: On the Description tab, enter a short description, a long description, or both. You an also rename the node on this tab.
  2. Use the Basic tab to configure the following WSDL Properties:
    • WSDL file name.
      Draft comment:
      (Same as SOAPAsyncRequest node)
      This property type is String. This field allows you to change the WSDL file you use to configure this node. This field displays the message 'choose a WSDL file by dragging and dropping a wsdl on the node, clicking the browse button or typing the file name'. The field can be configured in various ways:
      • You can click Browse to select a WSDL file to import from the workspace.
      • You can type in a file name that is relative to the message set project in which the WSDL exists, that is, type in the full path name of the WSDL but exclude the message set project name.
      • You can drag and drop a WSDL file onto the node.

      When you have made a new selection the WSDL file is validated. The WSDL validation is exactly the same as the validation that is done when you drag and drop the WSDL file onto a flow. After the file is validated, the message set to which it belongs is added as a reference project if it does not already exist.

      If the WSDL file is not validated, or an incorrect file name is entered, an error message is displayed on the editor and the corresponding WSDL properties are blank.

      If the same file name is entered into the text box, no validation or updates occur. In order to refresh the WSDL file contents click Browse, or drag and drop the WSDL file onto the node.

      Compile Time Validation: At the time of flow compilation, it is verified that there is one instance only of the referenced WSDL in the symbol table. An error is generated on the node if the referenced WSDL cannot be resolved, or if there are more than one WSDL files of the same name in the workspace. For a multi-file WSDL, verification only takes place for the main WSDL. For a multi-file WSDL it is also verified that the imports inside the main WSDL have been imported.

      The following cases lead to error conditions on this property editor:
      • If the WSDL file does not come from a message set project, or if the WSDL was not imported as described in the following topics:
      • There are no http bindings in the WSDL file.
      • There are no port types in the WSDL file.
      • An empty string is typed in the text box after a valid WSDL file name has been entered.
      • File name entered in the text box does not exist.
    • Port type.
      Draft comment:
      (Same as SOAPAsyncRequest node)
      This property type is String. The field lists all of the port types defined in the WSDL document.
      Draft comment:
      Which document?
      By default, the first port type found in the WSDL that has an associated http binding with it, is selected.
      Error Conditions:
      • Selected port type does not contain at least one operation.
    • Imported binding.
      Draft comment:
      (Same as SOAPAsyncRequest node)
      This property type is String. This property is updated any time the port type value changes. The field lists all SOAP bindings with HTTP transport (6.1) associated with the selected port type. Bindings are listed in the same order in which they appear in the WSDL source. The selected binding initially is the one that has both ports and operations. If there is no such binding, then binding with just ports is selected. Also, if no bindings have ports then the first binding in the list is selected.
      Error Conditions:
      • No SOAP bindings (with HTTP transport) in the WSDL document are associated with the port type.
      • Selected binding does not have any operations.
    • Binding operation. This property type is String. The box lists all operations defined by the selected port type and the first operation in the list is selected by default.
    • Service port.
      Draft comment:
      (Similar to SOAPRequest node)
      This property type is String. The port field is updated any time the selected binding is updated. The field lists all WSDL ports that point to the selected binding. The first port for the binding is the selected port by default.
      Error Conditions:
      • No ports point to the selected binding.
    • Target namespace. This is a hidden String property on this tab. It is updated with the Target namespace of the WSDL when the WSDL file name is configured.
  3. Use the Advanced tab, to define your headers:
    • Enable WS-addressing This property type is Boolean. This indicates whether to engage WS-addressing; the default is Enabled.
    • Must understand headers. This property type is Complex. This property lists all SOAP headers for the broker runtime to mark as understood.

      This prevents the Axis 2 server from signaling SOAP fault, should the SOAP input message contain one or more of such headers with the must understand bit turned on.

      This property is split into WSDL-defined and User-defined tables, each of which is a complex property. Each table has the following layout:
      • Must understand column. Selecting the checkbox in this column indicates that header listed in this row is added to the must understand header list.
      • Operation name column
      • Header name column
      • Header namespace column
    The WSDL-defined table is read-only, and is populated, based on the SOAP headers defined in the output part of the selected operations.

    By default, Must understand check boxes are selected for ALL entries in the WSDL-defined table. When the selected binding is updated, the WSDL-defined header table is updated accordingly.

    You can add custom headers, that is, headers not defined in the WSDL, in the user-defined table. This table includes Add, Edit, and Remove buttons. You need to select the must understand checkbox for the newly added custom header, in order for the header to be added to the must understand headers list.

  4. Use the HTTP Transport tab to set the HTTP transport related properties:
    • Web Service URL.
      Draft comment:
      (Same as HTTPRequest node)
      This property type is String. This property is automatically set from the SOAP address of the selected port. However, if you override the value then your value persists, and the URL is not configured from the service port.
    • Request timeout (in seconds). This property type is Integer. This is the wait time for a remote server to respond with a 'message received' acknowledgement.
    • HTTP(S) Proxy Location. This property type is String. This is the location of the proxy server to which requests are sent.
    • Protocol (if using SSL) This property type is Enumerate. The following options are available:
      SSL
      (the default). This option tries to connect using the SSLv3 protocol first, but allows the handshake to fall back to the SSLv2 protocol where the SSLv2 protocol is supported by the underlying JSSE provider.
      SSLv3
      This option tries to connect with the SSLv3 protocol only. Fallback to SSLv2 is not allowed.
      TLS
      This option tries to connect with the TLS protocol only. Fallback to SSLv3 or SSLv2 is not allowed.

      Note that both ends of an SSL connection must agree on the protocol to use, so the chosen protocol must be one that the remote server can accept.

    • Allowed SSL Ciphers (if using SSL) This property type is String. This setting allows you to specify a single cipher (such as SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA) or a list of ciphers that will be the only ones used by the connection. This set of ciphers must include one or more that are accepted by the remote server.

      A comma is used as a separator between the ciphers. The default value is an empty string, which allows the node to use any, or all, of the available ciphers during the SSL connection handshake. This method allows the greatest scope for making a successful SSL connection.

    • Use HTTP Transport. This is a hidden Boolean property on this tab. This property is set to true when the WSDL file name property is configured.
  5. Use the Response Message Parsing tab with its corresponding Parser Options sub tab to set the properties associated with the response message:
    • Message Domain. This property type is String. The value is set to SOAP and the property is greyed out.
    • Message Set. This property type is String. The value is set to be the message set project value, on the drag and drop of WSDL; the property is greyed out.
    • Message Type. This property type is String. This value is set to blank and the property is greyed out.
    • Message Format. This property type is String. This value is set to blank and the property is greyed out.
    Parser Options sub tab. The following properties are listed on this tab:
    • Parse timing. This property type is Enumerate. Enter one of the values On Demand. Immediate, or Complete.
    • Soap Parser Options. This property type consists of check boxes for the following:
      • Build tree using XML schema data types
      • Retain mixed content
      • Retain comments
      • Retain processing instructions
    • Opaque elements. This property type is Complex.
  6. Use the Validation tab to set the properties associated with validating:
    • Validate. This property type is Enumerate. Enter one of the values None. Content and Value, or Content.

      The field is pre-populated with Content and Value.

    • Failure Action. This property type is Enumerate. Enter one of the values User trace. Exception list, Local erroror Exception.
  7. Use the Security tab to implement the security properties associated with the node, and its associated WS-Security sub tab to properties associated with Web Services security:
    • Security Profile This property type is String. Enter one of the values No Security. Default Propagation, Default LDAP, or Default TFIM.
    WS-Security sub tab. This property type is Complex and consists of two columns:
    • XPath Expression and an associated Alias value are added to the WS-Security table.

      The alias is resolved in a Policy Set that is created by the administrator. The Policy Set resolves the alias to either encrypt or sign the part of the message referred to by the XPath expression.

Terminals and properties

The SOAPRequest node terminals are described in the following table.

Terminal Description
Failure The output terminal to which a message is routed if a failure is detected when the message is propagated to the Out flow (such as a message validation failure). Failures routed to this terminal include those caused by the retry processing occurring before the retry propagates the message to the Out flow.
Out The output terminal to which the message is routed if it has been successfully put to the output queue, and if further processing is required within this message flow. If no errors occur within the input node, a message received from an external resource is always sent to the Out terminal first.
Catch The output terminal to which the message is routed if an exception is thrown downstream and caught by this node.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined; the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).

The SOAPRequest node Description properties are described in the following table:

Property M C Default Description
Node name No No The node type The name of the node.
Short Description No No None A brief description of the node.
Long Description No No None Text that describes the purpose of the node in the message flow.

The SOAPRequest node Basic properties are described in the following table:

Property M C Default Description
WSDL file name Yes No <None> The name of the WSDL file used to configure this node
Port type Yes No From WSDL The selected port type from the WSDL file
Imported binding Yes No From WSDL The selected binding from the WSDL file
Binding operation Yes Yes From WSDL The selected binding from the WSDL file
Service port Yes No The first operation in the list. All operations defined by the selected port type.
Target namespace Yes No From WSDL The target namespace from the WSDL file
The SOAPRequest node Advanced properties are described in the following table:
Property M C Default Description
Enable WS-Addressing No Yes True Whether to engage Web Services Addressing.
WSDL defined SOAP headers Header name Yes No Must understand selected Populated, based on the defined SOAP headers.
WSDL defined SOAP headers Header namespace Yes No Must understand selected Populated, based on the defined SOAP headers.
WSDL defined SOAP headers Operation name Yes No Must understand selected Populated, based on the defined SOAP headers.
User defined SOAP headers Header name No Yes None Custom header name
User defined SOAP headers Header namespace No Yes None Custom header namespace
User defined SOAP headers Operation name No Yes None Custom header operation name
The SOAPRequest node HTTP Transport properties are described in the following table:
Property M C Default Description
Web service URL Yes Yes SOAP address of the selected port The URL of the SOAP address selected.
Request timeout (sec) No Yes 180 The time the client waits for a for a remote server to respond with a 'message received' acknowledgement.
HTTP(S) Proxy location No Yes Blank The location of the proxy server.
Protocol (if using SSL) No Yes SSL The selected protocol if you use SSL
Allowed SSL ciphers (if using SSL) No Yes None The specific SSL cipher, or ciphers, you are using.
The SOAPRequest node Response Message Parsing properties are described in the following table:
Property M C Default Description
Message domain Yes No SOAP The value of the message domain can not be changed.
Message set Yes No The value of the message set project value on drag and drop of WSDL The value of the message set can not be changed.
Message type Yes No Blank The value of the message type can not be changed.
Message format Yes No Blank The value of the message format can not be changed.
The SOAPRequest node Parser Options properties are described in the following table:
Property M C Default Description
Parse timing Yes Yes On demand  
Build tree using XML schema data types No Yes False  
Retain mixed content No Yes False  
Retain comments No Yes False  
Retain processing instructions No Yes False  
Opaque elements No Yes Blank  
The SOAPRequest node Validation properties are described in the following table:
Property M C Default Description
Validate No Yes Content and value Schema validation properties
Failure action No Yes User trace  
The SOAPRequest node Security properties are described in the following table:
Property M C Default Description
Security profile No Yes No security Value for the security profile in which you can enter your own value.
The SOAPRequest node WS-Security properties are described in the following table:
Property M C Default Description
Alias No Yes   This is the alias value associated with an XPath expression. This option is related to Web-services security only.
XPath Expresssion No Yes   The XPath expression added to the Web Services security table. This option is related to Web-Services security only.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:21:28

ac56190_.dita This topic's URL is:
End of change