Analyzing the Updates of SAP Integration Suite

With an ERP Clean Core strategy, you can ensure that your company benefits from the latest release state as well as cloud-compliant extensions and customizations with minimal changes.

By standardizing processes and data underlying ERP operations, your company can leverage more best practices and make adjustments where they are essential for differentiation from other providers. Your benefits in a nutshell:

• Increase your IT efficiency and reduce risks for your company.
• Optimize decision-making and implementation of measures with improved data quality.
• Accelerate innovation through regular upgrades and powerful development tools.

Organizations rely on IT to provide the right capabilities to drive strategy. IT must deliver necessary capabilities while also maintaining organizational agility. The key objective of IT is to grow an organization’s competitive differentiation by providing the business with the necessary capabilities from the right technology. Historically, this led to variation directly in ERP systems – of data, processes, integrations, extensions and ultimately the code. In some cases this was necessary; providing business-critical capability not present in standard or integrating disparate systems. In other cases, changes that were introduced did not deliver valuable outcomes. Whether necessary or unnecessary, the way in which standard functionality was extended sometimes introduced technical debt requiring significant effort to maintain. Now, changes in both the business and technology landscape are forcing organizations to address legacy complexity. Disruption across global supply chains, customer preferences, and employees means businesses must adapt quickly to changing requirements. Advancements in technology mean that new capabilities are available at an accelerated pace. Significant technical debt limits the ability to adopt new technologies – 10 to 20 percent of the technology budget dedicated to new products is diverted to resolving issues related to tech debt – thereby limiting the ability to respond to new business requirements.

SAP considers six dimensions when discussing the core of an organization. These technical and procedural considerations interact to provide the capability to your business so you can deliver outcomes.

Through the course of running the business and adapting to new requirements, variations are often introduced on each of these. However, to maximize cloud readiness, organizations must strive to keep each of these components as clean as possible.

Let’s take a look at a blog post, where you can learn why the renaming aligns with the function of the hub:

"The SAP API Business Hub has grown in scope, visitor persona, and content types. SAP customers, prospective customers, and consultants looking to accelerate their adoption and implementation often visit for prebuilt artifacts, templates, APIs, and events but they also find Business Processes, CDS views, BAdIs too, and with SAP Build Content also on the roadmap, the time was ripe to find a new name for that was better aligned to the function.

The goal of SAP API Business Hub from the very start was to offer accelerators by which customers derive value in the shortest time. While the initial focus was on integrations, then APIs, and with time new content types are being added like business processes, SAP BTP for the ABAP environment, SAP Build, and many more in the pipeline, it seemed prudent to align the name with the function than technology. Another way of seeing this is that any piece of content whether reusable or a template for, for example, an integration flow, a workflow, or an API has relevance in multiple dimensions like technology, industry, product.

To tell the whole story we need to describe the one point at which all this converged and that was the Customer and our purpose which is to speed up the customer's time to value. Hence the change to SAP Business Accelerator Hub which encompasses the goal to be achieved and its value to our users." SAP API Business Hub is now SAP Business Accelerat... - SAP Community

Default design

effective March 2024, the new design of the ABHE will become the default design.

The classic design of the ABHE will be deprecated in June 2024, you’ll still be able to toggle between the new and old design until June 2024 using the Set Default Design feature in the Site Editor.

Auto-Registration

of developers to ABHE. If the AuthGroup.API.ApplicationDeveloper role is directly assigned to developers by the BTP Cockpit Admin, they will get automatically registered as an application developer upon first time login.

Manage External Content

An option in the Enterprise Manager enables the visibility of Business Data Graphs (BDGs).

The hybrid deployment model of Edge Integration Cell enables you to:

• Design and monitor your integration content in the cloud.
• Deploy and run your integration content in your private landscape.

Edge Integration Cell supports the following use cases:

Security or compliance use cases

In many enterprises, sensitive data must be managed and controlled inside the enterprise's firewall. In addition, there could be strict architectural restrictions and you want to keep your data within your private landscape.

Getting a migration path for SAP Process Integration customers

SAP Process Integration is used by many customers for ground-to-ground integration scenarios. Edge Integration Cell allows these customers to benefit from the newest innovations that come with SAP Integration Suite, with the option to design and monitor integration content in the cloud and deploy and run their scenarios exclusively in their private landscapes.

In both cases, it is recommended to use a hybrid integration approach for enterprise-wide connectivity. For more information about the supported features and limitations of Edge Integration Cell, see: Edge Integration Cell Runtime Scope.

It is also important to notice that Edge Integration Cell is a runtime only, so it needs to be deployed on a Kubernetes platform in your private landscape, so either on private cloud or on premise. For this you have different options as seen on the picture above: If you want to set it up in a private cloud environment, then it is using the Microsoft Azure Kubernetes Service (AKS), or Amazon EKS. If you would like to run it as an on premise runtime with your on premise, you can use SUSE Rancher as your Kubernetes platform and deploy the Edge Integration Dell there.

This brings this capability of running your integration scenarios or manage your APIs within your private landscape.

High Level Architecture

When looking at the high-level architecture of Edge Integration Cell, there’s a dependent service called "Edge Lifecycle Management", which is used to manage the lifecycle of Edge Integration Cell. This is needed to manage the upgrades and to also manage your Kubernetes cluster. It also comes with an inbuilt cloud connector as part of the initial setup, so you don’t have to install one separately. Once this Edge Integration Cell set up is done and deployed on your Kubernetes cluster, then you can use the SAP Integration Suite tenant to design and monitor your integration scenarios. A detailed overview can be seen in the following figure:

• Search of an existing flow step in integration flow editor based on type, name, and ID.
• Search would be available in read and edit mode of integration flow.
• Extended existing search toolbar to cater to both add step and search existing step in integration flow editor.
• Enable you to navigate from the Monitoring and Inspect screen to view the deployed artifact and search the flow steps.

• Headers and properties in a content modifier are processed from top to bottom.
• You can now move the properties and headers in a content modifier step up and down to decide the order of processing them.
• If you like to process the header or properties in a certain order, first add all your entries and then use the "move" actions to sort them in the order of your choice. See: Define Content Modifier.
• You can also find more information here.