Forward events from SAP Integration Suite, advanced event mesh to SAP Build Process Automation

SAP Integration Suite, advanced event mesh will be forwarding events to SAP Build Process Automation. In order to configure the secure connection between these services, you will need to create a service key for SAP Build Process Automation, which will be used by AEM to connect and deliver the event to SAP Build Process Automation service.

1. In the SAP BTP cockpit, go to Instances and Subscriptions.

   Under Instances, choose the 3 dots next to the SAP Build Process Automation instance, for example, spa-service in the screenshot below, and select

   

2. In the dialog, give the key a name, for example, spa-key.

   

   Choose Create

3. After the key is created (it will take about half a minute), choose the 3 dots next to the key and download the key.

   

   Keep it in a safe place. You will need it later in the tutorial.

A REST delivery point (RDP) is a provisioned object on an event broker service that facilitates message delivery to REST consumers. The RDP can be bound to message queues to deliver messages from those queues to REST consumers. The RDP maintains a list of REST consumers, which are identified by their remote connection information.

For this tutorial, you will use an event broker service in AEM and in it, you can create a new queue or reuse an existing queue. In the steps below you will be using a queue named EDP_BP_Created_[SAPCommunityDisplayName] but this can be something different on your end.

To learn how to configure a queue in SAP Integration Suite, advanced event mesh, you can check out this tutorial 👉 Queues and subscriptions in SAP Integration Suite, advanced event mesh

The queue will need to be subscribed to the business event that you are interested in sending to SAP Build Process Automation, for example the default/sap.s4/S4D/ce/ce/sap/s4/beh/businesspartner/v1/BusinessPartner/Created/v1 topic which is where an Business Partner created event will be published.

Note that in order for SAP Build Process Automation to be able to process the event, the event needs to follow the CloudEvents specification.

Now that you know what a REST Delivery Point is, you are ready to create a REST Delivery Point (RDP) to forward messages from the queue to a REST consumer.

1. Inside the event broker service where the queue exists, choose Open Broker Manager.

2. Choose Clients on the left-side menu.

   Choose REST.

   

3. Choose + REST Delivery Point.

   

   Enter a name, for example, EDP-SBPA-BPCreated-[SAPCommunityDisplayName].

   

   Choose Create.

   A simple configuration form will appear. No need to modify anything here – Do not enable the RDP yet, that is, leave the toggle button off.

   Choose Apply.

   

4. Once created, go to the RDP details page by clicking on the name of the RDP.

   

   You will see that there isn’t much here yet, as you haven’t configured the REST consumer details. You will do this now.

   

Now that you’ve created a REST Delivery Point, you have to specify where you want events sent.

1. Navigate to the REST Consumers tab.

2. Choose the + REST Consumer button, and enter the name, for example, SBPA_[SAPCommunityDisplayName].

   Choose Create.

   

   A configuration form will be displayed.

3. Enter the details from the SAP Build Process Automation service key created in the previous step.

   IMPORTANT: Do not enable the REST Consumer yet – leave the toggle button off.

   Enter the following:

   Field	Value
   Host	Value from service key .endpoints.api, for examplespa-api-gateway-bpi-us-prod.cfapps.[region].hana.ondemand.com
   Port	443
   HTTP Method	POST
   TLS Enabled	Yes
   Authentication Scheme	OAuth 2.0 Client Credentials
   Client ID	Value from service key .uaa.clientid, for example sb-VQ18I1VS-3226-5LF1-JVWV-760D08FHP857-3ok534d4-8562-632j-436w-0j5b0n8r4d0l!b139588 | eventing-xsuaa-broker!b####
   Client Secret	Value from service key .uaa.clientsecret
   Token Endpoint URL	Concatenate the value from service key .uaa.url, for example https://[host].authentication.[region].hana.ondemand.com, and /oauth/token
   Token Expiry Default	3600

4. Choose Apply.

   

The newly created REST consumer will be listed in the REST Consumers tab. Now you need to configure the queue that you will bind to our RDP. Events in this queue will be forwarded.

Now that you have a REST consumer configured, you can proceed to bind a queue and configure the binding for our REST Delivery Point. All events received by the queue will be then forwarded to the REST consumer you configured, once enabled.

1. Navigate to the Queue Bindings tab.

2. Choose the + Queue Binding button.

   Select the queue you previously created, for example, EDP_BP_Created_[SAPCommunityDisplayName].

   

3. Choose Create.

4. A simple configuration form will be displayed.

   In the Post Request Target field, you need to enter the path where you can send events to SAP Build Process Automation (/internal/be/v1/events). Notice that you will need to include the / at the beginning of the value.

   Enter the following details:

   Field	Value
   Post Request Target	/internal/be/v1/events
   Request Target Evaluation	None
   Replace Target Authority	No

   Choose Apply.

   

The newly created queue binding will be listed in the Queue Bindings tab. Now you need to configure a request header that is required by SAP Build Process Automation.

Now that you have a Queue binding configured, you need to set some request headers which are specific to SAP Build Process Automation.

1. In the Queue Bindings tab, select your queue binding.

   

2. Navigate to the Request Headers tab.

   

3. You will create 2 headers.

   For each, you will choose + Request Header, enter the header name, then the header value, and then choose Apply.

   Create the following headers:

   Header Name	Header Value
   Content-Type	application/cloudevents+json
   WebHook-Request-Origin	aem

   

In the request headers configured you specified the Content-Type header. You can see that its value is application/cloudevents+json. This is because SAP Build Process Automation expects events that follow the CloudEvents specification.

Now that you’ve created the request headers, you are ready to enable the REST consumer and the RDP.

You’ve configured the REST consumer and the queue binding, you can enable the REST consumer and the RDP.

First, let’s see all the objects that you’ve configured.

1. Navigate back to the main page for your RDP.

   Select the Summary tab. Here you will see all the objects and their status. Notice that the only object in an operational state is the queue you created at the beginning of the exercise.

   

2. Navigate to the REST Consumers tab, and choose the name of your REST consumer, for example, SBPA_[SAPCommunityDisplayName].

   

3. Choose the Edit button on the top right.

   

   Enable the REST consumer by toggling the Enabled setting.

   Choose Apply.

   Now you are ready to enable our RDP.

4. Navigate back to the main page for your RDP.

   Select the Summary tab.

5. Choose the Connector / RDP, for example, EDP-SBPA-BPCreated-[SAPCommunityDisplayName].

   Choose Edit on the top right, and enable the RDP by toggling the Enabled setting.

   Choose the Apply button.

   Once you enable the RDP, if you navigate to the Summary tab, you should see that all the objects are in an operational state.

   

6. Now, go to the SAP S/4HANA Cloud system and create a Business Partner.

   This will trigger a Business Partner event which you will receive in your queue.

   Check that the queue configured for the RDP is accumulating messages.

   

Now that you’ve created events and sent them to your SAP Build Process Automation tenant, create a project that can be triggered by those events.

To achieve this, you can follow the steps in the Capture Events in SAP Build Process Automation tutorial.

This tutorial completed all the configuration required for the REST Delivery Point.

1. Created a REST Delivery Point.
2. Defined an RDP REST Consumer, where you configured the details of our SAP Build Process Automation tenant.
3. Bound a queue to our RDP.
4. Added request headers to the queue binding.
5. Enabled it all.

In this tutorial, you have learned how to create a REST Delivery Point (RDP) to forward messages from a queue to a REST consumer. You used OAuth 2.0 authentication to securely deliver events to SAP Build Process Automation. Now you know a mechanism to enable systems that expose REST endpoints to “react” to events produced by an event broker service.

• Managing REST Delivery Points - link.
• REST Consumer Authentication Schemes - link.
• Integration with Advanced Mesh Service Plan for Service Cloud - link.

Things to Ponder

1. What if you would need to transform or enrich the message before sending it to the REST consumer? How would you do it?
2. Can you think of a system within your company that exposes REST endpoints and could benefit from being part of an event-driven architecture?