Chapter 4. Launching a non-clustered JBoss EAP instance

Procedure

1. Launch the Red Hat AMI instance.

   A non-clustered instance of JBoss EAP has been configured and launched on a Red Hat AMI.

   Note
   • For complex configuration, you can either use the standalone.conf file in the JBoss EAP bin directory: /opt/rh/eap8/root/usr/share/wildfly/bin/, or you can start the JBoss EAP service and configure the server using CLI. The script can be found in the bin directory. Then, reload the configuration.
   • You must regularly run the yum -y update to apply security fixes and enhancements.

2. Start JBoss EAP using the following command:

   $ sudo systemctl start eap8-standalone

3. Stop JBoss EAP using the following command:

   $ sudo systemctl stop eap8-standalone

   Note

   If you want to bind JBoss EAP to a different IP address, add the following line in the /etc/opt/rh/eap8/wildfly/eap8-standalone.conf file on RHEL 9. The internal IP address is translated into a public IP address by EC2.

   WILDFLY_BIND=$YOUR_PRIVATE_IP_ADDRESS