Red Hat JBoss Enterprise Application Platform Administration I

JBoss EAP 7 is designed in a modular fashion, with multiple subsystems that you can customize to support Jakarta EE application requirements, such as database connectivity, batch processing, and integration tools. The subsystem configuration is maintained in the standalone.xml file for the standalone mode, and the domain.xml file for a managed domain mode.

These configuration files can be customized using three different approaches:

To access the JBoss EAP 7 management console, launch the web browser and navigate to http://localhost:9990.

By default, the JBoss EAP 7 management console is secured and you need to provide the username and password that you entered during the installation process: admin/redhat123.

Figure 1.15: The JBoss EAP 7 Management Console

To access the management CLI, launch a terminal, navigate to the JBOSS_HOME/bin directory, and run the jboss-cli.sh script. For example:

$ ./jboss-cli.sh --connect
[standalone@localhost:9990 /] :product-info 
{
    "outcome" => "success",
    "result" => [{"summary" => {
        "host-name" => "workstation.lab.example.com",
        "instance-identifier" => "cb96ecfd-6033-4595-bc80-dcbed3b79e30",
        "product-name" => "JBoss EAP",
        "product-version" => "7.4.11.GA",
        "product-community-identifier" => "Product",
        "product-home" => "/opt/jboss-eap-7.4",
        "last-update-date" => "6/29/23, 2:31 AM",
        "standalone-or-domain-identifier" => "STANDALONE_SERVER",
        "host-operating-system" => "Red Hat Enterprise Linux 9.0 (Plow)",
        "host-cpu" => {
            "host-cpu-arch" => "amd64",
            "host-core-count" => 2
        },
        "jvm" => {
            "name" => "OpenJDK 64-Bit Server VM",
            "java-version" => "11",
            "jvm-version" => "11.0.14.1",
            "jvm-vendor" => "Red Hat, Inc.",
            "java-home" => "/usr/lib/jvm/java-11-openjdk-11.0.14.1.1-6.el9.x86_64"
        }
    }}]
}

Enter 'quit' or 'q' to exit the management CLI.

If you invoke the management CLI without any arguments, then it starts in 'disconnected' mode. To connect to the server, use the --connect command option.

Another option to connect to a JBoss EAP 7 standalone server instance, or to a domain controller, is to use the connect <IPAddress> CLI command.

If the JBoss EAP instance, or the domain controller are running locally, then the management CLI does not prompt for credentials. Elsewhere in this course you learn to disable this automatic authentication for local access. If the JBoss EAP instance, or the domain controller are running in a different host, then the management CLI always asks for credentials.

Ultimately, the XML configuration file can be edited by using a text editor. For the standalone server, the file is available at JBOSS_HOME/standalone/configuration/standalone.xml.

<server xmlns="urn:jboss:domain:16.0">
    <extensions>
        <extension module="org.jboss.as.clustering.infinispan"/>
        ...
    </extensions>
    <management>
        ...
    </management>
    <profile>
        <subsystem xmlns="urn:jboss:domain:logging:8.0">
    ...

The file defines multiple <extension> tags. The extensions represent all the modules needed by JBoss EAP to start a subsystem. After the <extension> and the <management> tags, the file defines multiple <subsystem> tags. As a JBoss EAP system administrator, you manage and customize these subsystems to provide applications with the application server services.

Similarly, the managed domain also has the same set of configurations defined at JBOSS_HOME/domain/configuration/domain.xml. The structure, and differences, are discussed later in this course.

The JBoss EAP installer creates an administrative user during the installation process.

If additional administrative users are required, or if the installation was NOT done using the JBoss EAP installer, then you can create new users by using the add-user.sh script. This script is present in the JBOSS_HOME/bin directory.

You can add two different types of users:

[user@host jboss-eap-7.4]$ /opt/jboss-eap-7.4/bin/add-user.sh -u admin2 -p redhat123
Added user 'admin2' to file '/opt/jboss-eap-7.4/standalone/configuration/mgmt-users.properties'
Added user 'admin2' to file '/opt/jboss-eap-7.4/domain/configuration/mgmt-users.properties'

[user@host jboss-eap-7.4]$ /opt/jboss-eap-7.4/bin/add-user.sh -a -u appuser -p apppwd123
Added user 'appuser' to file '/opt/jboss-eap-7.4/standalone/configuration/application-users.properties'
Added user 'appuser' to file '/opt/jboss-eap-7.4/domain/configuration/application-users.properties'

You do not need to restart a JBoss EAP server instance, or managed domain, when changing the user files. JBoss EAP automatically detects changes to these files. They are plain text files, and the passwords stored in them are hashed. Lines beginning with a pound sign, #, are comments.

The host controllers in a managed domain might need special users to connect to the domain controller. You can create those users by using the add-user.sh script. Later in this course you learn about these special users.