
Continuing the blogpost series, we want to share with you the SAP Integration Suite innovation highlights of spring:
Probably you have seen it already, over the last days our user interface got a facelift and follows the Horizon theme with a modern, lightweight, and refreshed user experience. The icons, buttons, and texts change slightly but all functionality is still the same. Additionally, within our SAP Integration Suite home page we added a carousel that provides you with some spotlights. Enjoy the new look.
We have made a big step forward in the direction of embedded product support. This new feature assists you with a combined search across knowledge base articles and help documentation to achieve a better understanding and guides you towards a solution. Additionally, it lets you file incidents through the support platform, all in one single window. Check out the documentation.
Isolation of sensitive data for different lines of business is crucial. We have extended our access policies in that way that you can control the access in the design time not only on artifacts but also on package level. This simplifies the tenant admin’s experience while restricting access to all integration artifacts of a package at once. Access policies on artifacts released before are not disrupted. In future we will offer an overwrite option to allow package access policies to overwrite artifact access policies. Only with granted access developers can deploy, undeploy, start integration flows, or access local variables. Refer to the blogpost and to the documentation for all details.
Our design guidelines aim to model enterprise-wide integration flows in a robust fashion to safeguard the business processes. They cover different areas such as applying the highest security standards, handling errors, scripting, and performance. Now the first ones are embedded within the integration flow designer as rules and help to programmatically validate integration flows against them.
As an integration lead, you may not only learn about all available design guidelines but also enable the applicable ones on your tenants. And as an integration developer, you can validate the integration flows against the enabled guidelines and if needed improve the quality of your integration flow. Additionally, a report can be downloaded for report purposes. Be aware that currently not all design guidelines are covered by the tool. The complete list can be found in our help documentation. More rules will be added in the next increments. Check out the documentation.
You can now import message mappings from ES Repository that contains message type objects. Earlier, during the import, the message type objects were converted as WSDL files. See the documentation.
The pipeline concept is mainly addressed to existing SAP Process Orchestration customers which plan to migrate their scenarios to Cloud Integration, but it can also be generally applied to any asynchronous integration scenario. It contains a sequence of generic and scenario-specific integration flows, leverage the Partner Directory to define the message processing behaviour, use XSLT mappings to carry out the receiver determination, and handles all asynchronous scenarios with a reduced number of JMS queues. For more details read the blogpost.
You can now activate the Edge Integration Cell runtime on Google Cloud Platform. Check out the documentation and read also #3379690 to get the full list of supported regions and the future availability schedule.
As the Edge Integration Cell is updated at cloud speed you have to update your Kubernetes version monthly by using the Edge Lifecycle Management user interface. Now it is also possible to roll back to the last successful version if an upgrade or configuration modification operation fails. The option to downgrading back to a previous tried-and-trusted version is also on the roadmap. Read the documentation.
You can now create an OData API artifact using a .edmx file. This functionality enables users to easily generate and manage OData APIs by leveraging existing .edmx files. Details how to create the APIs can be found in the documentation.
Supporting our SAP Process Orchestration customers in their journey to SAP Integration Suite is one of our key investment areas. During last development takts we have released the innovations:
By introducing a new type of artifacts, Imported Archives, you are now able to import your user-defined functions (UDFs) which have a reference to imported archive objects (with XSLT or Java mappings) in Enterprise Services Repository directly into Cloud Integration. You can reuse the imported archive objects across multiple Function Libraries artifacts, which in turn are reused across multiple message mappings. Read the documentation.
As we want to increase reusability of message mapping artifacts from SAP Process Orchestration, we extended the import procedure of function library objects from the ES Repository by the execution types ALL_VALUES_OF_QUEUE and ALL_VALUES_OF_CONTEXT. Check out the documentation.
We are thrilled to announce that you can now archive the interchange payload of your transaction activities to meet your data-retention requirements for auditing purposes. This archiving feature is executed once a day. Both the payload and headers are stored as zip files on your own CMIS-compliant content management system. Refer to the documentation Creating an agreement template and Creating a trading partner agreement.
In B2B integration scenarios, you may occasionally encounter situations where certain information, such as different types of partners or currencies, is distributed across the source structure. However, there may only be one node in the target structure. To address this, the mapping guidelines editor now offers the ability to duplicate or replicate group or leaf nodes. This allows each source alternative to be mapped to one of these duplicates. See the documentation.
Additionally, we have news to tell regarding the global code value mappings. For the definition of more complex code value mapping scenarios, you may create a global code value mapping with multiple source code values to one on the target side. So, the value function now supports N:1 in addition to the existing 1:1 cardinality. Refer to the documentation.
You can now create a duplicate of an API artifact by copying it within the same package or in a different integration package within the same Integration Suite subscription. Read the documentation.
The recent update allows for the configuration of additional virtual hosts and client certificate-based authentication entirely as a self-service instead of the previously established procedure that involved creating ops tickets. This applies to the default as well as custom domains. Additionally, the keystore and trust store values can be maintained as a reference, thereby ensuring that the virtual host definitions are automatically updated whenever certificates and keys are rotated. For further details refer to the following documentation pages (this, this).
Get a better understanding how Graph can be used to compose different APIs into a single connected data graph you may walk through this tutorial.
For diagnose problems SAP Integration Suite, advanced event mesh offers you an end-to-end tracing capability for tracking an event all the way from the producing to the receiving application and it's way across one or multiple event brokers. Common OpenTelemetry backends can be leveraged for troubleshooting the error message. Read the documentation.
Since March already it is also possible not only to receive SAP S/4HANA but also SAP S/4HANA Cloud events directly in SAP Integration Suite, advanced event mesh without any intermediate hops. This is very helpful for any large SAP S/4HANA projects, where performance is crucial. Check out the documentation.
A new release 2.17.0 of the SAP Cloud Connector has been recently published and can be downloaded. With this release we’ve not only ensured the highest security levels but also worked on improving the overall user experience and functionality. See the blogpost or all the details.
Additional partner content has been published on SAP Business Accelerator Hub, our public catalog hosted by SAP to discover, explore, and test SAP and partner APIs required to build extensions or process integrations. Examples are the integration of SAP S/4HANA with Shopify published by Flexso NV; or Effective People A/S an integration to replicate employee data from SAP SuccessFactors Central to SAP Concur; and NTT DATA Business Solutions AG an exchange of application and vendor data between SAP LeanIX and SAP Integration Suite. Please check out the separate blogpost for more details.
The blog post ends with a list of links to websites that hopefully keep you up-to-dated:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
16 | |
12 | |
10 | |
10 | |
8 | |
8 | |
7 | |
6 | |
6 | |
6 |