anchor.diff:  To use environment variables set the following:
   
   ```
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_URL=https://api.run.pivotal.io
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_ORG={org}
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_SPACE={space}
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_DOMAIN=cfapps.io
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_SERVICES=redis,rabbit
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_USERNAME={email}
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_PASSWORD={password}
  -export SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_SKIP_SSL_VALIDATION=false
  +export spring.cloud.deployer.cloudfoundry.url=https://api.run.pivotal.io
  +export spring.cloud.deployer.cloudfoundry.org={org}
  +export spring.cloud.deployer.cloudfoundry.space={space}
  +export spring.cloud.deployer.cloudfoundry.domain=cfapps.io
  +export spring.cloud.deployer.cloudfoundry.services=redis,rabbit
  +export spring.cloud.deployer.cloudfoundry.username={email}
  +export spring.cloud.deployer.cloudfoundry.password={password}
  +export spring.cloud.deployer.cloudfoundry.skipSslValidation=false
   ```
   
   You need to fill in \{org}, \{space}, \{email} and \{password} before running these commands.
  
positive.code: NOTE: If you are deploying in an environment that requires you to sign on using the Pivotal Single Sign-On Service, refer to the section <<getting-started-security-cloud-foundry>> for information on how to configure the server.
  
  ```
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_URL https://api.run.pivotal.io
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_ORG {org}
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_SPACE {space}
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_DOMAIN cfapps.io
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_SERVICES redis,rabbit
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_USERNAME {email}
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_PASSWORD {password}
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_SKIP_SSL_VALIDATION false
  ```
  
  You can also set other optional properties for deployment to Cloud Foundry.
  
  You can set the buildpack that will be used to deploy the application.  For example, to use the Java offline buildback, set the following environment variable
  
  ```
  cf set-env dataflow-server SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_BUILDPACK java_buildpack_offline
  ```
  
  The default memory and disk sizes for a deployed application can also be configured. By default they are 1024 MB memory and 1024 MB disk.  Thse are controlled by setting an integer value, representing the number of MB, to the following properties, SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_MEMORY and SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_DISK.  The default number of instances to deploy is set to 1, but can be overridden using with the SPRING_CLOUD_DEPLOYER_CLOUDFOUNDRY_INSTANCES property.  All these properties are `@ConfigurationProperties` of the Cloud Foundry deployer.  See link:https://github.com/spring-cloud/spring-cloud-deployer-cloudfoundry/blob/master/src/main/java/org/springframework/cloud/deployer/spi/cloudfoundry/CloudFoundryDeployerProperties.java[CloudFoundryDeployerProperties.java] for more information.
  
  We are now ready to start the app.
  
  
negative.code: dataflow:>app import --uri http://bit.ly/stream-applications-rabbit-maven
  
  ```
  
  You can now use the shell commands to list available applications (source/processors/sink) and create streams. For example:
  
  [source,bash]
  ----
  dataflow:> stream create --name httptest --definition "http | log" --deploy
  ----
  
  NOTE: You will need to wait a little while until the apps are actually deployed successfully
  before posting data.  Tail the log file for each application to verify
  the application has started.
  
  Now post some data. The URL will be unique to your deployment, the following is just an example
  [source,bash]
  ----
  