SAP TechEd 2021: Watch the SAP Integration Suite session recordings and discover the SAP Integration Suite FAQs

In this blog post you will get an overview of the questions asked during our SAP Integration Suite sessions at SAP TechEd 2021, including their answers.

SAP Teched 2021 was a fantastic experience for our customers and partners as well as a great success for us. We have had over 2,000 session attendees at our SAP Integration Suite sessions, providing fantastic feedback and asking very good questions.

If you missed our SAP Integration Suite sessions, you could still register and watch the recordings of our sessions here:

We got over 100 great questions during these sessions from customers and partners. The hottest topics were the following:

The most interesting questions and answers you can find here:

Q: What is CPI currently called? Will CPI be called SAP Integration Suite going forward?

  • A: The old brand name SAP Cloud Platform Integration is an older product generation. SAP Integration Suite is the new product name with a lot more capabilities. Cloud Integration, which is an evolved version of older SAP Cloud Platform Integration, is one of the capabilities, apart from SAP API Management, Open Connectors, Integration Advisor, SAP Event Mesh, SAP Data Intelligence, and Trading Partner Management.

Q: What kind of skillset or programming language is required to use SAP Integration Suite?

  • A: We are making Integration Suite easy and user-friendly with many low-code, no-code options, like low-code API development. Also, we offer a lot of prepackaged integration content targeted for business users with limited or no integration experience. And then, we also have other features like scripting for which specific programming skills are required, like knowledge of XML/XSLT and Groovy Script.

Q: Is SAP Integration Suite running on Private cloud?

  • A: It is running only on Public Cloud, like Microsoft Azure, AWS, Alibaba Cloud, and since Dec 2021, also on Google Cloud Platform – not on Private Cloud.

Q: If I intend to use only SAP Integration Suite, does it matter which cloud provider I choose, AWS or Azure?

  • A: In general, it doesn’t. Kindly note there are the following two exceptions:
    • The Open Connectors capability is not available on Alibaba Cloud and is not EU Access compliant.
    • EU Access is currently available on AWS in Frankfurt only.
  • For further details, please see the SAP Discovery Center.

Q: We are in Private Cloud ECC, and we would like to see if we can use SAP Integration Suite as a middleware. Is that possible, or should we go with SAP PI/PO?

  • A: In general, you can use SAP Integration Suite as a Middleware. Using the Cloud Integration capability of SAP Integration Suite, you will be able to integrate with Private Cloud.
  • However, kindly view the SAP Integration Architecture Guide for Cloud and Hybrid Landscapes, particularly the chapter on Process Integration, including the recommendations when to use the Cloud Integration capability of SAP Integration Suite and when to use SAP Process Orchestration.

Q: How important is it for SAP Integration Suite to be on the same cloud provider as SAP and other cloud-run apps?

  • A: It doesn’t matter which Cloud Provider your SAP Integration Suite and apps run on. In general, it is recommended to run SAP Integration Suite in a data center that is near to the majority of your applications, mainly to avoid network latency.

Q: Instead of one tool, why is SAP adding multiple tools for Integration? Will SAP combine all and make one tool?

  • A: Integration has many dimensions and semantics like process integration, message-based integration, event-driven integration, API-based integration, etc. We offered this in the past as separate services; now, we combined them all as one SAP Integration Suite. You can purchase different licenses, including different options and service plans. (SAP Discovery Center – Integration Suite (cloud.sap)). Additionally, SAP plans to integrate the integration services of SAP Integration Suite tighter, e. g. through a harmonized tooling across SAP Integration Suite. You can find further information about the planned harmonized user experience on the public Roadmap for SAP Integration Suite, particularly under the term Integration Studio.

Q: Is SAP Integration Suite synonymous with Smart Data Integration, or are they different?

  • A: SAP Smart Data Integration is a service specific to SAP HANA Database for Data Integration scenarios and belongs to the data integration capability of SAP Integration Suite.

Q: Where does the SAP Cloud Platform Integration for Data Services (CPI-DS) tool fit into SAP Integration Suite? Where are data transformations (e.g., joins, filters, etc.) applied in SAP Integration Suite? Has the SAP Data Intelligence capability of SAP Integration Suite replaced CPI-DS?

  • A: The data integration capability SAP Cloud Platform Integration for data services is called SAP Cloud Integration for data services now, and it is included in the data integration capability of SAP Integration Suite, i. e. SAP Cloud Platform Integration for data services is still available as SAP Cloud Integration for data services and mainly used in the context of Integrated Business Planning (IBP) integration. Furthermore, SAP Data Intelligence belongs also to the data integration capability of SAP Integration Suite. You can find further details about the data integration capabilities of SAP Integration Suite, including the use cases and use case patterns in the Data Integration section of the SAP Integration Architecture Guide for Cloud and Hybrid Landscapes.

Q: Is there a difference in Neo and Cloud Foundry (CF) regarding SAP Integration Suite?

  • A: One of the key differences is that on SAP BTP, Neo environment, the integration services, such as SAP Cloud Integration and SAP API Management, are single, loosely coupled services, while on SAP BTP, Cloud Foundry environment, the integration services are bundled licensing-wise and functionality-wise under one umbrella, namely SAP Integration Suite. SAP Integration Suite is based on SAP BTP, Cloud Foundry environment, and available on hyperscale environments, such as Microsoft Azure, AWS, Alibaba Cloud, and since Dec 2021, also on Google Cloud Platform. Some of the advantages of SAP Integration Suite running in a multi-cloud environment are for example:
    • Simplified licensing
      • Simplified consumption based on common metric (messages) with unlimited asynchronous JMS message queues
      • Unlimited B2B Libraries
      • Free SAP to SAP integration messages (for predefined, unmodified integration content)
    • Operations
    • Features and functions
      • Central Launchpad with one-click provisioning, role management, launch, and monitoring experience
      • Service Now and Workday adapters and Integration Packs (for standard and premium editions)
      • Trading Partner Management to centrally manage customers, vendors, and logistics providers for B2B/EDI exchanges.
      • B2B Monitoring
    • SAP Integration Suite Roadmap: More and more new capabilities will be offered for SAP Integration Suite on multi-cloud environments and not on SAP BTP, Neo environment anymore, such as
      • Hybrid deployment option
        • On-premises deployment option for hybrid integration scenarios for SAP API Management, Cloud Integration, Event Broker
        • Long-term replacement of integration scenarios supported with SAP Process Orchestration
      • Additional adapters:
        • Dropbox, Microsoft Azure, Microsoft 365, RabbitMQ, Splunk, Slack, …
      • Integration assessment service based on SAP Integration Solution Advisory Methodology
      • Integration Studio with convergence of development environment for SAP Integration Suite
      • Data and message type editor

Q: Until when will the Cloud Integration capability of SAP Integration Suite (before: SAP Cloud Platform Integration, CPI) on Neo be available?

Q: Will additional nodes be added automatically if volume increases, or do we need to request SAP during high load scenarios?

  • A: Yes, additional nodes will be added automatically. If you see high volumes coming up, like for Black Friday, we recommend you create a ticket on the support component LOD-HCI-PI-OPS to inform SAP in advance and ensure fluent processes.

Q: Is it also the same for Cloud Foundry?

Q: Does SAP Integration Suite support high latency scenarios? What is the typical response or execution time for pass-through async/sync scenarios?

  • A: Yes, SAP Integration Suite supports high-performance scenarios. Many customers process several millions of messages every day with SAP Integration Suite.
  • The response times depend on the complexity of integration scenarios.

Q: Do you have any pointers for testing the integrations, including APIs?

  • A: Yes, we have OData APIs for SAP Integration Suite, via which you can test your integration scenarios. Furthermore, we have an integration test capability within the integration flow designer.

Q: Is there any scalability and performance/sizing guide planned for SAP Integration Suite?

  • A: Currently, there is no performance or sizing guide planned for SAP Integration Suite. SAP Integration Suite scales very well; many customers process several millions of messages every day with SAP Integration Suite. Nevertheless, if you see high volumes coming up, like for Black Friday, please create a ticket on the support component LOD-HCI-PI-OPS to inform SAP in advance.

Q: If any iFlow or API is handling massive data, can we dedicate nodes for this process so that others will not impact on performance?

  • A: This is currently not possible. However, SAP Integration Suite scales very well; many customers process several millions of messages every day with SAP Integration Suite. Nevertheless, if you see high volumes coming up, like for Black Friday, please create a ticket on the support component LOD-HCI-PI-OPS to inform SAP in advance.

Q: Does auto-scaling of Cloud Foundry also apply to SAP Integration Suite?

Q: Which are the details for the High Availability (HA)/ Data Center (DC) roadmap that is planned?

  • A: We plan to support improved high availability via multi-availability zones. Additional details you can find on the SAP Integration Suite roadmap under: “High availability of design time across multiple availability zones” and “High-availability support across multiple availability zones”.
  • An availability zone is basically an isolated building served by an own set of network devices, power supply, etc. As part of the multi-availability zones concept, in general, three availability zones, which are in close distance, are connected with each other. In each availability zone, the same set of SAP Integration Suite tenants is running in an active-active mode. Furthermore, the multi-availability zones share the data of the SAP Integration Suite tenants synchronously, which is ensured without latency through the close distance of the multi-availability zones. If one availability zone would experience a service disruption, one of the other two availability zones would automatically take over and ensure the continuous operations of the SAP Integration Suite tenants.

Q: Is the High Availability (HA) setup available on Multi-Cloud, Neo, or both?

  • A: High Availability will be available on any Multi-Cloud (CF) data center and the “SAP BTP, Neo environment” data center in Frankfurt.

Q: Where can I learn more about SAP Integration Suite?

Q: Any Plans for video series for learning SAP API Management, SAP Event Mesh, Hub. Etc?

  • A: We are creating new learning materials, including, e.g., videos, missions, demos, etc., regularly. Kindly discover our latest OpenSAP course: Accelerate Enterprise Integrations with SAP Integration Suite, which also includes some information on SAP Event Mesh with a focus on asynchronous messaging and SAP API Management.

Q: What are the plans for the B2B Add-On? Is there support with true EDI (ANSI X12, EDIFACT)?

  • A: B2B is already supported today, such as EDI converter, ack handling, archiving, support for AS2 adapter, and Integration Advisor to build message implementation. Furthermore, several B2B libraries are available for different B2B standards, such as ANSI X12 and EDIFACT. Mapping guidelines are also a key component of the B2B/EDI support. Additionally, Trading Partner Management to centrally manage trading partners, as well as B2B Monitoring, are available in SAP Integration Suite.

Q: Is there any accelerator planned to migrate B2B integration from SAP PI/PO to SAP Integration Suite?

Q: Are there any productive use cases implemented for B2B integration using SAP Integration Suite and Integration Advisor?

Q: Is the Integration Advisor delivered as part of the SAP Business Technology Platform (SAP BTP)?

  • A: The Integration Advisor is a capability of SAP Integration Suite, and SAP Integration Suite is a service on SAP Business Technology Platform.

Q: In the Cloud Integration capability of SAP Integration Suite, we can’t create data types. Also, in the Integration Advisor capability, we can’t do the complex mapping (For this again, we have to come to Cloud Integration). Will SAP simplify this?

Q: Can the Digital Integration Hub be leveraged to support EDI with non-SAP systems as well?

  • A: Yes, the Integration Advisor capability of SAP Integration Suite, which is the foundation of a Digital Integration Hub, will help you generate and provide proposals for mappings, for example, for integrating non-SAP systems leveraging EDI as B2B standard.

Q: Where can I find the cost details for using SAP Integration Suite?

Q: Is SAP Integration Suite part of SAP BTP or a product that has to be licensed extra?

  • A: SAP Integration Suite is one of the many services on SAP BTP. You can find further information about the licensing options of SAP BTP and SAP Integration in the SAP Discovery Center – Services.

Q: Within the SAP BTP free tier, does the SAP Integration Suite trial version provide the Kafka adapter available for doing Process Orchestration?

  • A: Yes, this is correct.

Q: Will Signavio be part of SAP Integration Suite or still be a separate offering?

  • A: SAP Signavio is a separate offering to SAP Integration Suite.

Q: For those of us who haven’t our SAP S/4HANA in AWS GovCloud (US) (“NS2”) due to security requirements, is SAP Integration Suite available to us? And is it limited to US person support only?

  • A: SAP Integration Suite is available for AWS GovCloud (US) but does not include the Open Connectors capability. SAP Integration Suite on AWS GovCloud (US) has the same support as other offerings in AWS GovCloud (US), with US persons only.

Q: With SAP Integration Suite Premium Edition, is there any limit to the number of calls with SAP Alert Notification service and any limit on the number of internal JMS queues?

Q: Is there a plan to create and release an on-premise version of SAP Integration Suite for those who have no plan to move to cloud in the future?

  • A: The hybrid deployment option is planned along with the Roadmap for SAP Integration Suite. With the hybrid deployment option of SAP Integration Suite, you can integrate on-premise applications with each other via an on-premise deployment option of SAP Integration Suite. Kindly note that the configuration and monitoring of the hybrid deployment option of SAP Integration Suite are in the cloud; we plan to offer OData APIs for on-premise monitoring and operations.

Q: Is Integration Cell the same as the hybrid deployment option?

  • A: Yes, Integration Cell was the name of the hybrid deployment option of SAP Integration Suite in the early internal development process.

Q: Can you please give more information regarding the hybrid deployment option? What does it mean? Will it be a container with Cloud Integration and API-Management capabilities to be deployed on-premise?

  • A: The hybrid deployment option is an on-premise agent for hybrid integration scenarios for SAP API Management, Cloud Integration, and Event Broker. It will be an on-premise runtime based on container technology to support on-premise to on-premise integrations. Kindly look at the “Hybrid deployment option” on SAP Integration Suite Roadmap.

Q: Will the hybrid deployment option be part of the SAP Integration Suite licenses or a separate license?

  • A: The hybrid deployment option will be included as an optional component of SAP Integration Suite licenses. The exact details are not available yet and will be published as soon as the hybrid deployment option is available.

Q: Will message numbers of the hybrid deployment option increase license costs?

  • A: Message numbers will probably be counted and relates to your license service plan. Further details about the license metrics of the hybrid deployment option will be published as soon as the hybrid deployment option is available.

Q: When is the hybrid deployment option planned?

Q: Is there some place to go and see a detailed technical overview of how to install the hybrid deployment option of SAP Integration Suite?

  • A: The hybrid deployment option will be an on-premise runtime based on container technology and need to be installed on a SAP BTP, Kubernetes environment cluster maintained by customers. Further details about the installation requirements will be published as soon as the hybrid deployment option of SAP Integration Suite is available.

Q: Is SAP PI/PO required for the hybrid deployment option?

  • A: No, the hybrid deployment option of SAP Integration Suite does not require SAP Process Integration/SAP Process Orchestration.

Q: If I build Cloud Integration artifacts using SAP Integration Suite now and use SAP PI/PO as runtime, will it be possible to migrate to the hybrid deployment option without any rework?

  • A: Yes, there will be full integration flow compatibility. For example, you can deploy the same integration flow you designed with SAP Integration Suite on SAP Process Integration/SAP Process Orchestration today or/and on the hybrid deployment option of SAP Integration Suite in the future.

Q: Will the hybrid deployment option be available through SAP PI/PO 7.5 Cloud Integration runtime or as a separate runtime?

  • A: The hybrid deployment option will be an optional component of SAP Integration Suite, i.e., independent of SAP Process Integration/SAP Process Orchestration.

Q: Are the hybrid deployment option and on-premise integration available now, or is that in the future?

  • A: You can integrate cloud to on-premise systems with SAP Integration Suite today. On-premise to on-premise integrations can also be done through the cloud, i. e. via SAP Integration Suite. The hybrid deployment option for SAP Integration Suite is planned along with the Roadmap for SAP Integration Suite.

Q: Will the hybrid deployment option work from SAP Integration Suite on Neo?

  • A: The hybrid deployment option of SAP Integration Suite is not planned to be available on SAP BTP, Neo environment. The hybrid Deployment option will be offered as part of SAP Integration Suite, which is available on multi-cloud environments running on Hyperscalers like Microsoft Azure, AWS, Alibaba cloud, and since Q4/2021 Google Cloud Platform.

Q: Is the hybrid deployment option mainly used for IT security or bandwidth/performance reasons?

  • A: The main use cases for the hybrid deployment option are:
    • On-premise to on-premise integrations
    • API-led integration on-premise, such as execution of API policies & mediations on-premise.
    • Expose business events from SAP on-premise applications to SAP Event Mesh and/or third-party event brokers

Q: As per SAP roadmap, the future integration tool will be SAP Integration Suite, and there are guides released to migrate from SAP PI/PO to SAP Integration Suite. Do we need to migrate SAP PI/PO to on-premise SAP Integration Suite with the hybrid deployment option?

  • A: For the migration from SAP Process Integration/SAP Process Orchestration to SAP Integration Suite, you can start today already considering the following best practices:
    • Move cloud-to-cloud and ground-to-cloud integration scenarios wherever possible to SAP Integration Suite.
    • Move your pass-through integration scenarios to the SAP API Management capability within SAP Integration Suite, applying security policies, traffic policies, and access controls to your APIs.
    • Start moving your existing integration scenarios to SAP Integration Suite wherever possible, and completely migrate to SAP Integration Suite once the hybrid deployment option is available.
    • Leverage the flexible design time and runtime of the integration suite to migrate your integration-centric scenarios modeled with ccBPM (cross-component of SAP Business Process Management) in SAP Process Integration dual-stack to the cloud integration runtime inside SAP Process Orchestration.
    • Reuse existing interfaces and mappings from SAP Process Integration / SAP Process Orchestration.
    • Check out integration flow guidelines and patterns explaining how to design and build enterprise-grade integration flows in a robust fashion and describing how to implement commonly used enterprise integration patterns, for example, content-based routing, content enricher, splitter, aggregator, scatter-gather, …
  • You can find further details about the migration from SAP Process Integration/SAP Process Orchestration to SAP Integration Suite in the Migration Guide and the blog post [ Blog Series ] Moving integration artifacts from SAP Process Orchestration to Integration Suite | SAP Blogs.

Q: Will the on-premise SAP PI/PO be migrated to the SAP Integration Suite going forward?

  • A: The customer can choose to migrate from SAP Process Integration/SAP Process Orchestration to SAP Integration Suite already today. A migration guide is available to help you transition from SAP Process Integration/SAP Process Orchestration to SAP Integration Suite. There are many benefits to moving to SAP Integration Suite; you can find the value proposition of SAP Integration Suite and the reasons why you should move to SAP Integration Suite described in the migration guide values here. Moving forward, SAP Integration Suite will be the logical successor of SAP Process Orchestration. Watch out for the Roadmap: SAP Road Map Explorer. Additionally, a hybrid deployment option is planned along with the Roadmap for SAP Integration Suite.

Q: Can we use SAP Integration Suite for on-premise to on-premise integration?

  • A: Several on-premise to on-premise scenarios are already supported today with SAP Integration Suite. However, additional scenarios will be supported with the hybrid deployment option, planned along with the Roadmap for SAP Integration Suite. With the hybrid deployment option, an on-premise runtime will be offered to support on-premise to on-premise scenarios without the need to integrate through the cloud.
  • For further details, kindly view the SAP Integration Architecture Guide for Cloud and Hybrid Landscapes, particularly the chapter on Process Integration, including the recommendations when to use the Cloud Integration capability of SAP Integration Suite and when to use SAP Process Orchestration.

Q: My client doesn’t allow data in the cloud for security reasons – what options will they have when SAP PI/PO is end of life?

Q: When is SAP planning to release the migration tool from SAP PI/PO to SAP Integration Suite?

Q: Is there any news about using a sort of pipeline functionality in SAP Integration Suite that is today core to SAP PI/PO?

  • A: The modeling and runtime of Cloud Integration are much more flexible than the rather static pipeline and runtime of SAP Process Integration/SAP Process Orchestration. All Enterprise Integration Patterns supported on SAP Process Integration/SAP Process Orchestration are supported on Cloud Integration capability of SAP Integration Suite. Furthermore, the Cloud Integration capability of SAP Integration Suite also supports retry handling as well as the Quality of Service “Exactly Once”; both of these functions are implemented using JMS queues.

Q: Why is SAP not supporting the Retry approach in Cloud Integration capability of SAP Integration Suite same as SAP PI/PO, and we need to use JMS queues or Datastore and create additional flows to achieve such requirement?

  • A: SAP Integration Suite has a flexible pipeline where you have more control over building your orchestration compared to SAP Process Integration/SAP Process Orchestration, which has a fixed pipeline. This means that you need to explicitly model scenarios for retry.
  • While SAP Process Integration/SAP Process Orchestration and Cloud Integration capability of SAP Integration Suite are cousins and follow many similar patterns, they are not intended to be the same product. The Retry approach will mature as time goes on, but there are many benefits to JMS queues for guaranteed delivery, including performance in the cloud, which is why SAP chose it as a strategic investment for now. Expect more developments in the future.

Q: Can you provide more input (links, docs, tutorials) on migration from SAP PI/PO to SAP Integration Suite?

Q: Is there a plan to make all Monitoring features on SAP PI/PO available in SAP Integration Suite?

Q: With SAP Integration Suite, customers look for a better end-to-end interface monitoring dashboard out-of-the-box. Do you have any updates on this topic?

Does SAP Integration Suite have a queuing capability?

Q: Is there any change planned for SAP Ariba integration with SAP ERP Central Component (SAP ECC) or SAP S/4HANA? Will the Ariba integration tool SAP Ariba Cloud Integration Gateway (SAP Ariba CIG) eventually be expected to flow through SAP Integration Suite? Or will SAP Ariba continue to use SAP Ariba CIG?

  • A: SAP Ariba Cloud Integration Gateway is based on SAP Integration Suite and intended to simplify Ariba integrations. SAP Ariba Cloud Integration Gateway supports standardized integrations with SAP ERP Central Component and SAP S/4HANA. For any breakout scenarios and non-SAP integrations, you can leverage SAP Integration Suite. SAP Integration Suite is the all-encompassing comprehensive integration platform for SAP to SAP and non-SAP integrations. SAP Integration Suite plays a key role in integrating SAP Ariba and our SAP S/4HANA procurement apps. SAP Ariba Cloud Integration Gateway will continue to be standard for SAP ERP Central Component or SAP S/4HANA and SAP Ariba integrations. For everything else, it will be SAP Integration Suite. You can refer to the blog here on SAP Ariba Integration Approach | SAP Blogs from my Product Management colleague @Gayathri Narayana.

Q: If SAP Integration Suite is “the universal integration platform“ from SAP, why SAP Ariba Cloud Integration Gateway (SAP Ariba CIG) is needed just only for Ariba integration with SAP ERP Central Component (SAP ECC) or SAP S/4HANA?

  • A: Think of SAP Ariba Cloud Integration Gateway as a service more than a tool that comes as ‘managed capability’ along with content like mappings. It enables simplified and fast connections with Ariba and SAP ERP Central Component or SAP S/4HANA. Many of our customers need to extend further or customize these transformations provided by SAP Ariba Cloud Integration Gateway, so we also provide some of this content as pass-through flows on SAP API Business Hub, which can be extended and run on the Cloud Integration capability of SAP Integration Suite. In this case, you will use both SAP Ariba Cloud Integration Gateway and SAP Integration Suite together.

Q: What is SAP’s preferred method to interact with Salesforce or Amazon? Is it via adapters running on top of the Cloud Integration capability of SAP Integration Suite or by using the Open Connectors capability of SAP Integration Suite?

  • A: It is the customer’s choice. Both options are provided. Open Connectors capability of SAP Integration Suite provides a harmonized out-of-the-box API strategy for multiple third-party providers. If customers want to create a seamless API strategy, Open Connectors would be preferred. Suppose you work with heavy orchestration or transformation or mapping use cases in the Cloud Integration capability of SAP Integration Suite – in that case, you may use adapters offered by the Cloud Integration capability of SAP Integration Suite. It depends on the customer’s preference.

Q: For Workday integration, I see it available in the Open Connectors capability of SAP Integration Suite as well in adapters to be downloaded. What is the recommended method?

  • A: Both choices are available for a customer to choose from. (Please see the answer above.)

Q: If we use third-party adapters provided by Rojo Consultancy (which are part of SAP Integration Suite), do we need to go to Rojo Consultancy instead of SAP in case of any issue with the adapter?

  • A: No, these adapters will be supported directly by SAP.

Q: Is JMS messaging supported now, or is that still in the future?

  • A: SAP Integration Suite already supports JMS with an unlimited number of queues.

Q: Is the JMS adapter supported with SAP Integration Suite?

  • A: Yes. The JMS adapter in the Cloud Integration capability of SAP Integration Suite is used to decouple integration flows, hence enabling async communication. To connect to a message broker, you can use, for example, the AMQP adapter.

Q: Why some non-SAP adapters are available out-of-the-box, e.g., Facebook, while critical adapters like SalesForce, ServiceNow, etc., need to be deployed separately?

  • A: We plan to harmonize the consumption experience soon addressing this.

Q: We see that integration needs to build much custom/business logic these days. Will SAP Integration Suite support Java to allow customers to write more logic in integration?

  • A: Best Practices should not have Business Logic in the integration layer. SAP’s direction is to move towards Low-Code/No-Code. So, we are limiting scripting and coding to enable such skill agnostic access to develop integrations. Groovy Script and JavaScript are still supported for custom scenarios. User-defined functions (UDFs) can be imported from Enterprise Service Repository mapping and used.

Q: Does SAP Integration Suite provide predefined IT and business reports? E. g., if a business team wants to know the total number of orders for a business division or customer?

  • A: You could use APIs to generate your reports.

Q: How does SAP Integration Suite support an event-driven architecture? E. g., broadcasting and consuming events from/to Kafka stream?

  • With the use of SAP Event Mesh in conjunction with the Cloud Integration capability of SAP Integration Suite.

Q: So, with SAP Integration Suite, we get everything we need to connect our SAP back-end solutions with a Kafka event stream?

Q: Is there any plan to have a mapping and debugging tool in SAP Integration Suite?

  • A: We already support both XSLT and graphical mapping in the Cloud Integration capability of SAP Integration Suite. There is also a possibility to debug your flow and certain flow steps in an integration flow.

Q: Do I understand right that event-driven pattern is for async scenarios, and API-driven pattern is for sync scenarios? But for which cases “Digital Integration Hub” is a preferred pattern?

  • A: That’s correct. Digital Integration Hub is targeted for scenarios where you need the following benefits:
    • Decoupling of the back-end data sources from front-end API
    • Protection of back-end systems from excessive front-end APIs
    • Modernization of legacy system following a cloud-native approach
    • Normalization of the APIs for certain domains accessing data held in multiple data sources
    • Real-time business insights and analytics
    • Responsive user experience

Q: As I understand, events and APIs are also used in the “Digital Integration Hub”. How “Digital Integration Hub” pattern is different from API- and event-driven pattern?

Q: Is SAP Integration Suite required for SAP Event Mesh, or can SAP Event Mesh be set up and used on its own?

  • A: No, SAP Integration Suite is not required for SAP Event Mesh; i. e. SAP Event Mesh can be used independently of SAP Integration Suite.

Q: Is SAP Event Mesh part of SAP Integration Suite?

  • A: As part of a comprehensive Integration platform as a service, SAP Event Mesh is one of the capabilities of SAP Integration Suite, meaning, including SAP Event Mesh, you will get full integration capabilities and a whole integration experience with SAP Integration Suite. You can experience many benefits leveraging the entire portfolio. However, SAP Event Mesh is a separate product from a licensing perspective. You can find further information about the different license options of SAP Integration Suite, including SAP Event Mesh in the SAP Discovery Center.

Q: Do we need to get a separate license for SAP Event Mesh even if we have an SAP Integration Suite license?

  • A: A separate license for SAP Event Mesh is required. You can find further information about the different license options of SAP Integration Suite, including SAP Event Mesh in the SAP Discovery Center.

Q: Any roadmap to include SAP Event Mesh license into SAP Integration Suite?

  • A: Please keep an eye on the different licensing options for SAP Integration Suite, including SAP Event Mesh in the SAP Discovery Center.

Q: Is there a complete guide with the steps to set up SAP Event Mesh?

Q: Will also the integration with SAP Event Mesh be improved?

  • A: We’ll keep developing all capabilities of SAP Integration Suite further, i. e. including SAP Event Mesh. Kindly stay tuned on the Roadmap of the SAP Integration Suite for further details.

Q: Are retries handled natively when dealing with events, or should we explicitly set up the iFlow design accordingly?

  • A: It depends on the Message Broker. In general, retries are handled by the broker, but you can control the behavior like retry frequency, etc., using the configurations.

Q: Should we set up JMS queues in SAP Integration Suite? Or is SAP Event Mesh (instead of JMS\Kafka\etc.) preferable for async scenarios?

Q: As a partner, how do we build Open Connectors so that customers can easily access them on the SAP catalog?

Q: Is the Open Connectors capability of SAP Integration Suite part of the free tier? Do we need to take an additional licensing to do this?

  • A: Yes, in general, the Open Connectors capability of SAP Integration Suite is part of the free tier offering. Kindly note that the licensing of the Open Connectors capability of SAP Integration Suite depends on your service plan, mostly it is available for nearly all service plans, but there are some exceptions where Open Connectors capability of SAP Integration Suite is not available, e. g. in AliCloud, China – Shanghai region, and Frankfurt – EU Access. Kindly look into SAP Integration Suite licensing and pricing here: SAP Discovery Center – Integration Suite (cloud.sap).

Q: What about SAP API Management positioning in the Gartner Quadrant?

  • A: SAP made the biggest move in the Gartner Magic Quadrant for SAP API Management, so we are almost at the edge of being a leader. Next year we aim to become a leader :-).

Q: What is the API Business Hub Enterprise?

  • A: It is a central API catalog for application developers which is API Gateway agnostic and can list APIs from SAP and non-SAP API Gateway. The API Business Hub Enterprise offering is a rebranding of the Developer Portal, which includes all the existing functionalities of the Developer Portal in addition to the listed values in the following blog post: API Business Hub Enterprise | SAP Blogs. API Business Hub Enterprise is available with SAP Integration Suite and SAP API Management native on multi-cloud environments.

Q: Do you have any best practices on SAP API Management security management?

Q: In which integration pattern mentioned SAP PI/PO is integrated?

  • A: Integration patterns are general and can be more or less implemented with integration middleware, such as SAP Process Integration/SAP Process Orchestration or SAP Integration Suite. So, you can also implement these patterns using SAP Process Integration/SAP Process Orchestration.

Q: Is the Event-driven pattern available in SAP PI/PO?

  • A: Yes, you can implement an event-driven integration pattern in SAP Process Integration/SAP Process Orchestration.

Q: How can we use event integration in SAP PI/PO?

  • A: You can leverage SAP Event Mesh (with Webhook) with SAP Process Integration/SAP Process Orchestration to achieve the same.

Q: Are you planning to implement an API to download the runtime content?

  • A: Yes, you can already download the cloud content via the SAP Process Integration/SAP Process Orchestration tooling to the local Cloud Integration runtime. Further APIs are currently not planned.

Q: Why can we not edit or remove the UDF in the message mapping, which is imported via SAP PI/PO?

Q: Does the update of UFDs also support the external jars which are referenced in the UDF? (If yes, since when?)

  • A: Yes, currently, the update of inline user-defined functions (UDFs) is already supported. However, the import and modification of user-defined functions using function libraries and imported archives are not supported yet. Kindly stay tuned on the Roadmap of SAP Integration Suite for further details, by when the import and modification of user-defined functions using function libraries and imported archives will be offered.

In General, we recommend checking our SAP Integration Suite Roadmap regularly.

If you have further questions, please write your question in SAP Community here SAP Integration Suite Community Topic page, or here: SAP Integration Strategy topic page).

Suppose you are missing a feature or function. In that case, we have an influence portal: Influence Opportunity Homepage – Customer Influence (sap.com), where all customers and partners can write and vote for feature requests, e.g., special adapters, connectors, functions, etc., in SAP Integration Suite.

I hope you enjoyed these insights into SAP Integration Suite and its Roadmap, and this blog post with Q&A helped answer most of your questions.

Best Regards,

Milena

References:

SAP TechEd 2021: Connecting Your Enterprise with SAP Integration Suite | SAP Blogs

Accelerate Enterprise Integrations with SAP Integration Suite

Learning Journey: SAP Integration Suite

SAP Discovery Center – Integration Suite (cloud.sap)

Integration Architecture Guide for Cloud and Hybrid Landscapes Based on SAP® Integration Solution Advisory Methodology

CIO Guide: SAP’s Hybrid Integration Platform for the Intelligent Enterprise

SAP Road Map Explorer

Influence Opportunity Homepage – Customer Influence (sap.com)