Running the Coordinated Request Reply sample
You can run the
Coordinated Request Reply sample to perform the following processing:
- Convert a WebSphere MQ message with XML payload into one
containing the same data but in a CWF format.
- Store the initial ReplyToQ and ReplyToQMgr in a WebSphere MQ
message for later use.
- Run a simulated application to read a WebSphere MQ message
with a payload in CWF format, add the current time to the message, and
reply using a WebSphere MQ message with a payload in CWF format.
- Retrieve the original ReplyToQ and ReplyToQMgr from the WebSphere
MQ message created in Step 2 above.
- Convert the WebSphere MQ message with payload in CWF format into
one containing the same data but in an XML format, and send it as a
reply to the original request using the retrieved values for ReplyToQ
and ReplyToQMgr.
To run the Coordinated Request Reply sample:
- Ensure that the sample message flows and message set have been
deployed.
- In the Broker Development view, expand the Coordinated Request Reply Message Flow Project.
- Double click Requester.mbtest to open it in the Test Client, and click on Enqueue.
- Scroll to the bottom of the message data portion of the screen
and observe the value for CompletionTime
time which is 12:00:00.
- Click Send Message to place a
WebSphere MQ message on the
input queue of the Request message flow.
- In the Test Client, click on Dequeue
- Click on Get Message to get a message from the GET_REQREP_OUT queue.
Scroll to the end of the message and observe that the initial
CompletionTime value <st1:time hour="0" minute="0">of 12:00:00</st1:time>
has been replaced by the current time. This was done in the
Backend Reply message flow and demonstrates that the message was
processed in the Backend Reply message flow.
Once you have observed that the value of CompletionTime has been changed to a value other than 12:00:00 you have successfully run
the Coordinated Request Reply
sample. Should you run the test at exactly 12:00:00 then rerun
just after to ensure that the time in the message is updated in the
Backend message flow.
Back to sample home