Sap Btp Job Scheduling

SAP BTP Job Scheduling Service

Related Skills

• sap-dependency-security: Use for secure dependency and workflow hardening when your job scheduling microservices maintain npm/CLI dependency stacks

Table of Contents

• Overview
• When to Use This Skill
• Quick Decision Tree
• Core Concepts
• Service Constraints
• Quick Reference Tables
• Schedule Formats
• Cron Format (7 fields)
• Schedule Lifecycle States
• HTTP Methods for Jobs
• Best Practices
• Scheduling Optimization
• Asynchronous Jobs
• One-Time Schedules
• Authentication Quick Start
• Standard Plan (OAuth 2.0)
• xs-security.json Configuration
• Create Job Example
• Node.js Client Library
• Rate Limits
• Service Behavior
• Outage Recovery
• Auto-Deactivation Triggers
• Bundled Resources
• Common Pitfalls
• External Resources
• Updates and Maintenance

Overview

SAP Job Scheduling Service is a runtime-agnostic platform service for defining and managing one-time and recurring jobs or Cloud Foundry tasks on SAP BTP. It operates across multiple hyperscalers (AWS, Azure, GCP) without requiring application modifications.

Documentation Source: https://help.sap.com/docs/job-scheduling

Last Verified: 2025-11-27

When to Use This Skill

Use this skill when:

• Setting up Job Scheduling Service on Cloud Foundry or Kyma runtime
• Creating and managing jobs via REST API or dashboard
• Configuring schedules using cron, date/time, or human-readable formats
• Implementing asynchronous job execution for long-running processes
• Securing action endpoints with OAuth 2.0 and XSUAA
• Integrating with SAP Cloud ALM or Alert Notification Service
• Developing multitenant applications with tenant-aware job scheduling
• Troubleshooting job execution issues and schedule failures
• Using the Node.js client library (@sap/jobs-client)

Quick Decision Tree

What Task?

Setup & Configuration
├─ Initial setup prerequisites → references/setup-guide.md
├─ Create service instance
│  ├─ BTP Cockpit → references/setup-guide.md#cockpit
│  ├─ CF CLI → references/setup-guide.md#cf-cli
│  └─ Kyma Dashboard → references/setup-guide.md#kyma
└─ Configure XSUAA scopes → references/security.md

Job Management
├─ Create jobs → references/rest-api.md#create-job
├─ Configure schedules → references/rest-api.md#schedules
├─ Run logs & monitoring → references/rest-api.md#run-logs
└─ Dashboard operations → references/operations.md#dashboard

Schedule Configuration
├─ One-time vs recurring → references/concepts.md#schedule-types
├─ Cron format → references/concepts.md#cron-format
├─ Date/time formats → references/concepts.md#date-formats
└─ Human-readable → references/concepts.md#human-readable

Asynchronous Execution
├─ Async mode flow → references/concepts.md#async-mode
├─ Callback implementation → references/rest-api.md#update-run-log
└─ CF tasks → references/concepts.md#cf-tasks

Security & Authentication
├─ OAuth 2.0 setup → references/security.md#oauth
├─ XSUAA configuration → references/security.md#xsuaa
└─ Credential rotation → references/security.md#rotation

Integrations
├─ SAP Cloud ALM → references/integrations.md#cloud-alm
└─ Alert Notification → references/integrations.md#alert-notification

Troubleshooting
├─ Common errors → references/troubleshooting.md#errors
├─ FAQ → references/troubleshooting.md#faq
└─ Support: BC-CP-CF-JBS

Version History & Updates
└─ What's New (2021-2025) → references/changelog.md

Core Concepts

Job

A collection of schedules with an action endpoint. Jobs invoke a configured URL at specified times synchronously (short operations) or asynchronously (long processes).

Schedule

A one-time or recurring entity within a job. Supports multiple formats (cron, date/time, human-readable) and has three lifecycle states: SCHEDULED → RUNNING → COMPLETED.

Action Endpoint

An HTTP/REST endpoint exposed by your application that the service invokes when schedules trigger. Must be OAuth 2.0 protected in production.

Cloud Foundry Task

An app or script that runs independently in its own container. Always executes asynchronously with configurable memory allocation.

Service Constraints

Quick Reference Tables

Schedule Formats

Cron Format (7 fields)

Year Month Day DayOfWeek Hour Minute Second
*    *     *   *         *    *      *

Schedule Lifecycle States

HTTP Methods for Jobs

Best Practices

Scheduling Optimization

Avoid Peak Times:

• ❌ 0th or 30th second of any minute
• ❌ 0th, 30th, or multiples of 5 minutes
• ❌ Top of each hour
• ❌ Midnight UTC (busiest time)

Use Irregular Times:

• ✅ 01:12:17 instead of 01:00:00
• ✅ 01:38:37 instead of 01:30:00

Asynchronous Jobs

1. Return 202 Accepted immediately - Don't block the request
2. Store request headers - x-sap-job-id, x-sap-job-schedule-id, x-sap-job-run-id, x-sap-scheduler-host
3. Update run log on completion - Single API call with final status
4. Handle timeouts - Default 30 min, configurable up to 7 days

One-Time Schedules

• Use only for testing/validation
• Auto-deactivate after execution
• Use "time": "now" for immediate execution

Authentication Quick Start

Standard Plan (OAuth 2.0)

# Get access token
curl -X POST "<uaa_url>/oauth/token" \
  -H "Authorization: Basic $(echo -n '<clientid>:<clientsecret>' | base64)" \
  -d "grant_type=client_credentials"

# Use token in API calls
curl -X GET "https://jobscheduler-rest.<landscape>/scheduler/jobs" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json"

xs-security.json Configuration