Scribd
Upload
43 views2 pages

Transporting iFlows: Best Practices

The document outlines three main approaches for transporting iFlows from DEV to QA/PROD: using the Transport Management Service (TMS) for a controlled process, manual export/import via ZIP files for quick deployments, and CTS+ for on-premise or hybrid landscapes. Best practices include using TMS for security, externalizing parameters, grouping artifacts, maintaining consistent naming conventions, and thorough testing in QA before production. Each method has its own prerequisites and steps, with TMS being the recommended approach for its audit-traceability.

Uploaded by

selish
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
43 views2 pages

Transporting iFlows: Best Practices

The document outlines three main approaches for transporting iFlows from DEV to QA/PROD: using the Transport Management Service (TMS) for a controlled process, manual export/import via ZIP files for quick deployments, and CTS+ for on-premise or hybrid landscapes. Best practices include using TMS for security, externalizing parameters, grouping artifacts, maintaining consistent naming conventions, and thorough testing in QA before production. Each method has its own prerequisites and steps, with TMS being the recommended approach for its audit-traceability.

Uploaded by

selish
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Ways to Transport iFlows from DEV to QA/PROD

There are three main approaches:

1. Transport Management Service (TMS) – Recommended

SAP BTP's Transport Management Service allows you to move CPI artifacts across
subaccounts (e.g., from DEV to QA to PROD) in a controlled and auditable way.

Prerequisites:

• Subaccounts for DEV, QA, and PROD must be part of the same Global Account.

• Configure Transport Management and Cloud Integration in BTP Cockpit.

• Create Transport Nodes and Routes (DEV → QA → PROD).

Steps:

1. In DEV tenant:

o Deploy your iFlow.

o Export to Transport Management (via the "Transport" option in CPI).

2. In Transport Management:

o Approve the transport.

o Forward it to QA or PROD.

3. In QA/PROD tenant:

o Deploy the iFlow received via transport.

Benefit: Controlled, secure, and audit-traceable transport process.

2. Manual Export/Import (ZIP File) – Quick and Manual

Used for ad-hoc deployments or in smaller projects without TMS.

Steps:

1. In DEV tenant:

o Open your iFlow.

o Click Actions > Export → Downloads as a .zip.


2. In QA/PROD tenant:

o Go to Design.

o Click Create > Integration Flow > Import from file.

o Choose the .zip file and deploy.

Caution: Manual, error-prone, and lacks version control or approval process.

3. CTS+ (Change and Transport System from SAP Solution Manager) – For On-
Prem/Hybrid

Used in on-premise or hybrid SAP landscapes with Solution Manager.

Steps:

• Set up CTS+ in SolMan.

• Configure your CPI landscape in CTS Deploy Service.

• Export from DEV to QA/PROD using CTS transport requests.

Suitable for customers already using SAP Solution Manager.

Best Practices for Transporting iFlows

Tip Description

Use TMS For security, traceability, and audit compliance.

Externalize parameters (e.g., endpoint URLs, credentials) via Value


Use
Mapping or Config Parameters so the same iFlow can work across
Externalization
environments.

Group Include value mappings, security materials, and script collections when
Artifacts transporting iFlows.

Naming Use consistent versioning and naming (e.g., CustomerOrder_1.0.0) to


Convention avoid confusion.

Test
Always test in QA before promoting to PROD.
Thoroughly

You might also like