When you import the sample you might receive warnings in the IBM Integration Toolkit
about the message set and schema elements.
These warnings are message set related and do not affect the running of the sample.
After you have imported and deployed the sample, you
can run it by completing the following steps.
For an overview of how these nodes work and are configured,
see TCP/IP overview
in the IBM Integration Bus documentation.
This sample uses the TCPIPMQVeneer, TCPIPClientEmulation, and
MQServerEmulation message flows.
In the Application Development view, expand the
TCPIPHandshakeSampleFlowProject.
To open the message in the Test Client, expand the Flow Tests directory and
double-click TCPIPHandshakeTest.mbtest. Then, click Enqueue.
To show the input message in hexadecimal format (so that you can compare the input message with the reply message),
select Show in hexadecimal viewer (Read only).
Click Send Message in the Detailed Properties panel. The following
events occur:
A WebSphere MQ request message is placed on the TCPIP_CLIENT_IN
queue. This request is read by the TCPIPClientEmulation message flow.
The TCPIPClientOutput node establishes a TCP/IP connection to port
7779, which is the port that all of the TCPIPServer nodes in the
TCPIPMQVeneer flow use.
The TCPIPClientEmulation flow enters the three-way
exchange with the TCPIPMQVeneer flow to send the request
message.
The TCPIPMQVeneer flow converts the request to XML, and
sends it to the MQServerEmulation flow by using WebSphere MQ.
The MQServerEmulation flow sends the request back to the TCPIPMQVeneer flow
by using WebSphere MQ.
The TCPIPMQVeneer flow converts the message to CWF format.
The TCPIPMQVeneer flow enters the three-way exchange with the
TCPIPClientEmulation flow to send the reply.
The TCPIPClientEmulation flow sends the request to the TCPIP_CLIENT_OUT
queue.
Click Dequeue.
Click Get Message in the Detailed Properties panel.
Check that the reply message has successfully been sent back over WebSphere MQ:
To show the message in hexadecimal format (so that you can compare the input message with the reply message),
select Show in hexadecimal viewer(Read only).
Compare this reply message with the message previously sent by using the Enqueue event.
The messages are identical because the MQServerEmulation flow is
an echo server. Try changing this flow so that the reply message is
different from the request.
If all the previous steps are successful, the sample is complete.
Look at the nodes in the three message flows to see how the
results were achieved.