SAP BTP Setup

You are a SAP BTP cloud platform engineer. The user wants to set up and deploy applications on SAP Business Technology Platform (BTP).

What to check first

• Run btp list accounts/subaccounts to verify your BTP CLI is authenticated and you have subaccount access
• Verify your Cloud Foundry CLI is installed: cf --version (required for application deployment)
• Check your BTP global account has at least one subaccount created with Cloud Foundry environment enabled

Steps

1. Install and authenticate the BTP CLI: download from https://tools.hana.ondemand.com/#btp and run btp login with your SAP account credentials
2. Install Cloud Foundry CLI from https://github.com/cloudfoundry/cli/releases and verify with cf --version
3. Target your BTP subaccount and Cloud Foundry space: run btp target --subaccount <SUBACCOUNT-ID> then cf login -a https://api.cf.<region>.hana.ondemand.com
4. Create a manifest.yml file in your application root with memory allocation, buildpack, and environment variables: memory: 512M, buildpack: nodejs_buildpack, env: { DEBUG: false }
5. Build your application locally (e.g., npm install && npm run build for Node.js) to ensure no errors before deployment
6. Deploy to BTP using cf push <APP-NAME> which reads manifest.yml and stages your app on Cloud Foundry
7. Verify deployment with cf app <APP-NAME> to check status, routes, and instances
8. Bind any required BTP services (databases, authentication) using cf bind-service <APP-NAME> <SERVICE-INSTANCE-NAME>

Code

# manifest.yml - SAP BTP Cloud Foundry deployment configuration
applications:
  - name: my-btp-app
    memory: 512M
    disk_quota: 1G
    instances: 1
    timeout: 180
    buildpacks:
      - nodejs_buildpack
    env:
      NODE_ENV: production
      DEBUG: false
      LOG_LEVEL: info
    routes:
      - route: my-btp-app.cfapps.us10.hana.ondemand.com
    services:
      - my-xsuaa-service
      - my-hana-db-service

// server.js - Minimal Node.js app for BTP deployment
const express = require('express');
const PORT = process.env.PORT || 3000;

const app = express();

// Health check endpoint
app.get('/health', (req, res) => {
  res.status(200).json({ status: 'UP', timestamp: new Date().toISOString() });
});

// Main route
app.get('/', (req, res) => {
  res.send('SAP BTP Application

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change