Quellenstraße 7 - 70376 Stuttgart - Germany

KaTe GmbH – Bilingual Mega Menu
SAP Cloud Integration Transport Management | IntegraTM
IntegraOps · Transport Management
IntegraTM

Control SAP Cloud Integration transports

With IntegraTM, packages and integration artifacts can be transferred reliably from source to target tenants. Targeted selection, parameters, dependency checks, approvals and technical verification combine into a controlled workflow.

Deployment remains a deliberate decision — transfer, verification and activation can be controlled independently.

IntegraTM transport lane: SAP Cloud Integration artifacts are transferred between development, test and production tenants
Transport routes, runs, progress and outcomes in one interface.
Configured transport routesStructure source and target
Controlled releasesEmail, approval & rejection
Technical verificationRead back and validate imported content
History & reportsTrack scope, decisions and outcomes
Overview

What is IntegraTM?

As IntegraOps’ transport management component for SAP Cloud Integration, IntegraTM brings the steps of a controlled artifact transport together. This keeps scope, decisions and technical outcomes connected in one traceable workflow.

From package to verified target state

Select packages or integration artifacts. Externalized parameters are detected, proposed with values and can be adjusted. After dependencies are reviewed and approval is granted, the transfer to the target system is completed with subsequent technical verification.

How it works

A transport run with clear decisions

From artifact selection to technical verification, IntegraTM guides you through a clear transport workflow. Reusable templates reduce preparation effort so recurring transports can be prepared consistently.

01

Choose a transport route

Define source and target for the planned run.

02

Define the scope

Select packages or supported individual artifacts precisely.

03

Review the configuration

Decide on parameters and resolve identified dependencies.

04

Approve & import

Include required approvals and execute the import.

05

Verify & document

Read back design content and configuration in the target technically.

Important clarification: Technical verification confirms imported design content and configuration. Functional behavior in the target is then tested separately. A deployment request alone therefore proves neither a completed deployment nor successful message processing.

Capabilities

Everything a controlled transport needs

IntegraTM capabilities support technical preparation, controlled execution and traceable outcomes for SAP Cloud Integration.

Configured transport routes

Defined source-to-target connections structure transfers between SAP Cloud Integration tenants. This makes every transport route clearly traceable.

Targeted artifact selection

Choose complete packages or supported individual artifacts to match the objective. This keeps the transport scope intentionally focused.

Externalized parameters

Target-specific configuration values can be adopted from the source, retained in the target or adjusted. This keeps target configuration under control.

Dependency check

Identified missing dependencies can be resolved before import. This reduces the risk of incomplete transports.

Templates & approvals

Reusable templates simplify recurring transports while required approvals are documented as part of the workflow.

Email & approval workflow

Whenever approval requests, rejections, errors or relevant transport events occur, stakeholders are informed by email. Authorized people can also approve or reject transports at the approval step.

Technical verification

After import, design content and configuration can be read back and verified technically. This makes the target state transparent.

History, reports & API

Scope, decisions and outcomes remain traceable; transports can also be integrated with other automation tools through the API.

Multiple environments in one tenant

Use one SAP Integration Suite tenant to host more than one logically separated environment. Virtual transports establish separate environments within the same physical tenant.

Use Cases

Handle transport tasks systematically

To organize cloud integration across development, test and production stages in a controlled way, IntegraTM provides clear transport workflows. This allows recurring tasks to be prepared, approved and checked transparently.

Transfer a new version to the test tenant

Select the affected iFlows, check dependencies and define externalized parameters for the target. This prepares the test state precisely.

Release to production

First prepare the transport scope, then request approval by email and approve or reject the run at the approval step.

Control transfer and activation separately

Import and verify content, then make a deliberate decision about a subsequent deployment.

Streamline recurring transports

Use saved templates while still running each new transport with its own decisions and checks. This retains control.

Integration with automation tools

Integrate transports into existing tools through the API and actively inform stakeholders about approvals or errors.

Create virtual environments in one tenant

Use virtual transports to establish two logically separated environments in one SAP Integration Suite tenant. A dedicated prefix keeps virtual copies clearly distinguishable.

Virtual environments

Run more than one environment in a single tenant

With IntegraTM, one SAP Integration Suite tenant can host more than one logically separated environment. This can support a three-tier system landscape with only two physical tenants, for example for development, test and production. Virtual transports establish distinct environments within the same tenant.

Virtual transports establish distinct logical environments within one shared physical tenant.
Dedicated prefixes identify virtual copies clearly in transport routes and history.
A three-tier development, test and production landscape can be organized with two physical tenants.
FAQ

Frequently asked questions about IntegraTM

Direct answers on controlled SAP Cloud Integration transports, approvals and target configurations.

Transport scope and target configuration

What is IntegraTM?
As IntegraOps’ transport management component, IntegraTM enables transparent transfers of packages and integration artifacts in SAP Cloud Integration. It connects selection and parameter decisions with approvals, import and technical verification.
Which content can be transported with IntegraTM?
Depending on the objective, complete packages or supported individual artifacts can be selected. The scope is defined for each run and then documented in the history.
How are externalized parameters handled?
For target-specific configuration values, you can decide whether they are adopted from the source, retained in the target or adjusted. This deliberately incorporates target configuration into the workflow.

Approvals, deployment and technical verification

How do email notifications and approvals work?
When approval requests, rejections, errors or relevant transport events occur, stakeholders are informed by email. Authorized people can approve or reject a transport at the approval step; the decision is also documented in the transport run.
Is deployment automatic after transport?
No. Deployment is optional. After import and technical verification, it can be decided whether transferred content should be activated. A deployment request alone proves neither a completed deployment nor successful message processing.
What does technical verification confirm?
Technical verification reads back and checks imported design content and configuration in the target. Functional behavior is then tested in the relevant test process.

Virtual environments in SAP Integration Suite

How can a three-tier landscape be implemented with only two SAP Integration Suite tenants?
IntegraTM uses virtual transports to establish more than one logically separated environment within a single SAP Integration Suite tenant. This can support a three-tier system landscape with two physical tenants, for example for development, test and production. A dedicated prefix distinguishes virtual copies inside the shared tenant. Returning a transport requires a suitable saved mapping from a successfully verified entry run; Virtual → Virtual is not currently supported.
Can IntegraTM be integrated into existing automation?
Yes. The API can integrate transports with other automation tools and broader workflows. History and reports also help trace the scope, decisions and technical outcomes of each run.
Next step

Would you like to structure your SAP Cloud Integration transports?

Discuss your tenant setup, release organization and requirements for approvals, parameters and technical verification with KaTe.