The TCPIP Client Nodes sample uses the TCPIPClientInput,
TCPIPClientOutput, TCPIPClientReceive, TCPIPServerInput, and
TCPIPServerOutput nodes. For an overview of how these nodes work and are configured,
see TCP/IP overview
in the WebSphere Message Broker documentation..
This sample demonstrates how the TCPIP client
nodes can be used within a WebSphere MQ request/reply model to make a
call to a TCP/IP server.
The three message flows (TCPIPAsyncIn, TCPIPAsyncOut, and TCPIPServerSimulation) that are initially deployed by the sample demonstrate an asynchronous model, where separate flows are used to communicate with the TCP/IP server:
This sample also demonstrates how to deploy a synchronous implementation of the same scenario by using the TCPIPSync and TCPIPServerSimulation message flows:
The TCPIPServerSimulation message flow mimics a TCP/IP server that is configured to echo the incoming data (with a slight modification) back on the same port.
You can extend this sample to use
a separate, stand-alone TCP/IP server in place of the TCPIPServerSimulation flow that is described
in the asynchronous scenario.
For further details on how to extend this sample, see
Extending the TCPIP Client Nodes sample.
The following message flows are imported by the
sample: