When you add a SOAPExtract node to a message flow,
configure it to remove SOAP envelopes or route SOAP messages.
About this task
When you have put an instance of the SOAPExtract
node into a message flow, you can configure it; see Configuring a message flow node. The properties of
the node are displayed in the Properties view.
Procedure
-
On the Description tab, enter a Short
description, a Long description, or both. You can
also rename the node on this tab.
-
On the Basic tab:
-
Specify in Remove envelope whether the node must
remove the soap envelope and place it in the location given in Envelope Destination, or leave it on the message. The default value is that the node
removes the envelope.
-
In Envelope Destination, enter an XPath expression
that represents the destination to which the node will copy the envelope. By default, the node
copies the envelope to the LocalEnvironment ($LocalEnvironment/SOAP/Envelope).
-
In Destination path mode, specify the behavior of the
Envelope Destination property.
- Create path: The node creates the tree if the path
specifies a location that does not already exist. Only simple expressions of the form
aaa/bbb/ccc
in Envelope Destination are
supported. The default.
- XPath location of existing element: If you know
that the destination element exists, you can use any valid XPath 1.0 expression in Envelope Destination.
-
In Route to 'operation' label, specify whether the
node must route the message to the SOAP operation given in the message. The default setting is for
the node to send the message to the Out terminal.
-
In Label Prefix, enter the value to prefix to the
label used for routing by the node. Entering a prefix allows for name spacing between subflows. By
default, no value is prefixed to the label name used for routing the message.