anchor.diff:  
   <p class="note"><strong>Note</strong>: <%=vars.product_short%> automatically allocates 512MB to an app when you do not specify a value.</p>
   
  -### <a id='yourapp-step5'></a>Step 5: Provide a JDBC Driver ###
  +### Step 5: Provide a JDBC Driver ###
   
   The Java buildpack does not bundle a JDBC driver with your application. If your application accesses a SQL RDBMS, you must do the following:
   
   * Include the appropriate driver in your application.
   * Create a dependency task for the driver in the build script for your build tool or IDE.
   
  -### <a id='yourapp-step6'></a>Step 6: Configure Service Connections for Your Groovy App ###
  +### Step 6: Configure Service Connections for Your Groovy App ###
   
   <%=vars.product_short%> provides extensive support for connecting a Groovy app that runs on Grails or Spring to to services such as MySQL, PostgreSQL, MongoDB, Redis, and RabbitMQ. For more information on creating and binding a service connection for your app, refer to the appropriate framework topic:
   
  
positive.code: 
  Refer to the [Deploying with Application Manifests](../../devguide/deploy-apps/manifest.html) topic for more information.
  
  ### <a id='yourapp-step8'></a>Step 8: Log in and Target the API Endpoint ###
  
  Run `cf login -a [API_ENDPOINT]`, enter your login credentials, and select a space and org. The API endpoint is <%=vars.api_endpoint%>.
  
  <%=vars.gen_GSG%>
  
  ### <a id='yourapp-step9'></a>Step 9: Deploy Your Application ###
  When you deploy your application, `cf push`:
  
   * Creates a URL that is the route to your application. The URL is in the form HOST.DOMAIN, where HOST is the APP_NAME and DOMAIN is specified by your administrator. Your DOMAIN is`<%=vars.app_domain%>`.
  
negative.code: ## <a id='troubleshoot'></a>Troubleshooting ##
  If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
  
  ### App Deploy Fails ###
  Even when the deploy fails, the app might exist on <%=vars.product_short%>. Run `cf apps` to review the apps in the currently targeted org and space. You might be able to correct the issue using the <%=vars.dev_console_2%>, or you might have to delete the app and redeploy.
  
  ### App Requires a Unique URL ###
  <%=vars.product_short%> requires that each app that you deploy have a unique URL. Otherwise, the new app URL collides with an existing app URL and <%=vars.product_short%> cannot successfully deploy the app. You can fix this issue by running `cf push` with either of the following flags to create a unique URL:
  
  * `-n` to assign a different HOST name for the app.
  * `--random-route` to create a URL that includes the app name and random words. Using this option might create a long URL, depending on the number of words that the app name includes.
  
  
  
   
  