JBoss farming service is back!

Please note this tutorial has been written for an older version of JBoss application server (v.5).

If you are running WildFly or JBoss EAP 6/7 the Farming Service is not available any more. The recommended way to distribute applications to your cluster using a single distribution point is to switch to Domain mode and use management instruments.

This way, you will be able to deploy/undeploy your applications to a Server Group in a similar way you used to do with the Farming Server, although you will be using Management Instruments such as the CLI and Web Console.

Read more here:

How to deploy applications on WildFly

If your applications will be running on the Cloud, we suggest checking this tutorial

Building and deploying a Jakarta EE application on OpenShift

JBoss Forming Service for JBoss 5 users

Good news. With the release 5.1.0 of the application server the farming service is back and has got even better!
Some JBoss user were disappointed that with the release 5.0.0 of the AS, the farming service was unavailable. This was because of the new profile service available in JBoss 5.The newer release of the AS fixed the problem. The farming service is back and has got some new features.

1# The farming service is available also for exploded directories.

In the 4.X release of JBoss the farming service was available only for archive deployment. With the new release you can safely deploy exploded deployments too.

2# Optimized file transfer
In the release 4.X each time a new node joined the cluster, it received a copy of the content of the farm directory even if the application was already deployed on it. This needless operation has been eliminated in the release 5.1.0

3# Deploy and farming service are now synchronized
In the earlier release if you removed a deployment unit from the deploy folder and not from the farm directory, at next startup the application would have been redeployed again. Tbis has been corrected in JBoss AS 5.1.0