My Experience in SAP/HANA

This post explains the health check configuration for an SAP Web Dispatcher located behind an AWS Load Balancer. Configure the health check to use the following path: /sap/public/ping

  Issue:  A 502 Bad Gateway error occurs for any request sent to a SAP Web Dispatcher that sits behind an AWS Application Load Balancer. Solution:  Check the target group defined in the AWS load balancer for the SAP Web Dispatcher and ensure the correct protocol version is configured. You will need to switch between HTTP1 and HTTP2 depending on your version.  

The environment in test is BOBJ - 4.2 SP3 HANA - 2.0 SP5 Method used : File based Trust store Several blogs and SAP Notes were used as a starting point for setting up SSO between SAP BusinessObjects and the HANA DB. https://blogs.sap.com/2020/03/22/sap-bi-platform-saml-sso-to-hana-database/ There's an SNote which provides documentation . Configure SAML SSO to HANA according to 1900023 - How to setup SAML SSO to HANA from BI. Based on my experience and all tests, the following pre-requisites are required. 1. Public URLs has to be setup to access XS admin page/Wdisp for the tenant DB 2. SSL is not mandatory. 3. HANA parameters to point to the correct Trustkeystore 4.FW to be open for the required ports. Despite all the configuration, the test connection in CMC always resulted in ""Connection Failed: The test of the HANA SSO ticket used to log onto the HANA DB has failed due to: [10]: authentication failed. (FWM 02133)" error." This appears to be a bug in the CMC...

 Problem:  Your SAP system runs on Linux, and the Oracle database is on a dedicated host with no SAP instance installed. In this type of distributed setup, scheduling DB jobs from DB13 does not work directly. Rather than adding an additional gateway on the DB instance, the following procedure can be used instead. Solution: Set the variable 'SAPDBHOST' with the database host name. In case of RAC database use the virtual hostname of the first node (see SAP Note 1738351 in case of Solution Manager). For database installed in OS cluster, use the virtual hostname of the cluster; Set the profile variable 'gw/netstat_once' to 0. This is to identify dynamic changes of the logical hostnames; Set the profile variable 'gw/remsh' with the full path of the 'rsh' in case you want to use normal remote shell or full path of 'ssh' in case of secure remote shell; Perform a connection test from the SAP instance host to database host. You should use 'rsh' o...

  SAP Product Versions The SAP product versions listed in the tables below are supported by their respective support package stacks. Each stack is associated with a leading software component version, and the support package level of that component version serves as a unique identifier for the stack level. SAP NetWeaver SAP Product Version Leading Software Component Version Support Package Name SAP NETWEAVER 7.0 SAP_BASIS 700 SAPKB700<xx> SAP EHP1 FOR SAP NETWEAVER 7.0 SAP_BASIS 701  SAPKB701<xx> SAP EHP2 FOR SAP NETWEAVER 7.0 SAP_BASIS 702 SAPKB702<xx> SAP NETWEAVER PI 7.1 SAP_BASIS 710  SAPKB710<xx> SAP EHP1 FOR SAP NW PI 7.1 SAP_BASIS 711  SAPKB711<xx> SAP NETWEAVER 7.3 SAP_BASIS 730  SAPKB730<xx> ...