Lab
A Cloud Guru

Configuring a JBoss EAP Standalone Server

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.

Try for free Contact sales

Path Info

Level

Beginner

Duration

45m

Published

Jan 24, 2020

Challenge

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 127.0.0.1 address to use 0.0.0.0 instead:
```
<interfaces>
    <interface name="management">
        <inet-address value="${jboss.bind.address.management:0.0.0.0}"/>
    </interface>
    <interface name="public">
        <inet-address value="${jboss.bind.address:0.0.0.0}"/>
    </interface>
</interfaces>
```
5. Press Esc and enter :wq to save and exit the file.
Challenge

Update Users for the Standalone Server
1. Open the user group configuration file:
```
sudo vim standalone/configuration/mgmt-groups.properties
```
2. Add the tina user to the dev group:
```
tina=dev
```
3. Press Esc and enter :wq to save and exit the file.
Challenge

Update the Log Level
1. Open the log file for when the JBoss server boots:
```
sudo vim standalone/configuration/logging.properties
```
2. Set the log level to DEBUG:
```
logger.level=DEBUG
```
3. Press Esc and enter :wq to save and exit the file.
Challenge

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/mgmt-groups.properties
```
4. Finally, we want to review the log file:
```
sudo vim standalone/configuration/logging.properties
```
  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.

Author

A Cloud Guru

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

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.