[
"<div class=\"preview-content\">\n    <h1>Access Control</h1>\n    The access control definitions grant or restrict access to the management operations.\n\n    <h2>Common Configuration Tasks</h2>\n    <ul>\n        <li>Add users and groups and assign roles to them.</li>\n        <li>Define custom roles scoped to hosts or server groups.</li>\n    </ul>\n</div>",
"<h1>Administrator</h1><p>The Administrator role has unrestricted access to all resources and operations on the server except the audit logging system. The Administrator role has access to sensitive data and operations. This role can also configure the access control system. The Administrator role is only required when handling sensitive data or configuring users and roles. Administrators cannot access the audit logging system and cannot change themselves to the Auditor or SuperUser role.</p>",
"<h1>Auditor</h1><p>The Auditor role has all the permissions of the Monitor role and can also view (but not modify) sensitive data, and has full access to the audit logging system. The Auditor role is the only role other than SuperUser that can access the audit logging system. Auditors cannot modify sensitive data or resources. Only read access is permitted.</p>",
"<div class='preview-content'>\n    <h1>Batch Subsystem</h1>\n    The Batch subsystem allows to configure the settings for bulk-oriented, non-interactive, background execution of jobs.\n</div>",
"<div class='preview-content'>\n    <h1>Content Repository</h1>\n    <p>All deployment artifacts uploaded to the domain.</p>\n</div>",
"<div class='preview-content'><h1>Datasources</h1>The Datasource subsystem allows you to create and configure datasources and manage JDBC database drivers.</div>",
"<h1>Deployer</h1><p>The Deployer role has the same permissions as the Monitor, but can modify configuration and state for deployments and any other resource type enabled as an application resource.</p>",
"<div class=\"preview-content\">\n\n    <h1>Deployment</h1>\n    A deployment represents anything that can be deployed (e.g. an application such as EJB-JAR, WAR, EAR, any kind of standard archive such as RAR or JBoss-specific deployment) into a server.\n\n    <h2>Common Configuration Tasks</h2>\n    Deploy and manage applications and other EE resources.\n</div>",
"<div class='preview-content'><h1>EE</h1>\"The EE subsystem allows you to configure common functionality in the Java EE platform, such as defining global modules, enabling descriptor-based property replacement, and configuring default bindings.\"</div>",
"<div class='preview-content'><h1>EJB 3</h1>\"The EJB3 sybsystem allows you to configure Enterprise JavaBeans (EJB) including Session, Message-Driven, and Entity beans. \"</div>",
"<div class=\"preview-content\">\n\n    <h1>Groups</h1>\n    <p>The list of known groups.</p>\n\n</div>",
"<div class='preview-content'><h1>HTTP</h1>\"The HTTP subsystem allows you to configure the HTTP and AJP connectors.\"</div>",
"\n<div class=\"preview-content\">\n\n    <h1>Interfaces</h1>\n    A logical name for a network interface/IP address/host name to which sockets can be bound. The domain.xml, host.xml and standalone.xml configurations all include a section where interfaces can be declared. Other sections of the configuration can then reference those interfaces by their logical name, rather than having to include the full details of the interface (which may vary on different machines).\n    <p/>\n    An interface configuration includes the logical name of the interface as well as information specifying the criteria to use for resolving the actual physical address to use.\n    <p/>\n    See Interfaces and ports for further details.\n\n</div>",
"<div class='preview-content'><h1>JacORB</h1>The JacORB subsystem allows you to enable configure the CORBA services for JTS transactions and other ORB services.</div>",
"<div class='preview-content'><h1>JCA</h1>The JCA (Java EE Connector Architecture) subsystem allows you to configure the general settings for the JCA container and resource adapter deployments.</div>",
"<div class='preview-content'><h1>JMX</h1>\"The JMX (Java Management Extensions) subsystem allows you to configure remote connectors, the model controller in the MBeanServer, and management audit logging. \"</div>",
"<div class='preview-content'><h1>JPA</h1>\"The JPA (Java Persistence API)  subsystem manages the JPA 2.0 container-managed requirements and allows you to deploy persistent unit definitions, annotations, and desriptors.\"</div>",
"<div class='preview-content'><h1>Logging</h1>\"The Logging subsystem, which also supports several third party logging frameworks, allows you to configure log categories and handlers for the server and for application deployments.\"</div>",
"<div class='preview-content'><h1>Mail</h1>The Mail subsystem allows you to configure standard mail server attributes and define custom mail transports.</div>",
"<div class='preview-content'>\n    <h1>Mail Sessions</h1>\n    The Mail subsystem allows you to configure standard mail server attributes and define custom mail transports.\n</div>",
"<h1>Maintainer</h1><p>The Maintainer role has access to view and modify runtime state and all configuration except sensitive data and operations. The Maintainer role is the general purpose role that doesn’t have access to sensitive data and operation. The Maintainer role allows users to be granted almost complete access to administer the server without giving those users access to passwords and other sensitive information. Maintainers cannot access sensitive data or operations.</p>",
"<h1>Monitor</h1><p>Users of the Monitor role have the fewest permissions and can only read the current configuration and state of the server. This role is intended for users who need to track and report on the performance of the server. Monitors cannot modify server configuration nor can they access sensitive data or operations.</p>",
"<h1>Operator</h1><p>The Operator role extends the Monitor role by adding the ability to modify the runtime state of the server. This means that Operators can reload and shutdown the server as well as pause and resume JMS destinations. The Operator role is ideal for users who are responsible for the physical or virtual hosts of the application server so they can ensure that servers can be shutdown and restarted corrected when needed. Operators cannot modify server configuration or access sensitive data or operations.</p>",
"\n<div class=\"preview-content\">\n\n    <h1>Paths</h1>\n    A logical name for a filesystem path. The domain.xml, host.xml and standalone.xml configurations all include a section where paths can be declared.\n    Other sections of the configuration can then reference those paths by their logical name, rather than having to include the full details of the path (which may vary on different machines). For example, the logging subsystem configuration includes a reference to the \\\"jboss.server.log.dir\\\" path that points to the server's \\\"log\\\" directory.\n\n</div>",
"<div class=\"preview-content\">\n\n    <h1>Configuration</h1>\n    The overall system configuration. Gives access to the server configuration.\n\n    <h2>Common Configuration Tasks</h2>\n    Configure subsystems, interfaces and socket bindings.\n\n    <h2>Related Links</h2>\n    <ul>\n        <li><a href=\"#standalone-runtime\">Server Runtime</a></li>\n    </ul>\n</div>",
"<div class=\"preview-content\">\n\n    <h1>Configuration</h1>\n    The overall system configuration. Gives access to the main configuration profiles that can be applied to server groups.\n\n    <h2>Common Configuration Tasks</h2>\n    Configure subsystems, interfaces and socket bindings.\n\n    <h2>Related Links</h2>\n    <ul>\n        <li><a href=\"#domain-runtime\">Domain Runtime: Server & Server Groups</a></li>\n    </ul>\n</div>",
"\n<div class=\"preview-content\">\n\n    <h1>Configuration Profile</h1>\n    A profile is a named set of subsystem configurations. A subsystem is an added set of capabilities added to the core server by an extension. A subsystem provides servlet handling capabilities; a subsystem provides an EJB container; a subsystem provides JTA, etc. A profile is a named list of subsystems, along with the details of each subsystem's configuration. A profile with a large number of subsystems results in a server with a large set of capabilities. A profile with a small, focused set of subsystems will have fewer capabilities but a smaller footprint.\n</div>",
"\n<div class=\"preview-content\">\n\n    <h1>System Properties</h1>\n    These properties are available throughout the configuration. The Boot-Time flag specifies if a property should be passed into the JVM start (-Dproperty=value)\n</div>",
"<div class='preview-content'><h1>Resource Adapter</h1>The Resource Adapter subsystem allows you to configure and deploy resource adapters.</div>",
"<div class=\"preview-content\">\n\n    <h1>Roles</h1>\n    <p>The list of known roles.</p>\n\n</div>",
"<div class=\"preview-content\">\n\n    <h1>Runtime</h1>\n    Runtime services, like log files, JVM metrics and subsystem specific runtime data.\n\n    <h2>Common Configuration Tasks</h2>\n    <ul>\n        <li>View and monitor metrics</li>\n        <li>Inspect server state</li>\n        <li>Lookup application related runtime service names</li>\n    </ul>\n\n</div>",
"<div class='preview-content'><h1>Security Subsystem</h1>The Security subsystem allows you to configure settings related to deep copy subjects.</div>",
"<div class='preview-content'><h1>Security Domains</h1>The Security Domains subsytem allows you to configure settings related to registered security domains. You can configure the attributes and module options.</div>",
"<div class=\"preview-content\"><h2>Server Groups</h2>A server group is set of server instances that will be managed and configured as one. In a managed domain each application server instance is a member of a server group. (Even if the group only has a single server, the server is still a member of a group.) It is the responsibility of the Domain Controller and the Host Controllers to ensure that all servers in a server group have a consistent configuration. They should all be configured with the same profile and they should have the same deployment content deployed.</div>",
"<div class='preview-content'><h1>Servlet/HTTP</h1>The Servlet subsystem allows you to configure the servlet/jsp configuration of the web subsystem.  </div>",
"\n<div class=\"preview-content\">\n\n    <h1>Socket Bindings</h1>\n    Socket bindings and socket binding groups allow you to define network\n    ports and their relationship to the networking interfaces required for\n    a configuration profile.\n\n</div>",
"<h1>SuperUser</h1><p>The SuperUser role has no restrictions and has complete access to all resources and operations of the server including the audit logging system. This role is equivalent to the administrator users of earlier versions. If RBAC is disabled, all management users have permissions equivalent to the SuperUser role.</p>",
"<div class='preview-content'><h1>Threads</h1>The Threads subsystem allows you to create and configure thread pools.</div>",
"<div class='preview-content'><h1>Transactions</h1>\"The Transaction subsystem allows you to configure Transaction Manager (TM) options such as statistics, timeout values, transaction logging, and whether to use Java Transaction Service (JTS).\"</div>",
"<div class='preview-content'>\n    <h1>Unassigned Content</h1>\n    <p>Uploaded deployment artifacts which are not assigned to any server group.</p>\n</div>",
"<div class=\"preview-content\">\n\n    <h1>Users</h1>\n    <p>The list of known users.</p>\n\n</div>",
"<div class='preview-content'><h1>Web Services</h1>\"The Web Services subsystem allows you to configure the host name, ports, and WSDL address for the Web Services provider.\"</div>"]