SAPReply node
Use the SAPReply node to send a reply to an SAP synchronous callout. Use this node with an SAPInput node to implement a message flow that acts as a remote function call (RFC) destination.
Purpose
An SAP program can call functions on remote RFC servers. These functions can be called asynchronously or synchronously, where they must provide a reply. A message flow can act as an RFC destination and receives the function call through the SAPInput node. When the function is called synchronously, use the SAPReply node to send a reply back.
The SAPReply node is contained in the WebSphere Adapters drawer of the message flow node palette, and is represented in the IBM App Connect Enterprise Toolkit by the following icon:
Using this node in a message flow
You can use an SAPReply node in the same message flow as an SAPInput node, or in a different flow from an SAPInput node. The SAPReply node must be deployed in the same integration server as the SAPInput node.
If the message flow is transactional, information about the state of in-flight transactions is held in IBM MQ queues, which means that IBM App Connect Enterprise must have access to IBM MQ when it is processing these messages. To enable this, ensure that IBM MQ is installed on the same computer as the integration node. For more information about using IBM MQ with IBM App Connect Enterprise, see Installing IBM MQ.
Terminals and properties
When you have put an instance of the SAPReply 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. To display the properties of the node in the Properties dialog, either double-click the node, or right-click the node and click Properties. All mandatory properties for which you must enter a value (those properties that do not have a default value defined) are marked with an asterisk.
The SAPReply 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 when the message is propagated. |
| Out | The output terminal to which the message is routed if it has been sent to an external resource. The message is 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 in the Properties view) 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).
| Property | M | C | Default | Description |
|---|---|---|---|---|
| Node name | No | No | The node type: SAPReply | 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. |
| Property | M | C | Default | Description |
|---|---|---|---|---|
| SAP Reply Identifier | No | No | $LocalEnvironment/Destination/Adapter/Reply/ReplyIdentifier | Use this property to specify the location of
the SAP reply identifier. The SAPReply node issues an exception
in the following circumstances:
|
| 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. You can enable and disable events that are shown here by selecting or clearing the Enabled check box. |