Red Hat Training

A Red Hat training course is available for JBoss Enterprise Application Platform Common Criteria Certification

Chapter 4. Running the Examples

JBoss Messaging has a number of examples that are available for download. Refer to the Installation Guide shipped with JBoss Enterprise Application Platform to learn how to install and configure the examples. The Installation Guide is available from http://docs.redhat.com/ under JBoss Enterprise Application Platform > 5.0.
Unzip the examples file to the $JBOSS_HOME/docs/examples directory.
Before you run these examples, deploy the jbm-examples-destinations-service located under $JBOSS_HOME/docs/examples/jboss-messaging-examples/destinations/ to $JBOSS_HOME/server/default/deploy. The
The following examples are included with JBoss Messaging:
$JBOSS_HOME/docs/examples/jboss-messaging-examples/queue/
This example shows a simple send and receive to a remote queue using a JMS client.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/queue-failover/
This example demonstrates the transparent failover of a JMS consumer.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/topic/
This example shows a simple send and receive to a remote topic using a JMS client.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/mdb/
This example demonstrates the use of an Enterprise JavaBean 2.1 MDB with JBoss Messaging.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/ejb3mdb/
This example demonstrates the use of an Enterprise JavaBean 3.0 MDB with JBoss Messaging.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/stateless/
This example demonstrates an Enterprise JavaBean 2.1 stateless session bean interacting with JBoss Messaging.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/mdb-failure/
This example demonstrates rollback and redelivery within an Enterprise JavaBean 2.1.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/secure-socket/
This example demonstrates a JMS client interacting with a JBoss Messaging server via SSL-encrypted transport.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/http/
This example demonstrates a JMS client interacting with a JBoss Messaging server by tunneling traffic via HTTP.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/web-service/
This example demonstrates the JBoss Webservice interacting with JBoss Messaging.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/distributed-queue/
This example demonstrates a JMS client interacting with a JBoss Messaging distributed queue. Two instances of JBoss Enterprise Application Platform are required to run this example.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/distributed-topic/
This example demonstrates a JMS client interacting with a JBoss Messaging distributed topic. Two instances of JBoss Enterprise Application Platform are required to run this example.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/servlet/
This example demonstrates how to use servlet transport with JBoss Messaging. It deploys a servlet and a ConnectionFactory which uses the servlet transport.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/ordering-group/
This example demonstrates the use of strict message ordering. It uses the JBoss Messaging ordering group API to deliver strictly ordered messages, regardless of the message priority.
$JBOSS_HOME/docs/examples/jboss-messaging-examples/bridge/
This example demonstrates the use of a message bridge. It deploys a message bridge within JBoss Enterprise Application Platform, which moves messages from a source to a target queue.
Familiarize yourself with the examples to gain a thorough understanding of JBoss Messaging.

Important

The non-clustered examples expect an instance of JBoss Enterprise Application Platform to be running with all default settings. The readme.html for each example provides the setup details, expected output, and simple troubleshooting.

Important

The clustered examples require two instances of JBoss Enterprise Application Platform to be running, with correctly configured cluster names and port settings. The readme.html for each example provides the setup details, expected output, and simple troubleshooting.