anchor.diff:  1. download the Spring Cloud Data Flow Admin and Shell apps:
   
   ```
  -wget http://repo.spring.io/milestone/org/springframework/cloud/spring-cloud-dataflow-admin/1.0.0.M2/spring-cloud-dataflow-admin-local-1.0.0.M2.jar
  +wget http://repo.spring.io/milestone/org/springframework/cloud/spring-cloud-dataflow-admin-local/1.0.0.M2/spring-cloud-dataflow-admin-local-1.0.0.M2.jar
   wget http://repo.spring.io/milestone/org/springframework/cloud/spring-cloud-dataflow-shell/1.0.0.M2/spring-cloud-dataflow-shell-1.0.0.M2.jar
   ```
   [start=2]
  
positive.code: dataflow:>
  ```
  
  ==== Spring Cloud Data Flow Admin app configuration settings for Cloud Foundry
  
  The following pieces of configuration must be provided, e.g. by setting variables in the apps environment, or passing variables on the Java invocation:
  
  ```
  # Default values cited after the equal sign.
  # Example values, typical for Pivotal Web Services, cited as a comment
  
  # url of the CF API (used when using cf login -a for example), e.g. https://api.run.pivotal.io
  # (for setting env var use CLOUDFOUNDRY_API_ENDPOINT)
  cloudfoundry.apiEndpoint=
  
  # name of the organization that owns the space above, e.g. youruser-org
  # (for setting env var use CLOUDFOUNDRY_ORGANIZATION)
  cloudfoundry.organization=
  
  # name of the space into which modules will be deployed
  # (for setting env var use CLOUDFOUNDRY_SPACE)
  cloudfoundry.space=<same space as admin when running on CF, or 'development'>
  
  # the root domain to use when mapping routes, e.g. cfapps.io
  # (for setting env var use CLOUDFOUNDRY_DOMAIN)
  cloudfoundry.domain=
  
  # Comma separated set of service instance names to bind to the module.
  # Amongst other things, this should include a service that will be used
  # for Spring Cloud Stream binding
  # (for setting env var use CLOUDFOUNDRY_SERVICES)
  cloudfoundry.services=redis
  
  # username and password of the user to use to create apps (modules)
  # (for setting env var use CLOUDFOUNDRY_USERNAME and CLOUDFOUNDRY_PASSWORD)
  cloudfoundry.username=
  cloudfoundry.password=
  
  # Whether to allow self-signed certificates during SSL validation
  # (for setting env var use CLOUDFOUNDRY_SKIP_SSL_VALIDATION)
  cloudfoundry.skipSslValidation=false
  ```
  
  === Deploying on YARN
  
  NOTE: The Apache YARN SPI implementation is a separate link:https://github.com/spring-cloud/spring-cloud-dataflow-admin-yarn[project].
  
  For YARN deployments we run the Admin app as a standalone application and all modules used for streams and tasks will be deployed on the YARN cluster that is configured to be used.
  
  [start=1]
  1. download the Spring Cloud Data Flow YARN distribution ZIP file which includes the Admin and the Shell apps:
  
  ```
  wget http://repo.spring.io/snapshot/org/springframework/cloud/dist/spring-cloud-dataflow-admin-yarn-dist/1.0.0.M2/spring-cloud-dataflow-admin-yarn-dist-1.0.0.M2.zip
  ```
  
  Unzip the distribution ZIP file and change to the directory containing the deployment files.
  
  ```
  cd spring-cloud-dataflow-admin-yarn-1.0.0.M2
  ```
  
  [start=2]
  2. Make sure Hadoop and Redis are running. If either one is not running on `localhost` you need to configure them in `config/servers.yml`
  
  [start=3]
  3. If this is the first time deploying make sure the user that runs the Admin app has rights to create and write to /dataflow directory. If there is an existing deployment on `hdfs` remove it using:
  
  ```
  $ hdfs dfs -rm -R /dataflow
  ```
  
  [start=4]
  4. start the Spring Cloud Data Flow Admin app for YARN
  
  ```
  $ ./bin/dataflow-admin-yarn
  ```
  
  [start=5]
  5. start `spring-cloud-dataflow-shell`
  
  ```
  $ ./bin/dataflow-shell
  ```
  
  [start=6]
  6. Test the deployment
  
  Create a stream:
  
  ```
  dataflow:>stream create --name "ticktock" --definition "time | hdfs --rollover=100" --deploy
  ```
  
  List streams:
  
  ```
  dataflow:>stream list
    Stream Name  Stream Definition           Status
    -----------  --------------------------  --------
    ticktock     time | hdfs --rollover=100  deployed
  ```
  
  After some time, destroy the stream:
  
  ```
  dataflow:>stream destroy --name ticktock
  ```
  
  YARN application is pushed and started automatically during a stream deployment process. However, at the moment, this YARN application instance is not automatically stopped. This has to be done using the provided YARN CLI for now. In future releases this should be done by the Admin app when the stream is un-deployed.
  
  From the Spring Cloud Data Flow Shell use:
  
  ```
  dataflow:>! bin/dataflow-yarn-cli submitted
  APPLICATION ID                  USER          
  ------------------------------  ------------  
  application_1447944262603_0003  spring        
  ```
  Use the application id to kill the app using the CLI:
  
  ```
  dataflow:>! bin/dataflow-yarn-cli kill -a application_1447944262603_0003
  Kill request for application_1447944262603_0003 sent
  ```
  
  
negative.code: $ java -jar spring-cloud-dataflow-shell-1.0.0.M2.jar
  ```
  
  If the admin and local are not running onthe same host, point the shell to the admin server
  
  ```
  server-unknown:>admin config server http://s-c-dataflow-admin.cfapps.io
  