KB 205 - PowerConnect Considerations for RISE Deployments
KB 205 (ABAP): PowerConnect Considerations for RISE Deployments
Category: Information | Priority: Normal |
|---|---|
Platform: ABAP | Version: 1 from 4.06.2024 |
Description
PowerConnect is certified and compatible for SAP RISE. Below is a table indicating support and specific considerations for RISE deployments:
SAP Version | Supported | Special Considerations for Installation |
|---|---|---|
NetWeaver ABAP on RISE | Yes, as long as it is an SAP-supported version | See instructions below |
RISE with S/4HANA Private Cloud Edition | Yes, as long as it is an SAP-supported version | See instructions below |
RISE with S/4HANA Public Cloud Edition | Yes, as long as it is an SAP-supported version | N/A |
RISE - Multi-Tenant - Same Database, Same Schema with Column Discriminator for each customer ID | Yes, as long as it is an SAP-supported version | N/A |
RISE - Multi-Tenant - Shared Database, Separate Table/Schema for each customer ID | Yes, as long as it is an SAP-supported version | N/A |
RISE - Multi-Tenant - Shared Database, Separate Tenant Database for each customer | Yes, as long as it is an SAP-supported version | N/A |
Installation Considerations
If the customer is deploying PowerConnect in a supported RISE environment, here are specific steps that need to be followed:
The customer needs to confirm that the SAP system has the necessary outbound network connectivity to send data to the observability platform (port 8088 and/or 443).
The customer needs to send a support incident requesting that SAP installs the add-on component in their environment.
The SAP team needs to conduct the SAINT installation on behalf of the customer in Client 000 following these instructions: SAINT Installation.
The SAP team also needs to upload the authorization object transport data and cofiles into the respective application directories (/usr/sap/trans/data and /usr/sap/trans/cofiles): Authorization Object Transport.
The remaining installation steps should be conducted in the productive client by the customer’s team leveraging the provided installation guides: ABAP Installation Guide.
Networking Considerations
There are two approaches that customers leverage for networking in RISE environments:
Connection to the observability platform via proxy server - This is the most common scenario that customers leverage for RISE deployments. In this scenario, the customer would need to raise a service request to SAP asking them to whitelist the observability platform URL from the proxy server with port 443. From there, we will configure the connectivity from the SAP application to the proxy server over port 3128 (no requests required for this), and from the proxy server, the data will be routed over port 443 (requires whitelisting).
Direct connection to the observability platform - The connectivity from the customer RISE tenant works without any modification/whitelisting. You can test this by asking SAP to perform a telnet connection test to the observability platform URL over port 443.