WildFly Concepts: Difference between revisions
No edit summary |
|||
| (31 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
* [[WildFly#Subjects|WildFly]] | * [[WildFly#Subjects|WildFly]] | ||
= | =Concepts= | ||
* [[WildFly Networking Concepts|Networking]] | |||
* [[WildFly Deployment Concepts|Deployments]] | |||
* [[WildFly Security Concepts|Security]] | |||
* [[WildFly Domain Mode Concepts|Domain Mode]] | |||
* [[WildFly and JMX]] | |||
* [[Remoting WildFly Subsystem Concepts|Remoting]] | |||
* [[WildFly System Properties|System Properties]] | |||
* [[WildFly Paths#Overview|Paths]] | |||
= | =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 [[WildFly_Domain_Mode_Concepts#Managed_Domain|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. | |||
If an attribute that is part of a profile used by a domain [[WildFly_Domain_Mode_Concepts#Server_Group|server group]] is changed with a CLI command, the change propagates to all servers associated with the server group, on their corresponding remote hosts. | |||
=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 <tt>$JBOSS_HOME/standalone/configuration/standalone_xml_history/current</tt> Upon reboot, the <tt>current</tt> directory is renamed to something similar to <tt>$JBOSS_HOME/standalone/configuration/standalone_xml_history/20160331-201819598</tt> and the cycle repeats. Also see [[WildFly_CLI_-_Taking_and_Restoring_Configuration_Snapshots|Taking and Restoring Configuration Snapshots]]. | |||
Latest revision as of 20:12, 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.
If an attribute that is part of a profile used by a domain server group is changed with a CLI command, the change propagates to all servers associated with the server group, on their corresponding remote hosts.
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.