JAmba is a JMS Message Routing package.
author: Mike Heijmans parabuzzle@users.sourceforge.net
---------------------------------------------------------

For more information please visit http://www.jambagroup.org

This file is to get here to get you started.

Since JAmba is still in Alpha, documentation is a little scarce.
However, here is some information on getting started:

First, JAmba has only been officially tested on JBoss-4.2.0.GA and
an ant target is provided for building and packaging as a sar for
JBoss. Everything you will need for packaging the sar should be included
in the source code. 

REQUIREMENTS:
So far we have found that JGroups version 2.6 is required to run JAmba.
We have supplied the required jar in the lib directory. You will need
to replace the JGroups jar from your Application Server's lib directory
and JAmba should work.

   WARNING! - the packaged JGroups that comes with JBoss-4.2.0 uses
              different config directives so, if you use JGroups for
              EJB or the cluster caching, you WILL need to change the
              udp or tcp config for those services. You can use the
              supplied example configs (udp.xml) and plugin the existing
              udp address and port for the service you are upgrading.

You will also need the following jars in your JDK lib/endorsed directory:
   *serializer.jar
   *xalan.jar
   *xercesImpl.jar
   *xml-apis.jar
These should come packaged with any newer JDK but you can find the files on
the apache.org website for the Apache Xerces project if you do not have them.


QUICK START FOR JBOSS
If you want to just build it and start experimenting follow these steps:
Run these commands:

[user@host]# ant build
[user@host]# ant package.jboss

This should build the jar and package everything you need in bin/jamba.sar
Now, put jamba.sar in your deploy directory and move jgroups-all.jar in to
your JBoss lib directory (removing any jgroups jars that are already there).

Configure jambaConfig.xml, udp.xml, and jGroupsStack.xml.

Reconfigure any files that may be using JGroups, restart JBoss and you should
be all set.

Here is a list of files that may need JGoups configuration changes:
*cluster-service.xml
*ejb3-clustered-sfsbcache-service.xml
*ejb3-entity-cache-service.xml
*jboss-web-cluster.sar/META-INF/jboss-service.xml