4.4. Start JBoss EAP 6 with an Alternative Configuration

Procedure 4.3. Start the Instance with an Alternative Configuration

1. Standalone server

   For a Standalone Server, provide the filename of the configuration file as an option to the --server-config parameter. The configuration file must be located in the EAP_HOME/standalone/configuration/ directory, and you need to specify the file path relative to that directory.

   Example 4.1. Using an alternate configuration file for a Standalone Server in Red Hat Enterprise Linux

   [user@host bin]$ ./standalone.sh --server-config=standalone-alternate.xml

   This example uses the EAP_HOME/standalone/configuration/standalone-alternate.xml configuration file.

   Example 4.2. Using an alternate configuration file for a Standalone Server in Microsoft Windows Server

   C:\EAP_HOME\bin> standalone.bat --server-config=standalone-alternate.xml

   This example uses the EAP_HOME\standalone\configuration\standalone-alternative.xml configuration file.

2. Managed Domain

   For a Managed Domain, provide the file name of the configuration file as an option to the --domain-config parameter. The file must be present in the EAP_HOME/domain/configuration/ directory, and you need to specify the path relative to that directory.

   Example 4.3. Using an alternate configuration file for a Managed Domain in Red Hat Enterprise Linux

   [user@host bin]$ ./domain.sh --domain-config=domain-alternate.xml

   This example uses the EAP_HOME/domain/configuration/domain-alternate.xml configuration file.

   Example 4.4. Using an alternate configuration file for a Managed Domain in Microsoft Windows Server

   C:\EAP_HOME\bin> domain.bat --domain-config=domain-alternate.xml
   
   

   This example uses the EAP_HOME\domain\configuration\domain-alternate.xml configuration file.