by Bruce Wolfe (Red Hat)
When planning your installation of JBoss EAP 6, you have three choices; ZIP, JAR or RPM. The JAR based installer is, arguably, the best and most flexible option because it will generate an answer file that can be used for silent, repeatable installs; great if you have to install JBoss on multiple servers (e.g. clustering). Using the answer file, repeat the install with:
$ java -jar jboss-eap-installer-<version>.jar <answer_file>.xml
In a production environment, it is likely that you will need to consider future upgrades to EAP core. The default directory layout works well for developers and simple use-cases, however it can make management and upgrades difficult. Ideally, separating the EAP core from the configuration and deployment directory is the minimum.
Many organisations operate central log servers, consider changing the log directory. Also, if you are adding your own module files, then using a module path allows you to keep your module files separate from the shipping modules.
Use any, or all of the following options to minimise upgrade issues; start-up option listed first, followed by the environment variable equivalent.
A path containing root directories used to hold modules.
Server Base Directory
The path to the Server base directory.
Server Config Directory
The path to the Server configuration directory.
Server Log Directory
The path to the Server log directory.
Either modify your start script with the required start-up options or add the required environment variables.
In the all-new JBoss Application Administration II (JB348) course, students will learn more about installation, management, clustering, troubleshooting, and much more.
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.