General API Updates

Objective

After completing this lesson, you will be able to identify Integration and API Updates to SAP Commerce Cloud

At-Least-Once Delivery for Webhook Events

At-least-once delivery (ALOD) automatically resends failed outbound webhook events to ensure that they are delivered successfully at least once. This provides a more reliable delivery mechanism for mission-critical events to ensure that vital information arrives at its intended destination.

Note

To run tests locally for at-least-once delivery (ALOD) webhook events, install Microsoft Azurite on your local machine. For more information, see Microsoft Azurite.

For more information, see the following topics:

Why?

ALOD provides a robust delivery mechanism for outbound events with persistent storage for retrying failed events up to 24 hours. It also includes dead-letter queue (DLQ) storage for messages with repeated failed attempts. These enhancements to eventing ensure that your outbound messages are received at least once, or stored and accessible in the DLQ if undeliverable.

Data Hub Updates

1. New Associated User Field in Backoffice for Data Hub

You can now associate a specific employee user with a Data Hub client using Backoffice.

For more information, see Tutorial: Defining a Data Hub Adapter OAuth Client.

(When Data Hub publishes items to SAP Commerce Cloud, the generated ImpEx runs as an anonymous user, which can causes issues. With the new Associated User field, you can associate an employee user, who is belongs to the adminGroup, to existing Data Hub clients. This way, the ImpEx runs under that Associated User.)

2. Data Hub V2 Default Endpoint

A new v2 endpoint backed by the Spring Web model-view-controller (MVC) is available for Data Hub since the June 2024 update release (2211.24). Both v1 and v2 are available for any new Data Hub deployment, and the default setting is updated to v2 starting with the December 2024 update release (2211.32).

Next lesson