To provide health check settings for SAP Web Dispatcher that sits behind a AWS Load Balancer -
Use the following path - /sap/public/ping
Tuesday, 23 November 2021
502 Bad Gateway - Sap Web Dispatcher as a target used in AWS Load Balancer
Issue: 502 Bad Gateway is issued for any request which is issued to a SAP Web Dispatcher that sits behind AWS Application load balancer.
Solution: Under the Target group defined in the AWS load balancer for the SAP Web dispatcher, ensure correct protocol version is defined.
You need to switch between the HTTP1/HTTP2 based on your version.
Monday, 1 November 2021
Test SAML SSO to HANA connection failed in Central Management Console (CMC)
The environment in test is
BOBJ - 4.2 SP3
HANA - 2.0 SP5
Method used : File based Trust store
Many blogs and SNotes were taken as a starting point in setting up the SSO between the SAP Business Objects and 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.
It looks like there is a bug in the CMC configuration window. Omit the entries for the Hana Tenant and instance number as highlighted in the screenshot below and the connection goes through fine.
Sunday, 29 August 2021
How to configure DB13 to work with a standalone/Remote Oracle database on Unix/Linux
Problem:
Your SAP system is on Linux. Oracle database runs in a dedicated host where no SAP instance is installed.
Scheduling DB Jobs from DB13 does not work in a distributed system. Instead of going for additional gateway on DB instance, the following procedure can be followed .
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' or 'ssh' depending on what was configured in step 3. This can be tested using the following command. It should not return errors neither asks for password. It is also important to reinforce that the same hostname set in step one should be used here: rsh <database host> -l <sid>adm sapxpg
- You can refer to KBA 2312909 to see how to setup the passwordless SSH connection.
- DB13 will automatically create an RFC destination called SAPXPG_DBDEST_<SAPDBHOST>. Make sure there are no gateway options set for that destination. What makes DB13 choose the gateway instead of remote connection is the setting of the gateway option in this destination. If no settings for that, remote shell will be used;
To Setup SSH:
- Log to your SAP application server OS(in which you will run DB13) with user <SID>ADM. Run command “ping <DB hostname>”. DB should be able to get reached.
- SSH service should be running on OS level, check ps –ef |grep sshd
- Now you can perform an SSH connection test with <SID>ADM user from the SAP application server to database server by command “ssh <database host> -l <SID>adm”. It will ask for the password of user <SID>ADM. (the <SID>adm user should exist in database host.)
- Run command “ssh-keygen –t rsa” on SAP application server where DB13 jobs to be scheduled from. This is to create RSA key. Normally this program generates one key and asks for a file to store the private key. The public key is stored in a file with the same name but ''.pub'' appended. The program also asks for a passphrase. This passphrase is other than the actual password of user <SID>adm. (It is a password for the private key to increase the security. If you set the passphrase, you will be asked for it when you use the private key.) Here for DB13 use, you do not need to set it.
It then created a folder named “.ssh” from <SID>ADM home, and generated a file “id_rsa” with the private key and file “id_rsa.pub” to save the public key under “.ssh” folder.
Run command “ssh-copy-id <SID>adm@<hostname>” to copy the public key into the database server's authorized_keys file.
Here is the example, vml2493 is my database host. Localhost is my SAP application host. A file named authorized_keys under directory /home/<SID>adm/.ssh in database host will be generated.
Now you can test the connection via command "ssh <database host> -l <SID>adm". You will be connected to database host directly without entering password. Then you can run some standard linux commands for test, like ";s" or "uname -a". It will return you command result from standalone database host successfully.
Here is an example:
Lastly make sure sapxpg is with permission -rwxr-xr-x for <SID>adm user and SAPSYS group. Connection test in KBA 1974030 "ssh <database host> -l <SID>adm sapxpg" should now work perfectly.
Note SSH is not an SAP delivery. The guide here is only an example. Make sure to review configuration of SSH with OS admin or OS vendor for security matter.
Warning:
The generated private ssh key is accessible from within SAP. If you are concern about the potential security hole, you can use the alternative way: install a standalone gateway in oracle database server.
To avoid "Host key verification failed" error, make sure the full qualified domain name (FQDN) of remote database host is maintained in the ssh configuration file (/home/<sid>adm/.ssh/known_hosts) of the application server. (KBA 2919219)
Note: If the SAP RFC SAPXPG_DBDEST_<dbhost> still fails, modify the connection as below.
Sunday, 2 May 2021
SAP Product Versions
SAP Product Versions
The SAP Product Versions listed in the tables below are supported by
support package stacks. Each support package stack has a leading software
component version. The support package level of this particular component
version is a key part of the stack and a unique identifier for the support
package stack level.
SAP NetWeaver
|
SAP Product Version |
Leading Software Component Version |
Support Package Name |
|
SAP_BASIS 700 |
SAPKB700<xx> |
|
|
SAP_BASIS 701 |
SAPKB701<xx> |
|
|
SAP_BASIS 702 |
SAPKB702<xx> |
|
|
SAP_BASIS 710 |
SAPKB710<xx> |
|
|
SAP_BASIS 711 |
SAPKB711<xx> |
|
|
SAP_BASIS 730 |
SAPKB730<xx> |
|
|
SAP_BASIS 731 |
SAPKB731<xx> |
|
|
SAP_BASIS 740 |
SAPKB740<xx> |
|
|
SAP_BASIS 750 |
SAPK-750<xx>INSAPBASIS |
|
|
SAP_BASIS 751 |
SAPK-751<xx>INSAPBASIS |
|
|
SAP_BASIS 752 |
SAPK-752<xx>INSAPBASIS |
SAP ERP
|
SAP Product Version |
Leading Software Component Version |
Support Package Name |
|
SAP_APPL 600 |
SAPKH600<xx> |
|
|
SAP_APPL 601 |
SAPKH601<xx> |
|
|
SAP_APPL 602 |
SAPKH602<xx> |
|
|
SAP_APPL 603 |
SAPKH603<xx> |
|
|
SAP_APPL 604 |
SAPKH604<xx> |
|
|
SAP_APPL 605 |
SAPKH605<xx> |
|
|
SAP_APPL 606 |
SAPKH606<xx> |
|
|
SAP_APPL 616 |
SAPKH616<xx> |
|
|
SAP_APPL 617 |
SAPKH617<xx> |
|
|
SAP_APPL 618 |
SAPK-618<xx>INSAPAPPL |
SAP S/4HANA
|
SAP Product Version |
Leading Software Component Version |
Support Package Name |
|
SAP_BASIS 750 |
SAPK-750<xx>INSAPBASIS |
|
|
SAP_BASIS 751 |
SAPK-751<xx>INSAPBASIS |
|
|
SAP_BASIS 752 |
SAPK-752<xx>INSAPBASIS |
|
|
SAP_BASIS 753 |
SAPK-753<xx>INSAPBASIS |
SAP CRM
|
SAP Product Version |
Leading Software Component Version |
Support Package Name |
|
BBPCRM 700 |
SAPKU700<xx> |
|
|
BBPCRM 701 |
SAPKU701<xx> |
|
|
BBPCRM 702 |
SAPKU702<xx> |
|
|
SAP enhancement package 2 for SAP CRM 7.0, version for SAP
HANA |
BBPCRM 712 |
SAPKU712<xx> |
|
BBPCRM 713 |
SAPKU713<xx> |
|
|
BBPCRM 714 |
SAPKU714<xx> |
SAP SCM
|
SAP Product Version |
Leading Software Component Version |
Support Package Name |
|
SCM 700 |
SAPKY700<xx> |
|
|
SAP enhancement package 1 for SAP Supply Chain Management
7.0 |
SCM 701 |
SAPKY701<xx> |
|
SAP enhancement package 2 for SAP Supply Chain Management 7.0 |
SCM 702 |
SAPKY702<xx> |
|
SAP enhancement package 2 for SAP SCM 7.0, version for SAP
HANA |
SCM 712 |
SAPKY712<xx> |
|
SAP enhancement package 3 for SAP Supply Chain Management
7.0 |
SCM 713 |
SAPKY713<xx> |
|
SAP enhancement package 4 for SAP Supply Chain Management
7.0 |
SCM 714 |
SAPK-714<xx>INSCM |
SAP Solution Manager
|
SAP Product Version |
Leading Software Component Version |
Support Package Name |
|
ST 720 |
SAPK-720<xx>INSTMAIN |
SAP SRM
|
SAP Product Version |
Leading Software Component Version |
Support Package Name |
|
SRM_SERVER 700 |
SAPKIBKV<xx> |
|
|
SRM_SERVER 701 |
SAPK-701<xx>INSRMSRV |
|
|
SAP enhancement package 2 for SAP Supplier Relationship
Management 7.0 |
SRM_SERVER 702 |
SAPK-702<xx>INSRMSRV |
|
SAP enhancement package 3 for SAP Supplier Relationship
Management 7.0 |
SRM_SERVER 713 |
SAPK-713<xx>INSRMSRV |
|
SAP enhancement package 4 for SAP Supplier Relationship
Management 7.0 |
SRM_SERVER 714 |
SAPK-714<xx>INSRMSRV |
Releases
SAP R/1 System RF: 1973
SAP R/2 Mainframe System: 1979
SAP R/3 Enterprise Edition 1.0 A: July 1992
SAP R/3 Enterprise Edition 2.0B (SAP R/3
2.0B): July 1993
SAP R/3 Enterprise Edition 3.1l (SAP R/3
3.1I): 11 May 1998
SAP R/3 Enterprise Edition 4.0B (SAP R/3
4.0B): 6 April 1998
SAP R/3 Enterprise Edition 4.3
SAP R/3 Enterprise Edition 4.5B (SAP R/3
4.5B): 29 March 1999
SAP R/3 Enterprise Edition 4.6B (SAP R/3
4.6B): 6 December 1999
SAP R/3 Enterprise Edition 4.6C (SAP R/3
4.6C): 3 April 2000
SAP R/3 Enterprise Edition 4.6F
SAP R/3 ENTERPRISE 4.7X110: 15 July 2002
SAP R/3 ENTERPRISE 4.7X200: 22 September 2003
SAP ERP Central Component (ECC) 5.0: 21 June
2004
SAP ERP Central Component (ECC) 6.0: 24
October 2005
SAP enhancement package 1 for SAP ERP 6.0
(EHP1 FOR SAP ERP 6.0): 21 December 2006
SAP enhancement package 2 for SAP ERP 6.0
(EHP2 FOR SAP ERP 6.0): 27 July 2007
SAP enhancement package 3 for SAP ERP 6.0
(EHP3 FOR SAP ERP 6.0): 7 December 2007
SAP enhancement package 4 for SAP ERP 6.0
(EHP4 FOR SAP ERP 6.0): 21 November 2008
SAP enhancement package 4 for SAP ERP 6.0 on
SAP enhancement package for SAP NetWeaver 7.0 (EHP4 FOR SAP ERP 6.0 / NW7.01):
21 November 2008
SAP enhancement package 5 for SAP ERP 6.0
(EHP5 FOR SAP ERP 6.0): 12 July 2010
SAP enhancement package 6 for SAP ERP 6.0
(EHP6 FOR SAP ERP 6.0): 24 August 2011
SAP enhancement package 7 for SAP ERP 6.0
(EHP7 FOR SAP ERP 6.0): 13 August 2013
SAP Fiori 1.0 for SAP ERP (UI FOR EHP7 FOR
SAP ERP 6.0): 29 November 2013
SAP enhancement package 8 for SAP ERP 6.0
(EHP8 FOR SAP ERP 6.0): 20 January 2016
SAP S/4HANA
SAP S/4HANA 1511: November 2015 [3]
SAP S/4HANA 1610: 31 October 2016 [4]
SAP S/4HANA 1709: 15 September 2017 [5]
SAP S/4HANA 1809: 21 September 2018 [6]
SAP S/4HANA 1909: 20 September 2019 [7]
SAP S/4HANA 2020: 7 October 2020 [8]
SAP Business Suite
SAP Business Suite is a bundle of business
applications that provide integration of information and processes,
collaboration, industry-specific functionality and scalability. SAP Business
Suite is based on SAP's technology platform called NetWeaver.
SAP Business Suite 7 has five
constituents:[1]
SAP ERP 6.0 (Enterprise Resource Planning)
SAP CRM 7.0 (Customer Relationship
Management)
SAP SRM 7.0 (Supplier Relationship
Management)
SAP SCM 7.0 (Supply Chain Management)
SAP PLM 7.0 (Product Lifecycle Management)
Subscribe to:
Posts (Atom)