AZ-120: Planning and Administering Microsoft Azure for SAP Workloads

Today I have successfully cleared AZ-120 Exam.

It really give me booster to go more deeper in Azure Technology & how we can leverage more for SAP systems.
There are lot of things which still need to discover in Azure to get more benefit for SAP Landscape. However I am currently working on SAP Migrations only but mostly we people use SAP method’s to perform the same. Azure is also providing their native tools do perform the System Migration from On-Premise to Azure but frankly speaking, I never checked the same & even not familiar with them.

This exam helps me to understand what Azure is providing for SAP & how we can utilise the same with cost optimisation.

There are 42 questions in the exam including Scenario based questions. Some questions are completely related to Azure & some are from SAP Technology(I hope you know SAP Basic Terms).

The Best Material which helps & obliviously related to exam also is only Microsoft Documentation which is officially available in docs.microsoft.com

Below links help me to go through the exam –

https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/get-started

https://blogs.sap.com/2019/12/15/sap-expert-role-guide-to-microsoft-azure-skills-and-certification/

https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE44g2b

https://blogs.sap.com/2019/12/30/exam-study-resources-for-az-120-planning-and-administering-microsoft-azure-for-sap-workloads/

https://docs.microsoft.com/en-us/learn/modules/introduction-azure-sap-workloads/

I hope above material will help you to clear the exam.

Let me know if you have more questions.

Best of Luck!!!

SAP HANA 2.0 Cockpit Installation and Configuration

Recently for testing purpose, I have installed SAP HANA 2.0 Cockpit on my Google Cloud Virtual Machine by following the below steps –

SAP HANA 2.0 Cockpit InstallationSAP HANA 2.0 Cockpit Installation

SAP HANA Cockpit install with the HANA DB which also requires by default mount point – /hana/shared

However i have also summarised the below steps which are useful for a newbie to install the same –

1. Download SAP HANA Cockpit 2.0 from SAP Support Portal
2. SAP HANA Cockpit come with SAP HANA DB & can be install on separate system
3. UNCAR the SAR file of SAP HANA Cockpit & Install with ./hdblcm command
4. Default Port for SAP HANA Cockpit – 51029
5. Default Port for SAP HANA XSA – 330 – i.e. – 39630
6. Default Instance Number for SAP HANA Cockpit – 96
7. Default first time user login in HANA Cockpit – COCKPIT_ADMIN with Master Password (Created during installation)
8. SAP HANA Cockpit installation use default installation directory – /hana/shared

Note – Default Installation Directory can be change by adding extra parameter while running ./hdblcm

However when i ran ./hdblcm, i got the below error as SIGNATURE.SMF file is missing in the installation directory.

File ‘SIGNATURE.SMF’ cannot be found in the SAP HANA Database installation kit. To include the signature when extracting the installation kit from a .SAR archive, use the SAPCAR option: -manifest SIGNATURE.SMF You can ignore this error and continue with the execution by passing the ignore option ‘check_signature_file’ to hdblcm, started as root. See SAP note 2078425, section ‘How to prepare SAP HANA packages for installation or update’ for instructions how to prepare packages for update or implications of ignoring this error.

Then i followed the above given SAP Note & ignore the file by passing the below command –

./hdblcm -sh –ignore=check_signature_file

Above is the workaround, I would suggest to extract the SIGNATURE.SMF file as per SAP Note & run the installation.

Once I have successfully installed the SAP HANA Cockpit, installer given me below 2 URL to access the same.

Launch SAP HANA cockpit by opening https://hanabox1.us-east1-b.c.hana-273005:51027
Launch SAP HANA cockpit manager by opening https://hanabox1.us-east1-b.c.hana-273005.internal:51029

However as I am running the Cockpit in Google Cloud VM with Public IP, i want to access the same from outside world & I changed the above hostname with Google Public IP but still page is not opening & throwing the error – “Can’t reach the Page”

I tried by both ports – SAP HANA Cockpit & XSA URL but both are failing.

While digging into more in the system I have identified that there is an change requires in XSCONTROLLER.INI file on below location –

/usr/sap/SID/SYS/global/hdb/custom/config

Make a copy of xscontroller.ini & change the below 2 parameter by giving your PUBLIC IP –

default_domain = PUBLIC IP
api_url = https://PUBLIC IP:39630

save the file & restart the HANA instance.

Please Note – I am using Dynamic Public IP so whenever I shut down & start the Google Cloud VM, it change the Public IP & I need to update the same again.

Once it’s start successfully, wait for sometime & check the XSA URL

https://PUBLIC IP:39630

Voila… Page is now opening & now you can login to HANA Cockpit & Manage your HANA DB’s.

SAP HANA Cockpit XSA
Page

Let me know if you find this useful.

Tomcat Performance issue in SAP Business Objects 4.1 SP7

A New Installation of SAP Business Objects 4.1 SP7 with default Tomcat 7.0 Installation comes with (-Xmx) = 2048M & MaxPermSize = 384M.

However in some cases when there are multiple users login & execution of reports are happening then this memory is quite low & you can see the performance issue in your BO server where Adaptive Processing Server started responding very slow & sometime it’s hang while creating OLAP connections.

Some errors can be visible in logging directory of Tomcat on below file –

/usr/sap//bin
However in the BO system setenv.sh defined parameter to use bobjenv.sh file for memory related parameters.

We can increase the Tomcat memory on below file as per SAP recommendation –

/usr/sap/SID/sap_bobj/tomcat/bin/bobjenv.sh

Create a backup of original file & change the parameter of above file as per below notes.

Please Note – Before updating any Tomcat memory parameter, shut down the BO application & Tomcat, update the parameter & Restart the Tomcat & BO applications.

Verify the Memory of Tomcat in Linux –

ps -ef | grep tomcat ——— see the new memory parameter.

Reference SAP Notes –
2405536 – Best Practice: The popular combinations of Tomcat Max Memory Pool size and MaxPermSize
2075671 – Best Practice: How to identify Tomcat crash, unresponsive or hanging issue

SAP ADS Rendering Issue

Recently we have discovered that after configuration of ADS service in SAP Netweaver 7.40, we are facing rendering error while running report (SA38) – FP_CHECK_DESTINATION_SERVICE

We verified the configuration by going through multiple available SAP blogs but didn’t find the resolution of rendering error.

As per SAP note rendering errors occurs due to SAP Interactive forms credentials but we are not using the same & we have not configured any interactive forms but still it’s throwing errors.

By going through the multiple SAP Note, we have discovered that this issue is related to missing SUSE OS libraries which need to install & then restart the Java System or else restart the Adobe Document Service.

Helpful SAP Notes –

2215355 – Complementary analysis for ADS termination
2029940 – IFbA: Required additional RPM package for ADS on Linux