MQ you say? Does it have to be MQ?
Here's a tutorial on setting up JMS within the WebSphere
Test Environment. The steps are identical for the full blown application server. You just have to set up a message bus, attach a server/cluster to the bus, and then configure a queue or topic and associate that with the bus as well. From there, an MDB can read messages off the queue.
To plop messages onto the queue, you need to create a connection factory, and a JNDI resolvable reference to the queue in question. This is also done through the admin console. An activation specification isn't a bad thing to configure either.
Here's a tutorial that sets up all of the JMS required features within WebSphere:
http://www.technicalfacilitation.com/examscam/tf/get.php?link=13configuringmessaging Here's another tutorial for creating Message Driven Beans (MDBs) using IBM's Rational Appliation Developer. It also includes a stateless session bean (SLSB) dropping a message on the queue/topic so the MDB can read it.
http://www.technicalfacilitation.com/examscam/tf/get.php?link=14creatingJMSMDBs You'll notice the screen for creating JMS resources also have options for attaching to an MQ queue. Once you're attached, the steps are similar to the ones uses for standard JMS/MDB messaging.
Cheers!
-Cameron McKenzie
