Uninstall the existing JBoss EAP instance, reinstall it using the automated installation method (myinstall.xml file), and configure the server.
| Resources | |
|---|---|
| Files |
|
| JBoss EAP 7 Administration Console URL | http://localhost:9990 |
Outcomes
You should be able to install an instance of JBoss EAP 7.
Use the following command to download the relevant lab files and ensure that JBoss EAP is not running:
[student@workstation ~]$ lab start features-review
Instructions
Another administrator installed JBoss EAP on an existing host and you need to replicate the same installation process on the workstation machine.
In this step, you have the answer file generated during the installation process.
Install JBoss EAP 7 by using the automated installer based on the following criteria:
Table 1.2. Criteria for automated installer execution
| Field | Value |
|---|---|
Admin username
|
admin
|
Admin password
|
redhat123
|
Install Path (JBOSS_HOME)
|
/opt/jboss-eap-7.4
|
The myinstall.xml.variables file and the myinstall.xml answer file are available at the /home/student/AD248/labs/features-review/ directory.
The JBoss EAP 7 installer is located at /home/student/.
Verify that the configuration from these files follows the expected characteristics.
[student@workstation ~]$sudo java -jar jboss-eap-7.4.0-installer.jar \/home/student/AD248/labs/features-review/myinstall.xmlChecking for corresponding .variables file Variables file detected: /home/student/AD248/labs/features-review/myinstall.xml.variables [ Starting automated installation ] Read pack list from xml definition. Try to add to selection [Name: Red Hat JBoss Enterprise Application Platform and Index: 0] Try to add to selection [Name: AppClient and Index: 1] Try to add to selection [Name: XMLs and XSDs and Index: 2] Try to add to selection [Name: Modules and Index: 3] Try to add to selection [Name: Welcome Content and Index: 4] Modify pack selection. Validation warning Password should have at least one non-alphanumeric symbol. [ Starting to unpack ] [ Processing package: Red Hat JBoss Enterprise Application Platform (1/5) ] [ Processing package: AppClient (2/5) ] [ Processing package: Docs (3/5) ] [ Processing package: Modules (4/5) ] [ Processing package: Welcome Content (5/5) ] [ Unpacking finished ] [ Starting processing ] Starting process Logging installation information (1/3) IzPack variable state written to /opt/jboss-eap-7.4/installation/InstallationLog.txt Starting process Adding admin user (2/3) Starting process Cleanup extraneous folders and tepmorary files (3/3) [ Processing finished ] [ Writing the uninstaller data ... ] [ Automated installation done ]
Verify that the /opt/jboss-eap-7.4 directory is created, and verify that the startup and other scripts, such as standalone.sh, domain.sh, add-user.sh, are available in the JBOSS_HOME/bin directory.
Red Hat recommends running JBoss EAP as a non-root user to prevent the access of malicious users with administrative permissions to the host.
The jboss user already exists.
Change the ownership of the /opt/jboss-eap-7.4 directory and all the files within the directory to user jboss and group jboss by using the chown -R command.
Verify the ownership change by running the following command :
[student@workstation ~]$ ls -la /opt/jboss-eap-7.4Start a JBoss EAP standalone server as the jboss user.
In a new terminal window, login as the jboss user to start the JBoss EAP 7 instance. (Hint: Use the sudo -u jboss command.)
Verify that the admin credentials work.
Log in to the JBoss EAP 7 administration console using the admin as the user, redhat123 as the password.
Shutdown the JBoss EAP 7 server by pressing Ctrl+C in the terminal window where you started EAP 7.
Open a new terminal window to verify the completion of this lab by running the following command:
[student@workstation ~]$ lab grade features-review