HP Integrity NonStop H-Series - Manual (Page 46)

NOTE: An extension module is configured through a corresponding subsystem definition.
Table 8 (page 46) lists and describes the extensions and their corresponding subsystem
configuration. The following snippet illustrates the various subsystems contained in the domain.xml
file:
Table 8 Subsystem configuration
Subsystem Configuration Extension
“EE subsystem” (page 49) org.jboss.as.ee
“EJB3 subsystem” (page 51) org.jboss.as.ejb3
“Infinispan subsystem” (page 53) org.jboss.as.clustering.infinispan
“Web subsystem” (page 57) org.jboss.as.web
“Security subsystem” (page 55) org.jboss.as.security
“Java Persistence API subsystem” (page 63) org.jboss.as.jpa
“Naming subsystem” (page 63) org.jboss.as.naming
The JGroups extension is required to form a cluster of JBoss servers. This release
of NSASJ does not support cluster formation. JBoss provides some features
beyond what is recommended in the EJB specification, which requires the
JBoss servers in a domain to form a cluster. Providing a cluster wide singleton
and cluster wide timer service are some such features. As of this release, these
JBoss specific features are not supported on NSASJ. org.jboss.as.clustering.jgroups
“Transaction management ” (page 68) org.jboss.as.transactions
“Logging” (page 73) org.jboss.as.logging
logging.properties
This file is used by the boot logger. For more information on logging.properties file, see
“Logging properties file” (page 77) .
46 Configuring NSASJ