Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

Standalone Clustered Mode

Standalone clustered operation mode is for when you want to run {project_name} within a cluster. This mode requires that you have a copy of the {project_name} distribution on each machine you want to run a server instance. This mode can be very easy to deploy initially, but can become quite cumbersome. To make a configuration change you’ll have to modify each distribution on each machine. For a large cluster this can become time consuming and error prone.

Standalone Clustered Configuration

The distribution has a mostly pre-configured app server configuration file for running within a cluster. It has all the specific infrastructure settings for networking, databases, caches, and discovery. This file resides in …​/standalone/configuration/standalone-ha.xml. There’s a few things missing from this configuration. You can’t run {project_name} in a cluster without configuring a shared database connection. You also need to deploy some type of load balancer in front of the cluster. The clustering and database sections of this guide walk you through these things.

Standalone HA Config

standalone ha config file

Any changes you make to this file while the server is running will not take effect and may even be overwritten by the server. Instead use the command line scripting or the web console of {appserver_name}. See the {appserver_admindoc_name} for more information.

Standalone Clustered Boot Script

You use the same boot scripts to start {project_name} as you do in standalone mode. The difference is that you pass in an additional flag to point to the HA config file.

Standalone Clustered Boot Scripts

standalone boot files

To boot the server:

$ .../bin/ --server-config=standalone-ha.xml
> ...\bin\standalone.bat --server-config=standalone-ha.xml