This is the fourth of a set of
instructions about how to set up your system to use WS-Addressing
with WebSphere® Message
Broker; these instructions
illustrate how to test the message flows.
This topic describes how to test
the message flows that you have already constructed. In this scenario,
you use a tool that uses HTTP protocol rather than WebSphere MQ protocol. You can use any tool
that has the facilities that are described in the following procedure.
- Start the tool and select http://localhost:nnnn/,
where nnnn is the address of the port that you
are using.
- Set the URL to the host, port, and selection for the deployed
flow. The SOAPInput nodes
listen on a different port from the HTTP nodes, and the listener is
built into the execution group rather than using a different
process.
- The SOAPInput node
expects a SOAPAction entry in the HTTP headers, therefore you must
add one.
- Click Add New Header.
- Enter the Value part of the header. The value must match the SOAPAction attribute
of the SOAP:operation element in your code.
- Select New Header in the Name pane.
- Change the name from New Header to SOAPAction and
click Enter.
- Select Load File and go to the directory
that contains the XML file you want to use.
- Select the file and click Open. Note the following conditions:
- If the message does not include any WS-Addressing entries, the ReplyTo and FaultTo locations
default to anonymous. This means that the results
are returned on the original client connection.
- If the message includes a WS-Addressing header (ReplyTo)
with a value of anonymous, the reply is returned
to the original client by using the original TCP/IP connection.
- If the message includes a WS-Addressing header with a value of FaultTo explicitly
included, the reply is returned to that address rather than the default
of using the location that was specified in the ReplyTo header.
- Click Send to test the flow. The result appears in the right pane.