SAP/cloud-integration-delivery-orchestrator

Orchestrate SAP Cloud Integration delivery across multi-tenant landscapes — replace repetitive manual steps with a single governed workflow.

Deploy the pre-built Docker image to SAP BTP Cloud Foundry with the supplied MTA descriptor.

Start setup 🚀

For evaluation, use a non-productive landscape.

Need help? Open a GitHub Issue — actively maintained by the team behind it.

• Set Up a Governed SAP Cloud Integration Delivery Flow — Now Open Source — product overview, deployment on SAP BTP, and core capabilities.
• There Is No "Delivery" in SAP Cloud Integration — why transport, import, and deploy are separate steps today.
• See What Changed in an SAP Cloud Integration iFlow Before Moving It to Another Tenant — Git snapshots, GitHub App sync, and BPMN Visual Diff for source-to-target artifact review.

This project is a fit if you:

• run more than one SAP Cloud Integration tenant and coordinate releases across them;
• own and manage your transport lifecycle — your team develops iFlows, configures TMS, and deploys to Test/Production without relying on a separate operations team;
• use SAP Cloud Transport Management for transport and routing; and
• can deploy to a BTP Cloud Foundry subaccount with the required service entitlements.

Ensure the following entitlements are assigned to your subaccount:

Clone the repository and create your landscape file:

git clone https://github.com/SAP/cloud-integration-delivery-orchestrator.git
cd cloud-integration-delivery-orchestrator

cp example.mtaext your-landscape.mtaext
# Edit your-landscape.mtaext

Minimal configuration in your-landscape.mtaext:

_schema-version: "3.1.0"
ID: cloud-integration-delivery-orchestrator-myorg
extends: cloud-integration-delivery-orchestrator

parameters:
  # Required — URL prefix (e.g. orchestrator → orchestrator.cfapps.eu10.hana.ondemand.com)
  app-host-prefix: "your-orchestrator-cf-app-prefix"
  # Required — defaults to :latest; pin to a release tag if you prefer a fixed version
  docker-image: "ghcr.io/sap/cloud-integration-delivery-orchestrator:latest"
  # Optional — PostgreSQL plan: development (default) or standard (production)
  # db-service-plan: "standard"

If you already have service instances, override the service-name in the resources section of your .mtaext. See example.mtaext for all available overrides.

mbt build

cf login -a https://api.cf.<region>.hana.ondemand.com -o <org> -s <space>

cf deploy mta_archives/cloud-integration-delivery-orchestrator_1.0.0.mtar -e your-landscape.mtaext

The MTA archive file name follows the version in mta.yaml (currently 1.0.0). The deployer will:

1. Create or update service instances (XSUAA, PostgreSQL, Destination, etc.)
2. Pull the Docker image from the registry
3. Start the application with all service bindings

• Assign a role collection in BTP Cockpit → Security → Role Collections, then assign it to your user:

• Open the application at https://<app-host-prefix>.cfapps.<region>.hana.ondemand.com and sign in.
• Configure System Configuration — the mandatory setting is the TMS destination for your transport landscape. CPI tenant connections are configured separately when you register tenants.
• Run Tenant Bootstrap for a new tenant to validate prerequisites before the first delivery.

You are ready when you can log in, see the home page, and open System Configuration.

Cloud Integration Delivery Orchestrator automates the transport, deployment, and governance of SAP Cloud Integration (CPI) artifacts across multiple tenants. It coordinates transport request generation, artifact export, and deployment into a single governed workflow via TMS and CPI OData APIs.

The project distributes a pre-built Docker image deployed to SAP BTP Cloud Foundry via an MTA descriptor. This repository holds the deployment configuration (MTA descriptor, XSUAA security, extension templates); the application source code lives in the two repositories linked below.

The published Docker image is built from two open-source repositories:

Three services are inactive by default in mta.yaml. Enable them in your .mtaext when needed, then redeploy.

Not required for core delivery workflows. Enable it when your landscape needs on-premise connectivity through SAP Cloud Connector — for example, when GitHub is GitHub Enterprise Server (GHES) on your corporate network. In that case, Cloud Connector is required to reach GHES, which in turn enables GitHub sync and BPMN Visual Diff against repositories hosted there.

resources:
  - name: cloud-integration-delivery-orchestrator-conn
    active: true

Centralized log aggregation, distributed tracing, and metrics. Requires a cloud-logging entitlement.

resources:
  - name: cloud-integration-delivery-orchestrator-cls
    active: true

Without this entitlement, omit the block — the application deploys normally with no-op tracing and metrics.

Delivery event notifications (e.g. Email, Slack, Microsoft Teams). Requires an alert-notification entitlement.

resources:
  - name: cloud-integration-delivery-orchestrator-ans
    active: true

Most deployments keep docker-image on :latest. To pick up a new release:

1. Rebuild: mbt build
2. Redeploy: cf deploy mta_archives/cloud-integration-delivery-orchestrator_<version>.mtar -e your-landscape.mtaext

If you pin a specific image tag in .mtaext, update that tag before redeploying. Service bindings and database are preserved automatically.

cf undeploy cloud-integration-delivery-orchestrator --delete-services --delete-service-keys

Warning: --delete-services removes the PostgreSQL instance and all data. Omit this flag to preserve the database.

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Copyright 2026 SAP SE or an SAP affiliate company and cloud-integration-delivery-orchestrator contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.