Blog Post

Running SAP Applications on the Microsoft Platform
5 MIN READ

SAP NetWeaver Licensing Mechanism in Microsoft Azure Cloud - Part 1

Goran Condric's avatar
Goran Condric
Icon for Microsoft rankMicrosoft
Apr 17, 2019
As an SAP administrator, you surely faced situations where suddenly a valid SAP license becomes invalid for no obvious reason. For an SAP ABAP system, the system will automatically generate a tem...
Updated Apr 17, 2019
Version 2.0
Goran Condric's avatar
Goran Condric
Icon for Microsoft rankMicrosoft
May 21, 2019

 

 

If you recheck the blog (or video), it is stated

“

An SAP hardware key is generated on an operating system host where SAP message server process is running.

 

For an SAP ABAP-based system, SAP message server is part of:

  • SAP ASCS instance (ABAP Central Services)
  • SAP DVEBMGS instance (so-called central instance)
    As newer SAP installations do not install the DVEBMGS instance anymore, there is a small chance that you will run into this kind of setup.

 

For SAP Java based systems, the SAP message server is part of:

  • SAP SCS instance (Java Central Services)

“

So you have to run saplicense on the SAP message server host (ASCS/SCS instance and maybe DVEBMS instance)

 

If you log as SAP OS admin <sid>adm user , the environment path to saplicense should be predefined , so saplicense should work without specifying path to saplicense executable. This is demonstrated in the video where I was logged with <sid>adm user , both on Windows and Linux OS.

With other users which most probably do not have defined path environment point to saplicense executable, you need to specify the full path to saplicense .

 

On linux full path to saplicense can be :

 

/usr/sap/<SID>/SYS/exe/uc/linuxx86_64/saplicense

/usr/sap/<SID>/SYS/exe/run/saplicense

 

On windows could be something like this:

 

\\<globalhost>\sapmnt\<SID>\SYS\exe\uc\NTAMD64\saplicense.exe

 

You can find location of saplicense if you log on as <sid>adm user and run command

 

where saplicense