(v1) SAP Event Mesh (old)

Step 1. Get the URLs of Your service

Please note that the instructions below are meant to quickstart Your operations with Int4 Suite Cloud Version. Some decisions below, for example to use clientId and clientSecret options, might not be fit for Your organization. Please consult Your SAP Basis and Security teams before proceeding.

Also, take a look at official SAP Documentation for these services.

https://help.sap.com/docs/event-mesh/event-mesh/use-rest-apis-to-manage-queues-and-queue-subscriptions?locale=en-US

Validate existence of Services in Your BTP tenant

Depending on Your organization security settings and Your role You might or might not have access to perform the actions below. Consult Your SAP Basis and SAP Security teams for the best person and authorization settings for completing these steps.

Navigate to Instances and Subscription in Your BTP Tenant

Look for Event Mesh related service instances. We need Event Mesh service with default plan.

If You don’t have an Event Mesh service, please validate Your entitlements for this service.

Create or use the access keys.

Once the service instance is identified, we need access keys created.

Click on the three dots at the end of respective line, and choose Create Service Key option

Now provide the necessary settings, minimal is to provide a name for the new service key.

Once the service is created, please click the name of it and note the information, as it’s going to be necessary in the next step:

{
"xsappname": "default-d1eee2de-64cf-4936-8xxxxxxxxxxxxx-service-broker-!b2436",
"management": [
{
"oa2": {
"clientid": "sb-default-d1xxxxxxxxxx68461|xbem-service-broker-!b2436",
"clientsecret": "TnpbJnHXxxxxxxxxx6obH8=",
"tokenendpoint": "https://int4xxcf.authentication.eu10.hana.ondemand.com/oauth/token",
"granttype": "client_credentials"
},
"uri": "https://enterprise-messaging-hub-backend.cfapps.eu10.hana.ondemand.com"
}
],
"messaging": [
{
"oa2": {
"clientid": "sb-default-d1exxxxxxxxxxxxxx61|xbem-service-broker-!b2436",
"clientsecret": "TnpbJnHxxxxxxxxxxxbH8=",
"tokenendpoint": "https://int4cf.authentication.eu10.hana.ondemand.com/oauth/token",
"granttype": "client_credentials"
},
"protocol": [
"amqp10ws"
],
"broker": {
"type": "sapmgw"
},
"uri": "wss://enterprise-messaging-messaging-gateway.cfapps.eu10.hana.ondemand.com/protocols/amqp10ws"
},
{
"oa2": {
"clientid": "sb-default-d1eee2de-xxxxxxxxxxxxxxbem-service-broker-!b2436",
"clientsecret": "TnpxxxxxxxxxxxxxxxxxxxbH8=",
"tokenendpoint": "https://int4cf.authentication.eu10.hana.ondemand.com/oauth/token",
"granttype": "client_credentials"
},
"protocol": [
"mqtt311ws"
],
"broker": {
"type": "sapmgw"
},
"uri": "wss://enterprise-messaging-messaging-gateway.cfapps.eu10.hana.ondemand.com/protocols/mqtt311ws"
},
{
"oa2": {
"clientid": "sb-default-d1eee2de-64cf-4936-8ac7-8bcxxxxx-service-broker-!b2436",
"clientsecret": "TnpxxxxxxxxxxxxxxxxxbH8=",
"tokenendpoint": "https://int4cf.authentication.eu10.hana.ondemand.com/oauth/token",
"granttype": "client_credentials"
},
"protocol": [
"httprest"
],
"broker": {
"type": "saprestmgw"
},
"uri": "https://enterprise-messaging-pubsub.cfapps.eu10.hana.ondemand.com"
}
],
"namespace": "int4suite/demo/em",
"serviceinstanceid": "d1eee2de-64cf-4936-8ac7-8bca3ae2cf55",
"uaa": {
"clientid": "sb-default-d1eee2de-64cf-4936-8ac7-8bca3xxxxxxvice-broker-!b2436",
"clientsecret": "TnpbxxxxxxxxxxxxxxxxxxobH8=",
"url": "https://int4cf.authentication.eu10.hana.ondemand.com",
"xsappname": "default-d1eee2de-64cf-4936-8ac7-8bca3ae2cf55-clone!b68461|xbem-service-broker-!b2436",
"credential-type": "instance-secret"
}
}

Key	Application

Key	Application
clientid	Needed for Communication System credentials
clientsecret	Needed for Communication System credentials
management.uri	Communication System Host Name for Event Hub management
messaging.uri, where protocol is httprest	Communication System Host Name for Event Hub messaging
tokenendpoint	Communication System Token Endpoint

Please note, that in our case, the token endpoint, clientid and clientsecret are the same across all the sections. This could be different in Your scenario.

Step 2. Create relevant Communication Systems

Create Communication System for Event Hub management

For host name, token endpoint and OAuth data please use the information available in the service key.

Create Communication System for Event Hub messaging

For host name, token endpoint and OAuth data please use the information available in the service key.

Create and assign a user for inbound communication

Go to Maintain Communication User tile

Create an user to be used for Inbound communication from Event Mesh to the testing solution - needed for some test types.

Assign the user to the Communication System created above.

Step 3. Choose an Int4 environment or create a new one

Follow the general description for Int4 Environment Configuration to create or amend an environment

Step 4. Create communication arrangements

Create Communication Arrangement for Scenario ID /INT4/COM_0006_EM_MAN

This should refer to the Communication System for Event Hub management, as defined above.

Assign the the respective Environment.

Authorizations and services should populate automatically.

Create Communication Arrangement for Scenario ID /INT4/COM_0007_EM_MES

This should refer to the Communication System for Event Hub messaging, as defined above.

Assign the the respective Environment.

Authorizations and services should populate automatically.