One of the key features of JBoss EAP 6 is the modular class-loading structure.
Driven by speed and simplicity, JBoss EAP 6’s default footprint is very lightweight. JBoss provides different profiles that you can use to run your application server. Only specific extensions are loaded with each profile. You can start a default standalone server instance more or less in 3 seconds. Configurations, files, logs and related files are all found on each corresponding folders for standalone and domain mode.
In order to understand JBoss EAP 6 architecture more, it is very important that we get a clear understanding extensions, subsystems and profiles.
Extensions
In simple terms extensions are modules(a particular set of capabilities) that extends the core capabilities of EAP. Extensions allow administrators to turn on or off modules such as clustering, logging and security depending on ones needs.
An extension is added using the <extension> tag in the beginning of the EAP configuration file. (standalone.xml or domain.xml)
Subsystems
Subsystems makes the extensions usable. It defines how it will be used and configured. It is also defined in the EAP configuration file (standalone.xml or domain.xml) using the <subsystem> tag under a profile.
For every extension added in an EAP instance, the capabilities and attributes of that extension are configured with the <subsystem> element. If no setting is required then you may simply leave the element empty. (e.g. <subsystem xmlns=”urn:jboss:domain:ee:1.0″/>)
Profiles
Profile is a set of subsystems combined for different purposes. For domain-mode, four profiles are defined by default. (default, ha, full, full-ha) For standalone-mode, an un-named profile is set.
Default Profile
Includes the ff. subsystems – logging, configadmin, security, datasources, inifinispan, jpa, weld, webservices, ee, ejb3, transactions, mail
Full Profile
All subsystems from default profile plus – cmp, jacorb, jaxr, messaging.
HA Profile
All subsystems from default profile plus – jgroups, modcluster
Full-HA Profile
All subsystems from full profile plus – jgroups, modcluster
Driven by speed and simplicity, JBoss EAP 6’s default footprint is very lightweight. JBoss provides different profiles that you can use to run your application server. Only specific extensions are loaded with each profile. You can start a default standalone server instance more or less in 3 seconds. Configurations, files, logs and related files are all found on each corresponding folders for standalone and domain mode.
In order to understand JBoss EAP 6 architecture more, it is very important that we get a clear understanding extensions, subsystems and profiles.
Extensions
In simple terms extensions are modules(a particular set of capabilities) that extends the core capabilities of EAP. Extensions allow administrators to turn on or off modules such as clustering, logging and security depending on ones needs.
An extension is added using the <extension> tag in the beginning of the EAP configuration file. (standalone.xml or domain.xml)
Subsystems
Subsystems makes the extensions usable. It defines how it will be used and configured. It is also defined in the EAP configuration file (standalone.xml or domain.xml) using the <subsystem> tag under a profile.
For every extension added in an EAP instance, the capabilities and attributes of that extension are configured with the <subsystem> element. If no setting is required then you may simply leave the element empty. (e.g. <subsystem xmlns=”urn:jboss:domain:ee:1.0″/>)
Profiles
Profile is a set of subsystems combined for different purposes. For domain-mode, four profiles are defined by default. (default, ha, full, full-ha) For standalone-mode, an un-named profile is set.
Default Profile
Includes the ff. subsystems – logging, configadmin, security, datasources, inifinispan, jpa, weld, webservices, ee, ejb3, transactions, mail
Full Profile
All subsystems from default profile plus – cmp, jacorb, jaxr, messaging.
HA Profile
All subsystems from default profile plus – jgroups, modcluster
Full-HA Profile
All subsystems from full profile plus – jgroups, modcluster
No comments:
Post a Comment