红帽全球峰会此内容没有您所选择的语言版本。
4.2. Standard Server Profiles
The JBoss Enterprise Application Platform ships with six server profiles. You can choose which configuration to start by passing the
-c parameter to the server startup script. For instance, the run.sh -c all command starts the server in the all profile.
Each profile is contained in a directory named
install_directory/server/[profile name]/. You can look into each server profile's directory to see the services, applications, and libraries included in the profile.
Note
The exact contents of the
server/[profile name] directory depends on the profile service implementation and is subject to change as the management layer and embedded server evolve.
- all
- Default profile loaded when
run.shis executed without the-cparameter. The profile provides clustering support and other enterprise extensions. - production
- The production profile is based on the
allprofile and provides configuration optimized for production environments. - minimal
- Starts the core server container without any of the enterprise services. Use the
minimalprofile as a base to build a customized version of JBoss Enterprise Application Platform that only contains the services you need. - default
- The
defaultprofile is the mostly common used profile for application developers. It supports the standard Java EE 5.0 programming APIs (e.g., Annotations, JPA, and EJB3).Note
Thedefaultprofile is a misnomer; it is not loaded automatically if you do not specify a profile at start up. Theallprofile is loaded when you do not specify a profile at startup. - standard
- The standard profile is the profile that has been tested for Java EE compliance. The major differences with the existing configurations is that call-by-value and deployment isolation are enabled by default, along with support for
rmiiiopandjuddi(taken from the all config). - web
- The web profile is an experimental, lightweight configuration created around JBoss Web that will follow the developments of the Java EE 6 web profile. Except for the
servlet/jspcontainer, it provides support for JTA/JCA and JPA. It also limits itself to allowing access to the server only through the http port. Please note that this configuration is not Java EE certified and will most likely change in the following releases.
The detailed services and APIs supported in each of those profiles will be discussed throughout.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}