Configuring a JBoss EAP Standalone Server

45 minutes
  • 4 Learning Objectives

About this Hands-on Lab

JBoss EAP can be run in a number of modes, but the standalone server mode is just that — a single instance of JBoss that can be used to deploy and manage Java applications through the provided console or the CLI. For the most part, the JBoss EAP can run successfully out-of-the-box, but we can further configure access by altering any of the provided standalone server configuration files.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Update Standalone Networking
  1. Attempt to access the JBoss management console at PUBLICIP:9990. This attempt should fail.

  2. From the CLI, switch to the JBoss home directory:

    cd /opt/jboss-eap/
  3. Open the standalone configuration file:

    sudo vim standalone/configuration/standalone.xml
  4. We need to update our networking interfaces to accept connections from outside the local host. Look for the <interfaces> code block and update the address to use instead:

        <interface name="management">
            <inet-address value="${}"/>
        <interface name="public">
            <inet-address value="${jboss.bind.address:}"/>
  5. Press Esc and enter :wq to save and exit the file.

Update Users for the Standalone Server
  1. Open the user group configuration file:

    sudo vim standalone/configuration/
  2. Add the tina user to the dev group:

  3. Press Esc and enter :wq to save and exit the file.

Update the Log Level
  1. Open the log file for when the JBoss server boots:

    sudo vim standalone/configuration/
  2. Set the log level to DEBUG:

  3. Press Esc and enter :wq to save and exit the file.

Confirm that Configuration Changes
  1. Restart JBoss:

    sudo systemctl restart jboss-eap-rhel
  2. Check that you can access the management console at PUBLICIP:9990 using the provided lab credentials.

  3. Check the user configuration to ensure that the group persists:

    sudo vim standalone/configuration/
  4. Finally, we want to review the log file:

    sudo vim standalone/configuration/

    Note: For this configuration, the change does not persist. This is because the log level is set for when the service boots and will be overwritten once the boot process is finished. The log file is the only setting that has this behavior.

Additional Resources

You have recently finished an install of JBoss EAP in standalone mode and find that the management console cannot be accessed by all required parties. Your coworker, Tina, has requested addition to the dev group.

Using the configuration files located at /opt/jboss-eap/standalone/configuration/, update the standalone server's network interface configuration to allow access from any IP and add the tina user to the appropriate group.

Since you are making changes to the standalone.xml configuration itself and have encountered issues before, you also want to ensure the startup logs run in DEBUG mode in the event of errors upon restart. Restart the jboss-eap-rhel service for the changes to take effect.

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?