如何在Bluemix上推送并启动Spring Boot构建的Spring Batch批量应用？

Absolutely, you can deploy your Spring Batch uber-jar as a non-web batch application on Bluemix—here's a straightforward, step-by-step guide to get it done, plus how to launch it via the command line:

1. Create a Deployment Configuration (manifest.yml) #

Bluemix relies on a manifest.yml file to define app settings. Since this isn't a web app, we need to override default behaviors (like port binding) and specify exactly how to start your batch job.

Create a manifest.yml file in the same folder as your uber-jar with these contents (replace placeholder values with your app's details):

---
applications:
- name: your-batch-app-name  # Pick a unique name for your app
  path: ./your-uber-jar-file.jar  # Path to your built uber-jar
  buildpack: java_buildpack
  memory: 1G  # Adjust based on your job's memory needs (e.g., 512M for small jobs)
  instances: 1
  command: java -jar your-uber-jar-file.jar  # Explicit command to start the batch job
  no-route: true  # Critical: Disables public URL/port binding (no web server needed)

• no-route: true is essential here—it tells Bluemix we don't need a public endpoint, which avoids errors from missing web server ports.
• Tweak memory to match your batch job's resource demands (e.g., if your job processes large datasets, you might need 2G).

2. Deploy the App to Bluemix #

First, log into your Bluemix account using the Cloud Foundry CLI:

cf login

Once logged in, navigate to the folder with your manifest.yml and jar file, then run:

cf push

This will upload your jar, stage it using the Java buildpack, and set up your app instance in Bluemix.

3. Launch the Batch App via Command Line #

You have two common ways to run your batch app, depending on your use case:

Scenario 1: One-Time Batch Job Execution #

If your Spring Batch app runs the job once and exits (the default behavior for most batch jobs), using cf start might cause Bluemix to mark the app as "crashed" (since the process exits). Instead, use Cloud Foundry tasks to run it as a one-off job:

cf run-task your-batch-app-name "java -jar your-uber-jar-file.jar" --name batch-job-run

To check the task's status:

cf tasks your-batch-app-name

To view logs and confirm the job completed successfully (or debug errors):

cf logs your-batch-app-name --recent

Scenario 2: Scheduled/Continuous Batch Execution #

If your app uses a scheduler (like Spring's @Scheduled annotation) to run jobs periodically, you'll want the app to stay running. In this case, start it normally:

cf start your-batch-app-name

Bluemix will monitor the process and restart it if it exits unexpectedly. To verify the app is running:

cf app your-batch-app-name

To watch live logs and confirm scheduled jobs are executing:

cf logs your-batch-app-name

Quick Tips #

• Trim Unnecessary Dependencies: If your Spring Boot app includes web starters (like spring-boot-starter-web), exclude them to reduce overhead and avoid accidental port binding attempts.
• Log Monitoring: Always check logs with cf logs if you run into issues—they'll show exactly what happened when the job ran.
• Resource Tuning: For one-time jobs, you can set instances: 0 in your manifest to avoid keeping idle instances running, then use cf run-task to trigger execution as needed.

内容的提问来源于stack exchange，提问作者Abhi