Chapter 1. Introduction
A JBoss EAP installation is optimized by default. However, configurations to your environment, applications, and use of JBoss EAP subsystems can impact performance, meaning additional configuration might be needed.
This guide provides optimization recommendations for common JBoss EAP use cases, as well as instructions for monitoring performance and diagnosing performance issues.
You should stress test and verify all performance configuration changes under anticipated conditions in a development or testing environment prior to deploying them to production.
1.1. About the Use of EAP_HOME in this Document
In this document, the variable EAP_HOME is used to denote the path to the JBoss EAP installation. Replace this variable with the actual path to your JBoss EAP installation.
-
If you installed JBoss EAP using the ZIP install method, the install directory is the
jboss-eap-7.3directory where you extracted the ZIP archive. -
If you installed JBoss EAP using the RPM install method, the install directory is
/opt/rh/eap7/root/usr/share/wildfly/. If you used the installer to install JBoss EAP, the default path for
EAP_HOMEis${user.home}/EAP-7.3.0:-
For Red Hat Enterprise Linux and Solaris:
/home/USER_NAME/EAP-7.3.0/ -
For Microsoft Windows:
C:\Users\USER_NAME\EAP-7.3.0\
-
For Red Hat Enterprise Linux and Solaris:
If you used the Red Hat CodeReady Studio installer to install and configure the JBoss EAP server, the default path for
EAP_HOMEis${user.home}/devstudio/runtimes/jboss-eap:-
For Red Hat Enterprise Linux:
/home/USER_NAME/devstudio/runtimes/jboss-eap/ -
For Microsoft Windows:
C:\Users\USER_NAME\devstudio\runtimes\jboss-eaporC:\Documents and Settings\USER_NAME\devstudio\runtimes\jboss-eap\
-
For Red Hat Enterprise Linux:
EAP_HOME is not an environment variable. JBOSS_HOME is the environment variable used in scripts.
