Running WildFly from a custom configuration folder

In this recipe, you will learn how to run WildFly from a custom configuration folder. This can be handy if you want to use the same WildFly installation folder, but run two or more WildFly instances with different configurations.

How to do it…

1. What you have to do is to just copy the standalone folder to a path of your choice.
2. That's it! Now just run WildFly as usual, specifying your configuration folder by passing the -Djboss.server.base.dir directive:

   $ cd $WILDFLY_HOME
   $ ./bin/standalone.sh -Djboss.server.base.dir=/your/config/path

How it works…

On specification of a different jboss.server.base.dir directory, WildFly tries to pick up the standalone.xml file from the expected folder. In fact, your configuration path has to maintain the same folder structure. WildFly lets you override different paths, in case you need to.

The following is a table summarizing all such paths:

There's more…

Furthermore, you can use a different configuration file by specifying it via the --server-config directive, as follows:

$ $WILDFLY_HOME/bin/standalone.sh --server-config=standalone-ha.xml