The WebSphere Embedded JMS Provider software is a separate (optional) download from the Application Server 5.0 Trial software. Be sure to download and install it along with the Application Server.The publish and subscribe sample consists of an application client that publishes a message on one of three topics and an MDB that is listening on a fourth, wildcard topic, that receives messages published on any of the first three. The MDB prints the message it receives to the standard output.
1. Click on the "Message-driven beans" sample in navigation pane of the Samples Gallery.The page that is displayed contains the information that is needed to setup the embedded JMS provider for this sample (described next).
3. Start the WebSphere Administrative Console and navigate to <your server>->Resources > WebSphere JMS Provider.
4.
5. Click the New button.
6. Enter the values given on the TechNotes page under "Defining properties for topic connection factory".
7.
8. Choose WebSphere JMS Provider in the content pane.
9.
10. Create four new topics with the property values given on the TechNotes page under "Defining properties for topics".
11.
12. In the content pane, choose on the name of your server, then on Message Listener Service, then on Listener Ports, then on SamplePubSubListenerPort.
13. The values for these properties on the TechNotes are incorrect. Verify that the following property values are set:
14.
15. In the content pane, under "Publish and Subscribe", click Configure and Run.
16. Follow the instructions there for running the sample and confirming that the server received the message by examining the standard output log file.
The standard output log file for your server is called SystemOut.log and can be found under install_root/Appserver/logs/<your server>.The point-to-point sample consists of an application client that sends a message to a queue and an MDB that is configured to be triggered by messages on that queue. The MDB takes the message it receives and sends it to a second queue where the client receives it back and compares it to the original message it sent.
1. The page that is displayed contains the information that is needed to setup the embedded JMS provider for this sample (described next).
3. In the WebSphere Administrative Console, navigate to: <your server>->Resources > WebSphere JMS Provider.
4.
5. Click the New button.
6. Enter the values given on the TechNotes page under "Defining properties for queue connection factory".
7.
8. Choose WebSphere JMS Provider in the content pane.
9.
10. Create two new queues with the property values given on the TechNotes page under "Defining properties for queues".
11.
12. In the content pane, choose on the name of your server, then on Message Listener Service, then on Listener Ports, then on SamplePtoPListenerPort.
13. The values for these properties on the TechNotes page are incorrect. Verify that the following property values are set:
14.
15. In the content pane, under "Point-to-Point", click Configure and Run.
16. Follow the instructions there for running the sample and confirming that the MDB received and sent back the message to the client.
Copyright © TIBCO Software Inc. All Rights Reserved.