Message-driven beans samples

 

     

  1. Create JMS messages (point-to-point)

    2. Develop and deploy a JMS message sample application that tests WAS message-driven beans support in a point-to-point scenario. Illustrates how to develop and deploy an application that comprises the following components:

    • A Java/JMS program that writes a message to a queue.

    • A message-driven bean that is invoked by a JMS listener when a message arrives on a defined queue.

    For more information, see

    $WAS_HOME/Enterprise/../../WAS51/WAS51/jacl/messaging/doc/PtoP/wsbldPtoP.xml

     

  2. Message Listener (point-to-point)

    3. Designed to demonstrate the use and behavior of message-driven beans for a simple point-to-point scenario. Uses the JMS message sample deployed in the sample above.

    For more information, see:

    $WAS_HOME/Enterprise/../../WAS51/WAS51/jacl/messaging/doc/PtoP/wsrunPtoP.xml

     

  3. Create JMS message publish/subscribe

    4. Develop and deploy a JMS message sample application that tests WAS message-driven beans support in a publish/subscribe scenario. Illustrates how to develop and deploy an application that comprises the following components:

    • A client program that starts the message sequence by publishing a message to a selected topic.

    • A message-driven bean that is invoked by a JMS listener when the broker passes a message to the listener from a topic to which it has subscribed.

    For more information, see

    $WAS_HOME/Enterprise/../../WAS51/WAS51/jacl/messaging/doc/PubSub/wsbldPubSub.xml

     

  4. Message Listener (publish/subscribe)

    5. Demonstrate the use and behavior of message-driven beans for a simple publish/subscribe scenario. Uses the JMS message sample deployed in the publish/subscribe sample above.

    For more information, see:

    $WAS_HOME/Enterprise/../../WAS51/WAS51/jacl/messaging/doc/PubSub/wsrunPubSub.xml

 

Message-driven beans - an overview
Developing an enterprise application to use message-driven beans