(v1) SAP Event Mesh
- Marcin Galczynski
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.
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
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
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 the environment
Environment creation
From the Launchpad, select the Environments Tile
List of environments will appear. Choose “Create” in the top right to initialize environment creation. 
Create Environment pop-up will appear on the screen.
Here, please select the appropriate Environment Type and provide a unique identifier (Id). It’s also possible to add a description field for internal reference.
Available environment types:
Type | Description |
|---|---|
Advanced Event Mesh | Use for testing Event scenarios with Advanced Event Mesh solution |
HTTP Host | Used for general API tests, in scenarios where endpoints are available with HTTP and HTTPS based URL’s. Use this for REST API’s and general SOAP/Webservice based endpoints |
SAP API Management | Use for connecting to SAP API Management for API data import |
SAP Cloud Integration | Use for connecting to SAP Cloud Integration for metadata import and testing iFlow scenarios. This includes also B2B/TPM and Pipeline concept based scenarios |
SAP Event Mesh | Use for testing Event scenarios with SAP Event Mesh solution |
SAP PI/PO | Use for connecting to SAP PI/PO instances for message selection and test case creation in migration scenarios |
Once type is selected and ID populated, click Create to create the environment definition. 
Environment definition screen will appear with multiple options, common and type dependent.
Basic information section
Field | Purpose |
|---|---|
Description | Free-form description of the environment, for reference only |
Production | Use this checkbox to mark environment as production environment to disable testing and limit the definition only for message collection and retrieval purposes |
Obsolete environment | Use this checkbox to mark environment as obsolete. This enables to keep the environment definition in place for reporting and audit purposes, while clearly distinguishing the environment as not available for test case creation and execution |
Properties section
Use this section to populate environment properties allowing for fine grained search and automatic assignment of environments for shift-left and migration scenarios. The fields can be filled with free-form tags.
Connections and parameters sections
This sections are specific to environment type.
Step 3. Populate the environment technical details
In the Connections sections of the environment screen, please note the Import Service Key button (or buttons, for some types).
Clicking the Import Service Key button opens up a dialog box, where the service key created before can be pasted or uploaded from file.
Please use this option for importing the respective service keys as created before.
Connection test
Following the import, Communication System definition and Communication Arrangement are created automatically. Connection test option is available.
Click on the 
Step 4. Enable Event Mesh Message Collection
In order to capture messages from Event Mesh installation into Your system for easy creation of test cases based on historical data, please proceed to the (v1) SAP Event Mesh Message Collection page of the manual.