JBoss EAP installation structure and details
JBoss eap installation overview If you installed EAP via an installation zip file, you have the following general structure: jboss-as ??? bin ??? client ??? common ??? docs ??? icons ??? lib ??? scripts ??? server ??? all ? ??? conf ? ??? deploy ? ??? deployers ? ??? farm ? ??? lib ??? default ? ??? conf ? ??? data ? ??? deploy ? ??? deployers ? ??? lib ??? minimal ? ??? conf ? ??? deploy ? ??? deployers ? ??? lib ??? production ? ??? conf ? ??? deploy ? ??? deployers ? ??? farm ? ??? lib ??? standard ??? conf ??? deploy ??? deployers ??? lib The general directory structure above is important because patches will refer to several key points in it: $JBOSS_HOME is the top directory where jboss-as is installed. The system administrator decides where the installation home directory is. It can be anywhere on the system – for developers it's usually located in their $HOME directory; for production systems this directory will be found in /usr/local. NOTE:: RPM based installations do NOT follow this general setup. Please refer to the RPM guide for more details. JBOSSCONF refers to the sub-directory under the server directory. EAP comes prepackaged with 5 server types: al, default, minimal, production, standard. Each profile has different default settings, enabling or disabling certain features. For instance, default is a very insecure installation where as production is a locked down and little output to the terminal profile. For more information refer to . When patching, it's important to make sure that the right profile is patched. If a profile is not in use, it should be fully removed from the system; leaving a general rule that patches that changes profile content should be applied to all profiles.