SCAReply node
Use the SCAReply node to send a message from the integration node to the originating client in response to a message received by a SCAInput node.
- Developer
- Application Integration Suite
- Standard
- Advanced
- Scale
- Adapter
Purpose
The SCAReply node can be used in a message flow to send a reply back to the client that used an SCAInput node to send an SCA request to the IBM® Integration Bus. The SCAReply node and the SCAInput node must be in the same integration server.
The SCAReply node must use the same transport as the SCAInput node that originated the SCA request.
If an MQ binding is specified in the SCA definition, WebSphere® MQ is used to process the messages, which means that WebSphere MQ must be installed on the same computer as the integration node. You must also specify a queue manager on the integration node by using the -q parameter of the mqsicreatebroker or mqsichangebroker command.WebSphere MQ is not provided as part of the IBM Integration Bus installation package, but your license for IBM Integration Bus entitles you to install and use WebSphere MQ. For more information about using WebSphere MQ with IBM Integration Bus, see Installing WebSphere MQ.
The SCAReply node is contained in the SCA drawer of the message flow node palette, and is represented in the IBM Integration Toolkit by the following icon:
Terminals and properties
When you have put an instance of the SCAReply 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. All mandatory properties for which you must enter a value (properties that do not have a default value defined) are marked with an asterisk.
The SCAReply node terminals are described in the following table.
| Terminal | Description |
|---|---|
| In | The input terminal that accepts a message for processing by the node. |
| Failure | The output terminal to which the message is routed if a failure is detected in this node. |
| Out | The output terminal to which the message is routed if it has been propagated successfully, and if further processing is required within this message flow. The message is propagated unchanged, except for the addition of status information. |
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 following table describes the Description properties of the SCAReply node.
| Property | M | C | Default | Description |
|---|---|---|---|---|
| Node name | No | No | The node type: SCAReply | 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 following table describes the Validation properties of the SCAReply node.
| Property | M | C | Default | Description |
|---|---|---|---|---|
| Validate | Yes | Yes | Inherit | Valid values are None, Content, Content and Value, and Inherit. |
| Failure action | Yes | No | Exception | This property controls what happens if validation fails. You can set this property only if you set Validate to Content or Content and Value. Valid values are User Trace, Local Error, Exception, and Exception List. |
| Property | M | C | Default | Description |
|---|---|---|---|---|
| Events | No | No | None | Events that you have defined for the node are
displayed on this tab. By default, no monitoring events are defined
on any node in a message flow. Use Add, Edit,
and Delete to create, change or delete monitoring
events for the node; see Configuring monitoring event sources by using monitoring properties for details. You can enable and disable events that are shown here by selecting or clearing the Enabled check box. |