Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 4. Launching a non-clustered JBoss EAP instance
This chapter lists the steps to launch a non-clustered instance of JBoss EAP on a Red Hat Amazon Machine Image (AMI) created through a private AMI or public Marketplace listing.
Prerequisites
- A suitable Red Hat AMI. See Supported Red Hat AMIs for more information.
- A pre-configured Security Group that allows incoming requests on at least ports 22, 8080, and 9990.
You can connect to an EC2 instance through ssh as the ec2-user user. If you need administrative privileges, you can change to root user later. For example,
$ ssh -l ec2-user ${INSTANCE_PUBLIC_IP}
...
$ sudo su -Procedure
Launch the Red Hat AMI instance.
A non-clustered instance of JBoss EAP has been configured and launched on a Red Hat AMI.
-
For complex configuration, you can either use the
standalone.conffile in the JBoss EAPbindirectory:/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 thebindirectory. Then, reload the configuration. -
You must regularly run the
yum -y updateto apply security fixes and enhancements.
Start JBoss EAP using the following command:
$ systemctl start eap8-standalone
Stop JBoss EAP using the following command:
$ systemctl stop eap8-standalone
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
