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

Reference topic

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

SOAPReply node

This topic describes the SOAPReply node.

Purpose

Use the SOAPReply node to

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

SOAPReply node icon

Using this node in a message flow

The SOAPReply 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:
  • SOAPReply sample

Draft comment:
<<LINK TO FileInput SAMPLE>>

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

Configuring the SOAPReply node

When you have put an instance of the SOAPReply 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. On the Validation tab, set the properties as described in Validation properties. Note that, if a message is propagated to the Failure terminal of the node, it is not validated.

    For more details, refer to Validating messages.

Terminals and properties

The SOAPReply 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.

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 SOAPReply 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 SOAPReply node Validation properties are described in the following table:

Property M C Default Description
Validate     Content value Valid values are None, Content and value, andContent.
Failure action     User trace Valid values are User trace, Exception list, Local error log, and Exception.
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:27

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