Chapter 2. Application Server Management

Procedure 2.1. Start the Platform Service as a Standalone Server

1. For Red Hat Enterprise Linux.

   Run the command: EAP_HOME/bin/standalone.sh

2. For Microsoft Windows Server.

   Run the command: EAP_HOME\bin\standalone.bat

3. Optional: Specify additional parameters.

   To print a list of additional parameters to pass to the start-up scripts, use the -h parameter.

Procedure 2.2. Start the Platform Service as a Managed Domain

1. For Red Hat Enterprise Linux.

   Run the command: EAP_HOME/bin/domain.sh

2. For Microsoft Windows Server.

   Run the command: EAP_HOME\bin\domain.bat

3. Optional: Pass additional parameters to the start-up script.

   For a list of parameters you can pass to the start-up script, use the -h parameter.

Procedure 2.3. Start the Instance with an Alternative Configuration

1. 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 2.1. 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 2.2. 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.

2. 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 2.3. 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 2.4. 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.

Procedure 2.4. Stop a standalone instance of JBoss EAP 6

1. Stop an instance which was started interactively from a command prompt.

   Press Ctrl-C in the terminal where JBoss EAP 6 is running.

2. Stop an instance which was started as an operating system service.

   Depending on your operating system, use one of the following procedures.

   • Red Hat Enterprise Linux

     For Red Hat Enterprise Linux, if you have written a service script, use its stop facility. This needs to be written into the script. Then you can use service scriptname stop, where scriptname is the name of your script.

   • Microsoft Windows Server

     In Microsoft Windows, use the net service command, or stop the service from the Services applet in the Control Panel.

3. Stop an instance which is running in the background (Red Hat Enterprise Linux)

   1. Locate the instance from the process list. One option is to run the command ps aux |grep "[j]ava -server". This returns one result for each JBoss EAP 6 instance that is running on the local machine.
   2. Send the process the TERM signal, by running kill process_ID, where process_ID is the number in the second field of the ps aux command above.