This sample can be extended to write a web service method to
retrieve the required item details from the backend database and to use
WAS 6.0 to setup the Web Services.
Message Broker RETAIL_CLIENT
flow sends the
SOAP JMS request message JMS Destination queue, and the web service
installed on the Websphere Application Server should retrieve the JMS
request message from the JMS Destination queue. The WAS
server will invokes the web services and will send the SOAP reply
message back
to the Message Broker RETAIL_CLIENT flow.
1. Here WAS 6.0 need to be configured to use
JMS as transport media.
2. Write the required web service method using
the WSDL created for the message set. The web service should be
implemented to perform database
operation to
retrieve the item details from the back end database.
3. Install the Web Service application
on
WAS6.0.
4. Use the required service name and port
number to connect to the JMS provider and Message Broker and JMS client.
If you want to extend the sample or indeed test any JMS Node flow with MQ, or any other JMS Provider, then you may find the following tool useful as a simple way to send and receive JMS messages. The tool also has the capabilities to send and receive WebSphere MQ messages so is ideal to test JMS Node flows which include transformations to/from Websphere MQ. The documentation for the tool contains examples of how to run it to send/receive messages to/from a JMS Provider.