Validation of VMR Provisioning

When S4 creates a channel to emit events to the Solace PubSub + VMR end-point, a handshake API is called to ensure that the particular VMR is provisioned via AEM.

Prerequisites

You have an enterprise account with SAP BTP. Refer to Getting Started with an Enterprise Account in the Cloud Foundry Environment.
You have access to a global account. Refer to Getting a Global Account.

Your global account must have an entitlement to use SAP Integration Suite, advanced event mesh. Available entitlements are listed in the service table on the Entitlements page. If your global account is missing this entitlement, contact your BTP cockpit administrator and request the entitlement.
You created a subaccount. Refer to Create a Subaccount in the Cloud Foundry Environment.

Procedure

Go to your SAP BTP cockpit global account and subaccount.

If you aren't sure how to navigate in the BTP cockpit, refer to Navigate in the Cockpit.
Choose Instances and Subscriptions.
Click on Create.
Under Service, choose the service name as SAP Integration Suite, advanced event mesh and plan as aem-validation-service.
Provide an Instance name and click on Create.
Create Service Binding.
1. The instance created will be listed under Instances tab. Click on the menu and choose Create Service Binding.
2. Provide a Binding name and click on Create. The service binding is created.
3. Click on the link service binding under credentials.
4. Under the tab JSON, the handshake API end-point which should be configured at the S4 side will be present in the URI field. To configure this API at the S4 end, refer to Integrating with SAP Event Mesh Advanced Plan
  
  Note
  
  The API returns either a HTTP response status 200 OK or 400 Bad request. This is to ensure that the VMR is provisioned via AEM.

Results

The events coming from S4 reaches their AEM end-point.