anchor.diff:  
   ### Other Deployment Options (OPTIONAL)
   
  -For the first deployment we used a shared volumen on the host computer. Let's explore deeper, what other deployment options we have.
  +For the first deployment we used a shared volumen on the host computer. Let's explore some additional ways to deploy your Java EE applications.
   
   #### Using the CLI
   
  
positive.code: | Password | docker#admin
  |====
  
  ### Stop and Remove Container
  
  #### Stop Container
  
negative.code: . Start/Stop/Restart Nodes in respective mode i.e. Standalone/Domain.
  . Adding/Deleting resource or subsystems to servers.
  
  Lets use the CLI to deploy Ticket Monster to WildFly running in the container.
  
  . CLI needs to be locally installed and comes as part of WildFly. Download WildFly 8.2 from http://<INSTRUCTOR_IP>:8082/downloads/wildfly-8.2.0.Final.zip. Unzip into a folder of your choice (e.g. `/Users/arungupta/tools/`). This will create `wildfly-8.2.0.Final` directory here. This folder is named $WIDLFY_HOME from here on. Make sure to add the `/Users/arungupta/tools/wildfly-8.2.0.Final/bin` to your $PATH.
  +
  [source, text]
  ----
  # Windows Example
  set PATH=%PATH%;%WILDFLY_HOME%/bin
  ----
  +
  . Run the ``wildfly-management'' image with fixed port mapping as explained in <<Fixed_Port_Mapping>>.
  . Run the `jboss-cli` command and connect to the WildFly instance.
  +
  [source, text]
  ----
  cd %WIDLFY_HOME%/bin
  ./jboss-cli.sh --controller=dockerhost:9990  -u=admin -p=docker#admin -c
  ----
  +
  This will show the output as:
  +
  [source, text]
  ----
  [standalone@dockerhost:9990 /]
  ----
  +
  . Deploy the application as:
  +
  [source, text]
  ----
  deploy <TICKET_MONSTER_PATH>/ticket-monster.war --force
  ----
  
  Now you've sucessfully used the CLI to remote deploy the Ticket Monster application to WildFly running as docker container.
  
  And again, keep the container running, we're going to look into the last deployment option you have.
  
  #### Using the Web Console
  
  WildFly comes with a web-based administration console. It also relies on the same management APIs that we've already been using via JBoss Developer Tools and the CLI. It does provide a nice web-based way to administrate your instance and if you've already exposed the container ports, you can simply access it via the URL: http://dockerhost:9990 in your web browser.
  
  .WildFly Web Console
  image::images/console1.png[]
  
  Username and password credentials are shown in <<WildFly_Administration_Credentials>>. Now navigate through the console and execute the following steps to deploy the application:
  
  . Go to the ``Deployments'' tab.
  . Click on ``Add'' button.
  . On ``Step 1/2: Deployment Selection'' screen, select the <TICKET_MONSTER_PATH>/ticket-monster.war file on your computer and click ``Next''. This would be `ticket-monster/demo/target/ticket-monster.war` from <<Build_Application>>.
  . On the ``Step 2/2: Verify Deployment Names'' screen, select ``Enable'' checkbox, and click on ``Save''.
  
  This will complete the deployment of Ticket Monster using Admin Console.
  
  #### Using Management API
  
  A standalone WildFly process, process can be configured to listen for remote management requests using its ``native management interface''. The CLI tool that comes with the application server uses this interface, and user can develop custom clients that use it as well. In order to use this, WildFly management interface listen IP needs to be changed from 127.0.0.1 to 0.0.0.0 which basically means, that it is not only listening on the localhost but also on all publicly assigned IP addresses.
  
  . Start another WildFly instance again:
  +
  [source, text]
  ----
  docker run -d --name wildflymngm -p 8080:8080 -p 9990:9990 --link db:db <INSTRUCTOR_IP>:5000/wildfly-management
  ----
  +
  There is no mapped volume in this case but an additional port exposed. The WildFly image that is used makes it easier for you to play around with the deployment via the management API. It has a tweaked start script which changes the management interface according to the behavior described in the first sentence.
  +
  . Create another new server adapter in JBoss Developer Studio.
  +
  .Create New Server Adapter
  image::images/jbds7.png[]
  +
  . Keep the defaults in the adapter properties.
  +
  .Adapter Properties
  image::images/jbds8.png[]
  +
  . Set up server properties by specifying the admin credentials (docker#admin). Note, you need to delete the existing password and use this instead:
  +
  .Management Login Credentials
  image::images/jbds9.png[]
  +
  . Right-click on the newly created server adapter and click ``Start''. Status quickly changes to ``Started, Synchronized'' as shown.
  +
  .Synchronized WildFly Server
  image::images/jbds10.png[]
  +
  . Right-click on the Ticket Monster project, select ``Run on Server'' and choose this server. The project runs and displays the start page of ticket-monster.
  . Stop WildFly when you're done.
  +
  [source, text]
  ----
  docker stop wildflymngm
  ----
  
  ## Docker Tools in Eclipse
  
  The Docker tooling is aimed at providing at minimum the same basic level features as the command-line interface, but also provide some advantages by having access to a full fledged UI.
  As this is still in early access stage, you will have to install it first:
  
  