onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

teched2025-IN161

An SAP TechEd 2025 session on assessing and migrating SAP Process Orchestration integration scenarios to SAP Integration Suite.

Two capabilities of SAP Integration Suite carry the session. Migration Assessment evaluates how integration scenarios might be migrated and estimates the technical effort involved; Migration Tooling then creates interfaces in Cloud Integration automatically from SAP Process Orchestration information, using integration flow templates that follow a pattern as the skeleton, and the README puts the share of technical migration effort it automates at 60-70%. Exercise 1, the assessment, is marked optional and can be skipped: the tooling exercises run independently of it. Exercise 2 migrates a content-based-routing scenario onto the pipeline for Cloud Integration, which sets scenarios up the way SAP Process Orchestration processes messages, in pipelines, with exactly-once delivery, error handling and restart; exercises 3 and 4 then extend the generated flows at the pipeline's extension points, with custom header properties and a custom receiver determination. The exercises run on one of four workshop tenants the session provides, with a user the instructors hand out.

GitHub4 ★

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
BTP/BAIP
Demonstrates
Platform migrationBTPPlatform migrationcapabilityMoving an application, integration or database from one platform to another: assessing what exists, converting what tooling supports, and adapting what cannot carry over. Language-level compatibility is a separate concern from moving the platform around an application.
Requires
SAP Integration SuiteSAP Integration Suiteartifactthe tenant the exercises run on, and the home of both the Migration Assessment and the Migration Tooling capability; the session provides four tenants and names the one in use.

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222@SAP-samplesmaintainerAjay SorengPersonContributes to this
In the atlas: contributes to 36@ajaysorengClaire TsengPersonContributes to this
In the atlas: contributes to 1@clairechingweitsengMaiara-EllwangerPersonContributes to this
In the atlas: contributes to 1@Maiara-EllwangerAlexander BundschuhPersonContributes to this
In the atlas: contributes to 2@peasantsboot4 contributors

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
Workshop or CodeJam material

Connections2

README

quoted from SAP-samples/teched2025-IN161 under Apache-2.0, read
SAP-samples/teched2025-IN161/README.mdOn GitHub

IN161 - Modernize and transform your integration to the cloud

Description

This repository contains the material for the SAP TechEd 2025 session called IN161 - Modernize and transform your integration to the cloud.

Overview

This session introduces attendees to the migration assessment and migration tool supporting you in the transformation from SAP Process Orchestration to SAP Integration Suite.

The Migration Assessment capability of SAP Integration Suite lets you evaluate how various integration scenarios might be migrated and allows you to estimate the technical efforts involved in the migration process.

After having finished the assessment of the current SAP Process Orchestration landscape, the next step is the actual migration. The goal of the Migration Tooling is to provide a semi-automated migration where interfaces in the Cloud Integration capability of SAP Integration Suite will be automatically created based on SAP Process Orchestration information, so that ideally 60-70% of technical migration efforts are automated. The migration of scenarios is based on a pattern approach, which means that integration flow templates following a specific pattern are used as skeleton to migrate the content and create the final integration flows.

In this exercise, we will leverage the so called Pipeline for Cloud Integration which is supported within the migration tooling. The Pipeline for Cloud Integration allows you to set up your integration scenarios in Cloud Integration similarly to how messages are processed in SAP Process Orchestration, in pipelines. As such, it helps you accelerating the transition to the cloud. It can be seen as framework which allows you to handle asynchronous messages in a common way with out-of-the-box support for exactly once delivery, error handling and sophisticated restart capabilities. For an introduction to the Pipeline for Cloud Integration, check out this blog post.

Requirements

The requirements to follow the exercises in this repository are...

Access to SAP Integration Suite tenant

For running through the exercises, we provide the following SAP Integration Suite tenants. The instructors will let you know which of the tenants are actually used for the exercises.

Tenants in EU:

Tenants in US:

Access:

  • Use the user userXX with XX from 01 to 45.

Note: You can copy and paste the user name from below. Please replace XX with the ID assigned to you. The ID and the password will be provided by the instructors during the session.

userXX

Prerequisites

As a prerequisite for the migration tooling exercises, you first need to run through the following preparation steps.

Exercises

In the following, the complete list of exercise steps are listed. You can use this section as an index or table of contents. Use the breadcrumb navigation on top of the pages to go back to the Table of Contents.

If you are interested in how the Migration Assessment works, start with the first exercise. Note, this exercise is optional. You can run through the migration tooling exercises independent of the migration assessment exercise.

For running through the Migration Tooling, continue with the second exercise.

To extend the generated integration flows using the Pipeline's extention points, run through the following exercises.

Contributing

Please read the CONTRIBUTING.md to understand the contribution guidelines.

Code of Conduct

Please read the SAP Open Source Code of Conduct.

How to obtain support

Support for the content in this repository is available during the actual time of the online session for which this content has been designed. Otherwise, you may request support via the Issues tab.

License

Copyright (c) 2025 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/teched2025-IN161tree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, operations-and-runtime
Contributors4
Ajay SorengClaire TsengMaiara-EllwangerAlexander Bundschuh

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-teched2025-in161
JSON
/artifacts/sap-samples-teched2025-in161.json
MCP
Connecting an agent