[
"<div class=\"preview-content\">\n    <h1>Access Control</h1>\n    The access control definitions grant or restrict access to management operations.\n\n    <h2>Common Configuration Tasks</h2>\n    <ul>\n        <li>Add users and groups.</li>\n        <li>Assign roles to users and groups.</li>\n        <li>Define custom roles scoped to hosts or server groups.</li>\n    </ul>\n</div>\n",
"<div class='preview-content'>\n    <h1>Messaging (ActiveMQ)</h1>\n    The Messaging (ActiveMQ) subsystem allows you to configure connections, destinations, clustering, and general settings for messaging providers.\n</div>\n",
"<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 change their permissions to Auditor or SuperUser.</p>\n",
"<div class=\"preview-content\">\n\n    <h2>Assignment</h2>\n    <p>A user is considered to be assigned to a role if:</p>\n    <ol>\n        <li>The user is:\n            <ul>\n                <li>listed as a user to be included in the role, or</li>\n                <li>a member of a group that is listed to be included in the role.</li>\n            </ul>\n        </li>\n        <li>The user is not:\n            <ul>\n                <li>listed as a user to exclude from the role, or</li>\n                <li>a member of a group that is listed to be excluded from the role.</li>\n            </ul>\n        </li>\n    </ol>\n    <p>Exclusions take priority over inclusions.</p>\n</div>",
"<h1>Auditor</h1><p>The Auditor role has all the permissions of the Monitor role and can also view, but not modify, sensitive data. The Auditor role is the only role other than SuperUser that can access the audit logging system. Only read access is permitted.</p>\n",
"<div class='preview-content'>\n    <h1>Batch Subsystem</h1>\n    The Batch subsystem allows you to configure an environment for running batch applications.\n</div>\n",
"<div class='preview-content'><h1>Infinispan</h1>The Infinispan subsystem allows you to configure the local, invalidation, distributed, and replicated caches for Infinispan cache containers.</div>\n",
"<div class='preview-content'>\n    <h1>Content Repository</h1>\n    <p>Manage all deployments that have been uploaded to the domain.</p>\n    <p>Upload a new deployment or create an unmanaged deployment. Assign deployments to server groups or remove deployments.</p>\n</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'><h1>Deployment Scanners</h1>The Deployment Scanners subsystem allows you to configure deployment scanners that monitor certain locations for applications to deploy.</div>\n",
"<div class=\"preview-content\">\n\n    <h1>Deployment</h1>\n    A deployment is anything that can be deployed to a server, such as WAR, EAR, and EJB JAR applications, standard archives, or JBoss-specific deployments.\n\n    <h2>Common Configuration Tasks</h2>\n    Deploy and manage applications and other Java EE resources.\n</div>\n",
"<div class='preview-content'><h1>Datasources</h1>The Datasource subsystem allows you to create and configure datasources.</div>\n",
"<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>\n",
"<div class='preview-content'><h1>EJB 3</h1>The EJB 3 subsystem allows you to configure Enterprise JavaBeans (EJBs) including session, message-driven, and entity beans. </div>\n",
"<div class='preview-content'>\n    <h1>Factory</h1>\n    Elytron settings for factories.\n</div>\n",
"<div class='preview-content'>\n    <h1>Mapper / Decoder</h1>\n    Elytron settings for\n    <ul>\n        <li>Role mappers</li>\n        <li>Permission mappers</li>\n        <li>Principal decoders</li>\n        <li>Role decoders</li>\n    </ul>\n</div>\n",
"<div class='preview-content'>\n    <h1>Security Realm</h1>\n    Elytron settings for security realms and authentication.\n</div>\n",
"<div class='preview-content'>\n    <h1>Other settings</h1>\n    Elytron settings for:\n    <ul>\n        <li>Key stores</li>\n        <li>Credential stores</li>\n        <li>Filtering key stores</li>\n        <li>Ldap key stores</li>\n        <li>Key managers</li>\n        <li>Server SSL contexts</li>\n        <li>Client SSL contexts</li>\n        <li>Trust managers</li>\n        <li>Security domains</li>\n        <li>Security properties</li>\n        <li>Transformers</li>\n        <li>Directory contexts (LDAP)</li>\n        <li>Provider Loader</li>\n    </ul>\n</div>\n",
"<div class=\"preview-content\">\n\n    <h1>Groups</h1>\n    <p>Manage groups and the roles assigned to each group.</p>\n\n</div>",
"<div class='preview-content'><h1>HTTP</h1>General configuration for the Undertow subsystem.</div>\n",
"<div class='preview-content'>\n    <h1>IIOP OpenJDK</h1>\n    The IIOP subsystem allows you to configure CORBA services for JTS transactions and other ORB services.\n</div>",
"<div class=\"preview-content\">\n    <h1>Interfaces</h1>\n    <p>An interface is a logical name for a network interface, IP address, or host name to which sockets can be bound. Other areas of the configuration can then reference the interface by its logical name instead of providing the full details, which may vary on different machines. An interface configuration also specifies criteria for resolving the actual physical address to use.</p>\n</div>\n",
"<div class='preview-content'>\n    <h1>IO</h1>\n    The IO subsystem allows you to define workers and buffer pools to be used by other subsystems.\n</div>\n",
"<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 Java EE Connector Architecture (JCA) subsystem allows you to configure the general settings for the JCA container and resource adapter deployments.</div>\n",
"<div class='preview-content'>\n    <h1>JGroups</h1>\n    The JGroups subsystem allows you to configure the protocol stacks and mechanisms for how servers in a cluster communicate.\n</div>\n",
"<div class='preview-content'>\n    <h1>JMS Bridge</h1>\n    <p>A JMS bridge consumes messages from a source JMS destination and sends them to a target JMS destination, typically on a different server.</p>\n\n    <p>The bridge can also be used to bridge messages from other non-Artemis JMS servers, as long as they are JMS 1.1 compliant.</p>\n</div>\n",
"<div class='preview-content'><h1>JMX</h1>The Java Management Extensions (JMX) subsystem allows you to configure JMX access and settings. </div>\n",
"<div class='preview-content'><h1>JPA</h1>The Java Persistence API (JPA) subsystem manages the JPA 2.1 container-managed requirements and allows you to deploy persistent unit definitions, annotations, and descriptors.</div>\n",
"<div class='preview-content'>\n    <h1>Servlet / JSP</h1>\n    Configuration for JSP and servlet container settings.\n</div>\n",
"<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>\n",
"<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>\n",
"<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 does not have access to sensitive data and operations. 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.</p>\n",
"<div class=\"preview-content\">\n\n    <h2>Membership</h2>\n    <p>A user is considered to be assigned to a role if:</p>\n    <ol>\n        <li>The user is:\n            <ul>\n                <li>listed as a user to be included in the role, or</li>\n                <li>a member of a group that is listed to be included in the role.</li>\n            </ul>\n        </li>\n        <li>The user is not:\n            <ul>\n                <li>listed as a user to exclude from the role, or</li>\n                <li>a member of a group that is listed to be excluded from the role.</li>\n            </ul>\n        </li>\n    </ol>\n    <p>Exclusions take priority over inclusions.</p>\n</div>",
"<div class=\"preview-content\">\n    <h1>Messaging Provider</h1>\n    <p>A messaging provider is an ActiveMQ server instance.</p>\n\n    <h3>Queues / Topics</h3>\n    <p>Create queues and topics used by this messaging provider.</p>\n\n    <h3>Connections</h3>\n    <p>Manage acceptors, which define how connections can be made to the messaging provider.</p>\n    <p>Create bridges, which consume messages from a source queue, and forward them to a target address, typically on a different server.</p>\n\n    <h3>Clustering</h3>\n    <p>Define broadcast and discovery groups, which control how connectors are handled and distributed by this provider.</p>\n    <p>Manage cluster connections to load balance between nodes of a cluster.</p>\n\n    <h3>Provider settings</h3>\n    <p>Configure the settings of this messaging provider.</p>\n</div>\n",
"<div class='preview-content'>\n    <h1>ModCluster</h1>\n    The ModCluster subsystem allows you to configure the server-side mod_cluster worker node.\n</div>\n",
"<h1>Monitor</h1><p>The Monitor role has 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>\n",
"<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 shut down 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 shut down and restarted correctly when needed. Operators cannot modify server configuration nor access sensitive data or operations.</p>\n",
"\n<div class=\"preview-content\">\n\n    <h1>Paths</h1>\n    A path is a logical name for a file system path. Other areas of the configuration can then reference the path using the logical name instead of the full path, which may vary on different machines. There are several predefined paths in use by the default configuration, such as the <span style=\"font-family: monospace\">jboss.server.log.dir</span> path that defines the directory for the server log.\n</div>\n",
"<div class='preview-content'><h1>PicketLink Federations</h1>\n    <p>The PicketLink subsystem allows you to configure and deploy identity providers (IDP) and service providers (SP), which are grouped together in a federation.</p>\n    <p>A federation can be understood as a circle of trust from which applications share common configurations, such as certificates and SAML-specific configurations. Each participating domain is trusted to accurately document the processes used to identify a user, the type of authentication system used, and any policies associated with the resulting authentication credentials.</p>\n    <p>Each federation has one IDP and many SPs.</p>\n</div>\n",
"<div class=\"preview-content\">\n\n    <h1>Configuration</h1>\n  <!--  The overall system configuration. Gives access to the server configuration.-->\n\n    The overall system and 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>\n",
"<div class=\"preview-content\">\n\n    <h1>Configuration</h1>\n    The overall system configuration, including collections of subsystem configurations known as profiles.\n\n    <h2>Common Configuration Tasks</h2>\n    Configure profiles, subsystems, interfaces, and socket bindings.\n\n    <h2>Related Links</h2>\n    <ul>\n        <li><a href=\"#hosts\">Domain Runtime: Servers and Server Groups</a></li>\n    </ul>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>Profiles</h1>\n    <p>A profile is a named collection of subsystem configurations. A subsystem is a set of capabilities that extends the core functionality of the server, such as messaging, logging, and application security. A managed domain can define many profiles for use by the servers in the domain. </p>\n</div>\n",
"\n<div class=\"preview-content\">\n\n    <h1>System Properties</h1>\n    These properties are available throughout the configuration. In a managed domain, the Boot-Time flag specifies whether a property should be passed in to the JVM when server processes are started (-Dproperty=value).\n\n</div>\n",
"<div class='preview-content'><h1>Resource Adapters</h1>The Resource Adapters subsystem allows you to configure and deploy resource adapters.</div>\n",
"<div class='preview-content'>\n    <h1>Remoting</h1>\n    The Remoting subsystem allows you to configure settings for inbound and outbound connections for local and remote services.\n</div>\n",
"<div class=\"preview-content\">\n\n    <h1>Roles</h1>\n    <p>Manage role permissions and membership lists.</p>\n\n</div>",
"<div class=\"preview-content\">\n    <h1>Data Source Metrics</h1>\n    <p>Datasources runtime metrics. If no metrics are shown, you may need to enable statistics for the Datasources subsystem in the 'Configuration' section.</p>\n</div>\n",
"<div class=\"preview-content\">\n\n    <h1>Runtime</h1>\n    <p>Manage hosts, server groups, and servers. View and monitor runtime services, such as log files, JVM metrics, and subsystem-specific runtime data.</p>\n\n    <h2>Common Configuration Tasks</h2>\n    <ul>\n        <li>Create and configure server groups.</li>\n        <li>Create and assign servers to server groups.</li>\n        <li>View and monitor metrics.</li>\n        <li>Inspect server state.</li>\n        <li>Look up application-related runtime service names.</li>\n    </ul>\n</div>\n",
"<div class=\"preview-content\">\n\n    <h1>Runtime</h1>\n    <p>View and monitor runtime services, such as log files, JVM metrics, and subsystem-specific runtime data.</p>\n\n    <h2>Common Configuration Tasks</h2>\n    <ul>\n        <li>View and monitor metrics.</li>\n        <li>Inspect server state.</li>\n        <li>Look up application-related runtime service names.</li>\n    </ul>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>Host Configuration</h1>\n    <p>A host controller is a physical or virtual host that interacts with the central domain controller to configure and manage the application server insatnces running on its host.</p>\n    <h2>Common Configuration Tasks</h2>\n    <ul>\n      <li>Configure network interfaces, JVM settings, and other properties for this host.</li>\n      <li>Create and manage server instances for this host.</li>\n      <li>View server log files.</li>\n    </ul>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>Hosts</h1>\n    <p>A managed domain consists of host controllers, which are physical or virtual hosts that interact with the central domain controller to manage the application server instances running on its host. One host controller is configured to act as the central domain controller. Each host controller can have multiple server groups.</p>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>HTTP Server</h1>\n    <p>Configuration for HTTP servers. Select a server to view its settings. If no metrics are shown, you might need to enable statistics in the 'Configuration' section.</p>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>Server Group</h1>\n    <p>A server group is a set of server instances that will be configured and managed as one. In a managed domain, all server instances are members of a server group. All server instances within a server group use the same profile and have the same deployment content.</p>\n    <h2>Common Configuration Tasks</h2>\n    <ul>\n      <li>Add new server groups.</li>\n      <li>Create and assign servers to server groups.</li>\n      <li>Start, stop, and reload servers.</li>\n      <li>View server log files.</li>\n    </ul>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>Server Groups</h1>\n    <p>A server group is set of server instances that will be configured and managed as one. In a managed domain, every application server instance is a member of a server group, even if there is only a single server in a server group.</p>\n    <p>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. All server instances use the same profile and have the same deployment content.</p>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>Transaction Metrics</h1>\n    <p>The current state of the transaction subsystem. If no metrics are shown, you may need to enable statistics for the Transaction subsystem in the 'Configuration' section.</p>\n</div>\n",
"<div class=\"preview-content\">\n    <h1>Web Service Endpoints</h1>\n    <p>List of web service endpoints, which must be deployed as regular applications. If no metrics are shown, you may need to enable statistics for the Web Services subsystem in the 'Configuration' section.</p>\n</div>\n",
"<div class='preview-content'><h1>Security Subsystem</h1>The Security subsystem provides the infrastructure for securing applications. Security domains can be configured to expose authentication, authorization, ACL, audit, mapping, and identity trust capabilities.</div>",
"<div class='preview-content'><h1>Security</h1>The Security subsystem allows you to create and configure  security domains for application security.</div>\n",
"<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'>\n    <h1>Server Groups</h1>\n    <p>Manage deployments that have been assigned to one or more server groups.</p>\n    <p>Upload a new deployment, create an unmanaged deployment, or choose a deployment from the content repository. Enable or unassign deployments.</p>\n</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",
"\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 and sensitive data. 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>\n",
"<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 Transactions subsystem allows you to configure transaction manager options, such as timeout values, transaction logging, statistics collection, and whether to use Java Transaction Service (JTS).</div>\n",
"<div class='preview-content'>\n    <h1>Unassigned Content</h1>\n    <p>Manage deployments that are not assigned to any server group.</p>\n    <p>Assign deployments to server groups or remove deployments. Deployments that have been assigned to one or more server group can be found in the Server Groups section.</p>\n</div>\n",
"<div class='preview-content'>\n    <h1>Filters</h1>\n    Configuration for Undertow filters to filter and modify requests.\n</div>\n",
"<div class='preview-content'>\n    <h1>Undertow</h1>\n    The Undertow (Web/HTTP) subsystem allows you to configure the web server and servlet container settings.\n</div>\n",
"<div class=\"preview-content\">\n\n    <h1>Users</h1>\n    <p>Manage users and the roles assigned to each user.</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>\n"]