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 list all available parameters for the start-up scripts, use the -h parameter.

Procedure 2.2. Run multiple instances of JBoss EAP standalone servers on a single machine

1. Create a copy of the EAP_HOME/standalone/ directory directly under EAP_HOME/ for each standalone server. For example, to create a directory for standalone servers node1 and node2, type the following commands.

   $ cd EAP_HOME
   $ cp -a ./standalone ./node1 
   $ cp -a ./standalone ./node2

2. Start each JBoss EAP standalone instance by specifying the node name, IP address, server directory, optional server configuration file, and optional port offset. The command uses the following syntax:

   $ ./bin/standalone.sh -Djboss.node.name=UNIQUE_NODENAME -Djboss.server.base.dir=EAP_HOME/NODE_DIRECTORY -b IP_ADDRESS -bmanagement MGMT_IP_ADDRESS --server-config=SERVER_CONFIGURATION_FILE -Djboss.socket.binding.port-offset=PORT_OFFSET

   1. This example starts node1

      $ cd EAP_HOME
      $ ./bin/standalone.sh -Djboss.node.name=node1 -Djboss.server.base.dir=EAP_HOME/node1 -b 10.10.10.10 -bmanagement 127.0.0.1
      

   2. This example to start node2 depends on whether the machine supports multiple IP addresses.
      • If the machine supports multiple IP addresses, the following command is to be used.

        $ cd EAP_HOME
        $ ./bin/standalone.sh -Djboss.node.name=node2 -Djboss.server.base.dir=EAP_HOME/node2 -b 10.10.10.40 -bmanagement 127.0.0.40
        

      • If the machine does not support multiple IP addresses, you must specify a jboss.socket.binding.port-offset property to avoid a port conflict.

        $ cd EAP_HOME
        $ ./bin/standalone.sh -Djboss.node.name=node2 -Djboss.server.base.dir=EAP_HOME/node2 -b 10.10.10.10 -bmanagement 127.0.0.1 -Djboss.socket.binding.port-offset=100
        

Procedure 2.3. 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.

   To list all available parameters for the start-up scripts, use the -h parameter.

Procedure 2.4. Configure the Host Name Using a System Property

1. Open the host configuration file for editing, for example, host.xml.
2. Find the host element in the file, for example:

   <host name="master" xmlns="urn:jboss:domain:1.6">

3. If it is present, remove the name="HOST_NAME" attribute declaration. The host element should now look like the following example.

   <host xmlns="urn:jboss:domain:1.6">

4. Start the server passing the -Djboss.host.name argument, for example:

   -Djboss.host.name=HOST_NAME

Procedure 2.5. Configure the Host Name Using a Specific Name

1. Start the JBoss EAP slave host using the following syntax:

   bin/domain.sh --host-config=HOST_FILE_NAME

   For example:

   bin/domain.sh --host-config=host-slave01.xml

2. Launch the Management CLI.
3. Use the following syntax to replace the host name:

   /host=EXISTING_HOST_NAME:write-attribute(name="name",value=UNIQUE_HOST_NAME)

   For example:

   /host=master:write-attribute(name="name",value="host-slave01")

   You should see the following result.

    "outcome" => "success"

   This modifies the host name attribute in the host-slave01.xml file as follows:

   <host name="host-slave01" xmlns="urn:jboss:domain:1.6">

4. You must reload the server configuration using the old host name to complete the process

   reload --host=EXISTING_HOST_NAME

   For example:

   reload --host=master

Procedure 2.6. Create managed domain on two machines

1. On Machine 1

   1. Use the add-user.sh script to add management user. For example, slave01, so the host can authenticate the domain controller. Note the SECRET_VALUE from the add-user output.
   2. Start domain with host-master.xml config file, which is preconfigured for dedicated domain controller.
   3. Use -bmanagement=$IP1 to make domain controller visible to other machines.

      EAP_HOME/bin/domain.sh --host-config=host-master.xml -bmanagement=$IP1

2. On Machine 2

   1. Update EAP_HOME/domain/configuration/host-slave.xml file with user credentials.

      	<?xml version='1.0' encoding='UTF-8'?>
              <host xmlns="urn:jboss:domain:1.6" name="slave01">   
              <!-- add user name here -->
               <management>
                  <security-realms>
                     <security-realm name="ManagementRealm">
                        <server-identities>
                          <secret value="$SECRET_VALUE" />   
                          <!-- use secret value from add-user.sh output-->
                        </server-identities> 
                        ...

   2. Start host.

      EAP_HOME/bin/domain.sh --host-config=host-slave.xml  -Djboss.domain.master.address=$IP1 -b=$IP2

3. Now we can manage the domain.

   via CLI:

   EAP_HOME/bin/jboss-cli.sh -c --controller=$IP1
   

   via Web Console:

   http://$IP1:9990
   

   Access the server index page:

   http://$IP2:8080/
   http://$IP2:8230/
   

Procedure 2.7. Run Multiple Host Controllers on a Single Machine

1. Copy the EAP_HOME/domain directory for the domain controller.

   cp -r EAP_HOME/domain /path/to/domain1

2. Copy the EAP_HOME/domain directory for a host controller.

   cp -r EAP_HOME/domain /path/to/host1

3. Start the domain controller using /path/to/domain1.

   EAP_HOME/bin/domain.sh --host-config=host-master.xml -Djboss.domain.base.dir=/path/to/domain1

4. Start the host controller using /path/to/host1.

   EAP_HOME/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.base.dir=/path/to/host1 -Djboss.domain.master.address=IP_ADDRESS -Djboss.management.native.port=PORT

Procedure 2.8. Stop an instance of JBoss EAP 6

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

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

Procedure 2.9. Stop an instance which was started as an operating system service.

• • 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 the script.

  • Microsoft Windows Server

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

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

1. Obtain the process ID (PID) of the process:

   • If only a single instance is running (standalone mode)

     Either of the following commands will return the PID of a single instance of JBoss EAP 6:
     • pidof java
     • jps
       (The jps command will return an ID for two processes; one for jboss-modules.jar and one for jps itself. Use the ID for jboss-modules.jar to stop the EAP instance)

   • If multiple EAP instances are running (domain mode)

     Identifying the correct process to end if more than one instance of EAP is running requires more comprehensive commands be used.
     • The jps command can be used in verbose mode to provide more information about the java processes it finds.
       Below is an abridged output from a verbose jps command identifying the different EAP processes running by PID and role:

       $ jps -v
       12155 jboss-modules.jar -D[Server:server-one] -XX:PermSize=256m -XX:MaxPermSize=256m -Xms1303m 
       ...
       
       12196 jboss-modules.jar -D[Server:server-two] -XX:PermSize=256m -XX:MaxPermSize=256m -Xms1303m 
       ...
       
       12096 jboss-modules.jar -D[Host Controller] -Xms64m -Xmx512m -XX:MaxPermSize=256m 
       ...
       
       11872 Main -Xms128m -Xmx750m -XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=96m -XX:+UseCodeCacheFlushing 
       ...
       
       11248 jboss-modules.jar -D[Standalone] -XX:+UseCompressedOops -verbose:gc 
       ...
       
       12892 Jps 
       ...
       
       12080 jboss-modules.jar -D[Process Controller] -Xms64m -Xmx512m -XX:MaxPermSize=256m 
       ...
       

     • The ps aux command can also be used to return information about multiple EAP instances.
       Below is an abridged output from a verbose ps aux command identifying the different EAP processes running by PID and role:

       $ ps aux | grep java
       username 12080  0.1  0.9 3606588 36772 pts/0   Sl+  10:09   0:01 /path/to/java -D[Process Controller] -server -Xms128m -Xmx128m -XX:MaxPermSize=256m 
       ...
       
       username 12096  1.0  4.1 3741304 158452 pts/0  Sl+  10:09   0:13 /path/to/java -D[Host Controller] -Xms128m -Xmx128m -XX:MaxPermSize=256m 
       ...
       
       username 12155  1.7  8.9 4741800 344224 pts/0  Sl+  10:09   0:22 /path/to/java -D[Server:server-one] -XX:PermSize=256m -XX:MaxPermSize=256m -Xms1000m -Xmx1000m -server -
       ...
       
       username 12196  1.8  9.4 4739612 364436 pts/0  Sl+  10:09   0:22 /path/to/java -D[Server:server-two] -XX:PermSize=256m -XX:MaxPermSize=256m -Xms1000m -Xmx1000m -server 
       ...
       

     In the above examples, the Process Controller processes are the processes to stop in order to stop the entire domain.
     The grep utility can be used with either of these commands to identify the Process Controller:

     jps -v | grep "Process Controller"

     ps aux | grep "Process Controller"

2. Send the process the TERM signal, by running kill PID, where PID is the process ID identified by one of the commands above.