WildFly Concepts: Difference between revisions
| Line 15: | Line 15: | ||
=Profile= | =Profile= | ||
A ''profile'' is a set of subsystem declarations, put together for a specific purpose. All the component subsystems of a profile cooperated in providing the functionality people expect of an application server. Only specific extensions are loaded with each profile. The profile configuration includes the subsystem declarations and detailed configuration for them. If the JBoss instance runs in standalone mode, the profiles are defined and configured in [[standalone.xml|standalone.xml]]. If the JBoss instances run in domain mode, the domain's profiles are defined and configured in [[domain.xml]]. JBoss ships with the following pre-defined profiles: | |||
* "default" packages subsystems offering default functionality (logging, security, datasources, infinispan, jpa, webservices, ee, ejb3, transactions, mail). | |||
* "full" contains all subsystems from the "default' profile plus jacorb, jaxr, messaging. | |||
* "ha" contains all subsystems from the "default' profile plus jgroups and modcluster. | |||
* "full-ha" contains all subsystems from the "full" profiles plus jgroups and modcluster. | |||
Custom profiles can be added. | |||
=Configuration History= | =Configuration History= | ||
Revision as of 20:06, 7 July 2017
Internal
Concepts
Profile
A profile is a set of subsystem declarations, put together for a specific purpose. All the component subsystems of a profile cooperated in providing the functionality people expect of an application server. Only specific extensions are loaded with each profile. The profile configuration includes the subsystem declarations and detailed configuration for them. If the JBoss instance runs in standalone mode, the profiles are defined and configured in standalone.xml. If the JBoss instances run in domain mode, the domain's profiles are defined and configured in domain.xml. JBoss ships with the following pre-defined profiles:
- "default" packages subsystems offering default functionality (logging, security, datasources, infinispan, jpa, webservices, ee, ejb3, transactions, mail).
- "full" contains all subsystems from the "default' profile plus jacorb, jaxr, messaging.
- "ha" contains all subsystems from the "default' profile plus jgroups and modcluster.
- "full-ha" contains all subsystems from the "full" profiles plus jgroups and modcluster.
Custom profiles can be added.
Configuration History
The application server maintains past versions of its configuration files. This behavior allows the operator to fall back to a certain previous configuration.
Each CLI operation increments the configuration version, and a full copy of the previous configuration is stored in $JBOSS_HOME/standalone/configuration/standalone_xml_history/current Upon reboot, the current directory is renamed to something similar to $JBOSS_HOME/standalone/configuration/standalone_xml_history/20160331-201819598 and the cycle repeats. Also see Taking and Restoring Configuration Snapshots.