If you're in a servlet container, there are some different options.  ActiveGrid works like a normal webapp, so your servlet container docs will tell you more.

In Tomcat, I started by creating an Apache httpd load balancer with a single-node Tomcat.  Once you have your ActiveGrid app deployed on a Tomcat server, follow these steps to create a load-balancing Apache server in front of that single Tomcat node.

http://tomcat.apache.org/connectors-doc/generic_howto/quick.html

and

http://tomcat.apache.org/connectors-doc/generic_howto/workers.html

Then, to add more nodes to the cluster (for performance and failover):

http://tomcat.apache.org/tomcat-5.0-doc/cluster-howto.html

One trick; in Linux, you'll need to configure your ethernet device for multicast.  I did my testing on a single machine, so I had to setup lo for multicast like this:

sudo ifconfig lo multicast
sudo route add -host 228.0.0.4 dev lo

Hope that helps!

-matt

Hi ,

It might sound like a dumb comment but looking at the response, I get the impression that the Activegrid Server is a development platform and not a deployment platform in a sense , that I have to depend on the application for failover deployment techniques . The issue I face in my setup is that I have multiple applications deployed across multiple servers causing overheads in management . I want to consolidate all my application infrastructure  to be easily managed through a single platform . It looks like if I choose ActiveGrid products , i will have to re-write most of my applications in the applications that activegrid supports and rely on the individual application failover techniques rather than get a single platform which gives me all the features

Hello,

Deploying ActiveGrid on a J2EE application/servlet server provides the single managed platform you seek.

All the failover, clustering, balancing etc is configured at the app server level, as small speaks to above.

Sounds like you would want the Java style deployment for your environment.

-EdC