anchor.diff:  . Access Admin Console at http://localhost:9090, show the error message.
   . Create user in management realm using add-user.sh, use ``admin'' as user and password.
   . Reload the Admin Console and show that login now works.
  -. Click on Administration tab and explain Access Control Providers.
  +. Click on `Administration' tab and explain Access Control Providers. WildFly 8 comes with two access control providers:
  +.. `simple' provider, the default one, gives all privileges to any authenticated administrator. This provides compatibility with older releases.
  +.. `rbac' provider allows you to setup configuration that will map users to different roles.
   . Change access control provider by giving the following command interactively on `jboss-cli`:
   +
   [source,text]
  
positive.code: ----
  +
  . Hmm, Admin Console is not accessible now. Restarting the server also did not help, debugging ...
  
  == Clustering + Session failover
  
  
negative.code: 
  [[deployment]]
  == Deployment
  === jboss-cli
  
  WildFly comes with a Command Line Interface management tool for a standalone server or a managed domain. This script is in the `bin` directory of WildFly distrbution and can be invoked by calling `jboss-cli.sh` for Mac/Linux based systems or `jboss-cli.bat` for Windows. It allows a user to connect to a standalone server or domain controller and execute management operations available through the management model.
  
  . Start a WildFly standalone server, if not already running, using the following command:
  +
  [source, text]
  ----
  standalone.sh
  ----
  +
  . Use `jboss-cli' to connect with this instance by giving the following command:
  +
  [source]
  ----
  jboss-cli.sh -c
  ----
  +
  The `-c` switch connects using the default host (`localhost') and management port (`9990'). These values are specified in `bin/jboss-cli.xml' and can be updated.
  +
  This opens up the `jboss-cli' interactive console and shows the following prompt:
  +
  [source]
  ----
  [standalone@localhost:9990 /]
  ----
  +
  The prompt indicates that `jboss-cli' is connected to a standalone instance's default management port.
  +
  . If WildFly instance is running on a different host and/or port, then `--controller` switch can be used to specify that information.
  +
  .. In another shell, start another WildFly instance on a different port using the following command:
  +
  [source]
  ----
  ./bin/standalone.sh -Djboss.socket.binding.port-offset=10000
  ----
  +
  This will start another WildFly standalone instance on application port 18080 and management port 19090.
  +
  .. Use `jboss-cli' to connect with this instance by giving the following command:
  +
  [source]
  ----
  jboss-cli.sh -c --controller=localhost:19990
  ----
  +
  This opens up the `jboss-cli' interactive console and shows the following prompt:
  +
  [source]
  ----
  [standalone@localhost:19990 /]
  ----
  +
  The prompt indicates that `jboss-cli' is connected to a standalone instance on port `19990'.
  
  WildFly internal management model consists of _management resources_ that that are added, removed, or modified by using _operations_ and _commands_. Operations are low level but a comprehensive way to manage the server. Commands are more user-friendly, although most of them still translate into operation requests and some of them even into a few composite operation requests.
  
  All resources are organized in a tree. The path to the node in the tree for a particular resource is its _address_ and is identified by `/`.
  
  Each resource expose information about their state as _attributes_.
  
  Each resource may support child resources.
  
  All resources expose metadata that describes their attributes, operations, and child types. This metadata can be queried by invoking one or more of the _global operations_ supported by the resource.
  
  Command and operation request history is enabled by default. While in the command line session, you can use the arrow keys to go back and forth in the history of commands and operations.
  
  === Admin Console
  
  === File system-based
  
  === Maven plugin
  
  === REST API
  
  include::jrebel.asciidoc[]
  
  [[testing]]
  