See information about the latest product version
SCA nodes
SCA nodes support interoperability between WebSphere® Message Broker and WebSphere Process Server.
- The SCAInput and SCAReply nodes are analogous
to the SOAPInput and SOAPReply nodes, and are used
in a message flow that provides an SCA endpoint. These SCA nodes are
used to construct a message flow which implements SCA.
The SCAInput node listens for SCA inbound requests (from WebSphere Process Server to WebSphere Message Broker).
The SCAReply node sends a reply back to the client that originated the SCA request. See SCAInput node and SCAReply node.
- The SCAAsyncRequest and SCAAsyncResponse nodes are
used to construct a pair of message flows that call a WebSphere Process
Server service component asynchronously.
The SCAAsyncRequest node sends an SCA outbound request to a service component that runs in WebSphere Process Server.
The SCAAsyncResponse node receives the response from a business process that is running in WebSphere Process Server and to which the previous asynchronous request was made. The SCAAsyncResponse node can be in the same message flow or in a separate message flow.
Calling a WebSphere Process Server service component asynchronously means that the SCAAsyncRequest node sends a request but does not wait for the associated response to be received, although it might wait for an acknowledgment of the request.
The nodes are used as a pair, and correlate responses and requests. See SCAAsyncRequest node and SCAAsyncResponse node.
- The SCARequest node
is used to send a request to WebSphere Process
Server.
The node is configured using a Broker SCA Definition (.outsca)
file; depending on the contents of the .outsca file,
requests are either:
- Two-way, synchronous; the node sends the request, then blocks until it receives a response, or the timeout period is exceeded.
- One-way; the node sends a request only.