Integration Suite in 2025 & 2026

[Sookriti_Mishra]

Watched this beautiful session by @UdoPaltzer: https://www.youtube.com/watch?v=kFynsigf99o

In case you wanted a quick summary, here you go:

Modernize Integrations:

• Use standard content as much as you can
• Try to replace your RFCs and IDOCs with OData, Rest, and SOAP.
• Leverage Event-driven Integration pattern (for real-time scenarios)
• Use Side-by-side extensions to leverage API-centric integrations (with Build)
• Leverage monitoring and error resolution capabilities by using SAP AIF (for Business Users), and Cloud ALM (for technical users)

End of maintenance. Time is ticking!

• 2027 - SAP PO | Standard Maintenance sunset
• 2030 - SAP PO | Extended maintenance sunset
• 2028 - Cloud Platform Integration Neo | Services sunset

As far as your migration support is concerned, SAP provides Migration guides, documentation, and community content, which you are already aware of. What is additionally provided is:

• SAP Migration Factory | a free 2-3 weeks program to help you assess and plan your migration from PI/PO to Integration Suite
• Evolve Neo Program | free access to SAP experts who will help you plan and prepare your migration to Cloud Foundry
• SAP Service and Support | quick migration assistance with short duration, low cost engagements

Edge Integration Cell 

• The latest kid in the block is now flexible to run hybrid integration runtime, which is offered as an optional extension to Integration Suite, which will help customer-managed private landscape to leverage the capabilities of Integration Suite. 
• The landscapes it supports are: Microsoft AKS, Amazon EKS, Red Hat OpenShift, SUSE Rancher, Google GKE. 

Cloud ALM

• Your one stop for end-to-end technical health monitoring for: SAP BTP, S/4HANA, S/4HANA Cloud, SuccessFactors, Integration Suite, Customer Experience, Business Network, Concur, Fieldglass.
• You can configure the Oubound Channels like: email alerts, on chat-based apps like MS Teams/ Slack, Ticketing System like Service Now, Tasks like JIRA, APIs like SAP Analytics Cloud/ Grafana, and Operation Automations like  Build Process Automation, and SAP iRPA, etc.
• For us Integration Suite guys, you can use it for Cloud Integratio, API Management and Event Mesh as well.
• Specifically for Integration Suite, you can now monitor Tenant Availability, Certificate Validity, Database and Resource consumption, Content, Exhaustion status of JMS queue. So, no more building custom iflows to trigger alerts. Please know that CALM pulls data every 5 mins, and persists data for 30 days. I wonder if they have a feature to display the trace only for failed messages. SAP, are you listening?

Innovations in 2025

• Artificial Intelligence
  - Joule copilot-based discovery and reuse of artifacts were made available in Business Accelerator Hub
  - Generation of Integration flow steps 
  - Groovy script optimization
  - API anomaly detection
  - API traffic prediction for usage and trend
  - AI adapter
• Business Accelerators
  - Additional non-SAP adaptors like, AI, Google, BigQuery, IBM MQ (JMS), BigQuery, Microsoft Azure Service Bus, Microsoft OneNote, Mongo DB, Salesforce Pub/ Sub, Shopify, etc
  - New design guidelines to ensure upgrade readiness of Groovy Scripts (Camel 3 to Camel 4)
• Migration & Modernization
  - Generate ABAP proxy in the backend without any dependency on PI
  - Edge Integration Cell: Local OData API access, HANA DB, Shared Kubernetes, Basis Authentication during offline mode 
  - Alerting of failed B2B messages in CALM
  - Automatic B2B interface creation based on Payload
• API-centric & Event-driven integration
  - Lightweight adapter in the context of Advanced Event Mesh for small, light-weight, event-driven integration with non-SAP applications
  - Migration support from EM to AEM

Agent-ready Application: IPaaS & AI Market Evolution & Trends

• Agent iPaaS
• Agent Integrations
• Agent Orchestration
• AI TRiSm (trusted relationship governance of the AI agents

SAP Integration Suite to become the trusted AI Integration Fabric: IS is evolving to become a trusted AI Integration fabric

Some of the use cases are:

• Integration for AI (to make agentic interactions & orchestration to make applications agent-ready)
• MCP Gateway
• Agent Orchestration
• AI Gateway
• Agent Identity Verification
• LLM connector
• AI for Integration (features in IS)
• Joule
• Anomaly detection
• API traffic predictions
• Script Optimization
• Configuration Agent

2026 SAP Integration Suite Strategic Outlook:

• Leveraging Joule for building Integration flows
• MCP enablement for APIs
• Migration Agents for Java Mappings & adapter modules
• AEM events in developer hub
• 15+ new third-party adapters including Adobe Sign, Google Suite, Oracle, OFTP2, Salesforce Service & Marketing, Cloud, Oracle Eloqua
• Joule Skills & AI Agents in SAP Business Accelerator Hub
• B2B capabilities in Edge Integration Cell

Roadmap for SAP Integration Suite:

• Artificial Intelligence
  - Integration flow design validation
  - Joule based generation of iflows
  - MCP for agentic AI
  - Migration agent for adapter modules, Java mapping
  - Configuration Agent
  - Payload-size anomaly detection
• Business Accelerators
  - More connectivity options, meaning, more adapters like Google Drive & Sheets Microsoft Excel & Outlook, OFTP2, RosettaNet, Salesforce Service Cloud, etc
  - Support for publications of Joule Skills & Agents in Business Accelerator Hub
  - Commercial module for Partner Content. Consumers/Customers with a licence to Partner Content can now use it. Currently, customers can copy and use it for free, but from now on, the IP rights are protected, so you can use it only if you have a licence.
• Migration & Modernization
  - Mass migration from PO to IS
  - Edge Integration Cell: customer-managed cloud connectors, offline mode support for 48 hours, B2B capabilities, multiple instances of EIC per Kubernetes Cluster
  - SAP IS data centers in Australia, Germany, India, Japan, US.
• API-Centric & Event-driven integrations
  - AEM health monitoring in SAP Cloud ALM
  - Auto discovery and publications of events from AEM to Developer Hub as single catalog for APIs and Events
  - Consumption of events through Developer Hub

[dinesh_svrs]

Thanks for the wonderful summary @Sookriti_Mishra ! 

[zfiori]

Hi Community,

"

• Artificial Intelligence
  - Joule copilot-based discovery and reuse of artifacts were made available in Business Accelerator Hub
  - Generation of Integration flow steps 
  - Groovy script optimization
  - API anomaly detection
  - API traffic prediction for usage and trend
  - AI adapter
• Business Accelerators
  - Additional non-SAP adaptors like, AI, Google, BigQuery, IBM MQ (JMS), BigQuery, Microsoft Azure Service Bus, Microsoft OneNote, Mongo DB, Salesforce Pub/ Sub, Shopify, etc
  - New design guidelines to ensure upgrade readiness of Groovy Scripts (Camel 3 to Camel 4)
• Migration & Modernization
  - Generate ABAP proxy in the backend without any dependency on PI
  - Edge Integration Cell: Local OData API access, HANA DB, Shared Kubernetes, Basis Authentication during offline mode 
  - Alerting of failed B2B messages in CALM
  - Automatic B2B interface creation based on Payload
• API-centric & Event-driven integration
  - Lightweight adapter in the context of Advanced Event Mesh for small, light-weight, event-driven integration with non-SAP applications
  - Migration support from EM to AEM "

Thanks for your selfless sharing, it really help us a lot.

🙂

Regards,

ZFiori.

[Sookriti_Mishra]

@zfiori , thanks for the comment. this really means a lot. 

@dinesh_svrs , glad to know you found this helpful. 

[chichilinaveen]

I wonder if they have a feature to display the trace only for failed messages. SAP, are you listening? This would be a great option if sap can look into this feature.