This questionnaire is specific to deployments of SAP Integration Suite, advanced event mesh in Dedicated Regions. For questions related to deployments in Customer-Controlled Regions, see Questionnaire: Deploying in a Customer-Controlled Region.
Deploying
| Configuration Question |
How SAP Uses This Information |
Related Documentation |
|---|---|---|
| What is your SAP Business Technology Platform (BTP) subaccount or tenant ID? |
We require the SAP BTP subaccount or tenant ID to deploy the Kubernetes cluster. You can find your IDs on the subaccount’s front page in the SAP BTP cockpit. You should have a subscription to SAP Integration Suite, advanced event mesh before completing this questionnaire. |
Setting Up SAP Integration Suite, Advanced Event Mesh |
|
What cloud provider do you want SAP to use? |
Dedicated Region deployments of advanced event mesh support the following implementations of Kubernetes:
|
|
|
In what region do you want to install advanced event mesh event broker services? |
To correctly install and configure your Dedicated Region deployment, SAP needs to know which cloud provider region (if applicable) to use. |
|
|
Do you want the Messaging Connectivity to or from your event broker services to go through the public internet, private networks, or both? |
To help you configure the Messaging Connectivity for your Dedicated Region, SAP must know how you want your Messaging Connectivity routed. |
See Messaging Connectivity in Advanced Event Mesh Connectivity Requirements |
|
Do you want your incoming Messaging Connectivity to be private? If so which of the networking options supported by SAP do you want to use? |
SAP uses this information to help guide you in configuring the networking option you choose. |
|
|
If you want your Messaging Connectivity to be private? Does your chosen networking option require a unique CIDR range? If so, you can you an appropriately sized CIDR that is compatible with your network plan? |
SAP requires the CIDR to provision the VPC/VNet. If the network option you chose requires a unique CIDR range, you must provide one that does not overlap with any networks your event broker services will peer with. It must accommodate your network plan, and the amount event broker services you want to deploy. Consider the size of your cluster’s network carefully, as it is not possible to change its size after creation. |
For EKS and AKS, use the Excel-based CIDR calculator For GKE, see Networking in Installing in Google Kubernetes Engine (GKE) |
| Do you want to use a self-managed key for encrypting the data at rest on the persistent storage of your event broker services? |
SAP encrypts all data at rest by default. Using a self-managed key for encrypting data at rest is optional. If you want to use a self-managed key for encrypting your data at rest you must provide the key to SAP. Self-managed keys provide enhanced security by providing you with control over the creation, management, and permissions of the encryption keys. SAP currently supports self-managed keys from the following providers:
|
Contact Information
You must provide a point of contact for each entry in the table below. SAP prefers a distribution list as the point of contact, though you can choose to provide individual contact details.
| Contact Type | Distribution List or Contact Details |
|---|---|
|
Event broker service incidents or issues. |
|
|
Event broker service upgrade notifications and scheduling. |
|
|
Release and maintenance notifications. |