2.6.4. Start JBoss Enterprise Application Platform 6 with an Alternative Configuration
If you do not specify a configuration file, the server starts with the default file. However, when you start the server, you can specify a configuration manually. The process varies slightly, depending on whether you are using a Managed Domain or Standalone Server, and depending on which operating system you are using.
Before using an alternate configuration file, prepare it using the default configuration as a template. For a Managed Domain, the configuration file needs to be placed in EAP_HOME/domain/configuration/
. For a Standalone Server, the configuration file should be placed in EAP_HOME/standalone/configuration/
.
Note
Managed Domain
For a Managed Domain, provide the file name of the configuration file as an option to the--domain-config
parameter. You do not need to give the full path, if the configuration file resides in theEAP_HOME/domain/configuration/
directory.Example 2.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
Example 2.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
Standalone server
For a Standalone Server, provide the filename of the configuration file as an option to the--server-config
parameter. You do not need to give the full path to the configuration file if it is in theEAP_HOME/standalone/configuration/
directory.Example 2.5. Using an alternate configuration file for a Standalone Server in Red Hat Enterprise Linux
[user@host bin]$ ./standalone.sh --server-config=
standalone-alternate.xml
Example 2.6. Using an alternate configuration file for a Standalone Server in Microsoft Windows Server
C:\EAP_HOME\bin> standalone.bat --server-config=
standalone-alternate.xml
JBoss Enterprise Application Platform 6 is now running, using your alternate configuration.