anchor.diff:          <role-name>speaker</role-name>
           <group-name>speakers</group-name>
       </security-role-mapping>
  -
  +----
   is drastically simplified in the `app.properties` file:
   
  +[source,xml]
  +----
       admins=admin,leader,helper,member,partner
       leaders=leader,helper,member,partner
       members=member
       helpers=helper,member
       partners=partner
  +----
   
   where groups are listed on the left of the equal operator and roles are listed on the right. In the example above, users in the group `admins` fulfill the role of `admin`, `leader`, `helper`, `member` and `partner`.
   
   To finish the configuration, add the file `jboss-web.xml` in the folder WEB-INF of your web module with the following content: 
   
  +[source,xml]
  +----
       <?xml version="1.0" encoding="UTF-8"?>
       <jboss-web>
   	      <security-domain>app</security-domain>
       </jboss-web>
  +----
   
   If you don't use a database as a security repository, you can find more details about available login modules for WildFly in its https://docs.jboss.org/author/display/WFLY8/Security+subsystem+configuration[online documentation].
   
  
positive.code: 
  The command returns `{"outcome" => "success"}` in case of success. This command resulted in the following part in the configuration file:
  
      <datasources>
          {...}
          <drivers>
  
negative.code: 
  The resulting part made by the console/command in the configuration file are:
  
  [source,xml]
  ----
      <datasources>
          {...}
          <datasource jndi-name="java:/jdbc/AppDS" pool-name="AppDS" enabled="true" use-java-context="true">
  