Running the Asynchronous Consumer sample consists of putting messages through the message flow. To run this sample you can use the Test Client to put input messages to the message flow. For more information about the Test Client, see Testing message flows by using the Test Client in the WebSphere Message Broker documentation.
If you encounter any problems when you run the sample, see Resolving problems when running samples in the WebSphere Message Broker documentation.
If you want to verify that your web services consumer is configured correctly, complete all of the following steps. If you have set up a TCP/IP Monitor, you have already checked which port the web services provider is using, but you must still configure the consumer to send the messages to your TCP/IP Monitor and then build and redeploy the broker archive (BAR) file.
The default port that web services use is 7800, and the SOAPRequest node is set up to use this port. However, if this port is already in use, the port number is incremented by one.
To check which port your provider execution group is using, issue the following mqsireportproperties command:
mqsireportproperties MB8BROKER -e sampleExecutionGroup -o HTTPConnector -n port
Where sampleExecutionGroup is the execution group for your sample.
To verify that the port that the SOAPRequest node is using is the correct port to call the provider flow, change the port of the SOAPRequest node to the port that the provider execution group is using by completing the following steps:
Ensure that JNDI Administered objects are created as described in Configuring the Asynchronous Consumer sample to use a JMS transport. Also ensure that JNDI properties are set on the SOAPInput and SOAPRequest nodes. Verify that the following WebSphere MQ queues are created either through the WebSphere MQ Explorer or the WebSphere MQ command console.
If the sample ran successfully, the output message is displayed in the Properties view.