This topic describes the SOAPRequest node.
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:
You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.
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.
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.
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.
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.
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.
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.
The field is pre-populated with Content and Value.
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.
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 |
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 |
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. |
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. |
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 |
Property | M | C | Default | Description |
---|---|---|---|---|
Validate | No | Yes | Content and value | Schema validation properties |
Failure action | No | Yes | User trace |
Property | M | C | Default | Description |
---|---|---|---|---|
Security profile | No | Yes | No security | Value for the security profile in which you can enter your own value. |
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. |