SAP Parameter Monitor

General

Checks the given SAP profile parameters for an expected value. Possible comparison operators are <equal>, <not equal>, <less than>, <greater than>, <less or equal>, <greater or equal>, <contains> and <not contains>.

Executable	SAP_Parameter_Monitor.exe
Connection method	http(s) to sapstartsrv
Ports	5<nr>13 (http) 5<nr>14 (https)
Lookup files	itesys.sapparametermonitor.parameterstate.ovl

Default parameters

Parameter name	Possible values	Default	Description
Host	<ip> | <hostname>	empty	Hostname or IP of the target system. If you use a virtual hostname on your SAP servers, please use also the virtual host to connect.
OSUsername	string	empty	Operating system user
OSPassword	string	empty	Password of the operating system user
SAPSID	string (3) | XXX	empty	SID of the SAP system
SAPInstance	number (2) | 00 - 99	empty	Instance number of the SAP system
SAPClient	number (3) | 000 - 999	empty	SAP Client (CLNT/MANDT)
SAPUsername	string	empty	SAP user
SAPPassword	string	empty	Password of the SAP user

Sensor-specific parameters

Parameter name	Possible values	Default	Description
DetectDynamicChanges	false | true	false	Defines if dynamic parameter changes will be recognized. warning Make sure that the job SAP_COLLECTOR_FOR_PERFMONITOR is planned correctly as described in SAP note 3205243
Parameters	<parameterName1><operator><expectedValue1>[;<parameterName2><operator><expectedValue2>[;...]] | FILE:<filename>	FILE:Security.preset	There are two possible ways to maintain this parameter Using custom set of parameters Syntax: <parameterName1><operator><expectedValue1>[;<parameterName2><operator><expectedValue2>[;...]] Using custom set of parameters from file in SAP_Parameter_Monitor folder Syntax: FILE:<filename> Possible comparison operators: == (equal to) != (not equal to) << (less than)1 >> (greater than)1 <= (less or equal)1 >= (greater or equal)1 *= (contains) *! (not contains) 1 only applicable for integer or double values (Please note that preset files will be overwritten during update of Scansor. If you want to customize a file, please copy and rename it)
Protocol	http | https	http	Used protocol for the connection to sapstartsrv

Presets

File name	Description
Security_S4.preset	Set of security dependent parameters based on the official SAP Security Baseline for S/4HANA.
Security.preset	Set of security dependent parameters based on the official SAP Security Baseline.
TLS1.2_and_1.1.preset	Set of parameters for TLS 1.2 and TLS 1.1.
TLS1.2_and_weaker.preset	Set of parameters for TLS 1.2 and weaker.
TLS1.2_only.preset	Set of parameters for TLS 1.2 only.
TLS1.3_and_1.2.preset	Set of parameters for TLS 1.3 and TLS 1.2.
TLS1.3_and_weaker.preset	Set of parameters for TLS 1.3 and weaker.

warning

The SSL/TLS parameters in your system can be different from the ones in the TLS presets but your system nevertheless can support one of the desired protocols. Please refer to SAP Note 510007, SAP Note 2384290 or SAP Note 3346659 for further information and use a custom preset for the sensor if nessessary.

Channels

Channel name	Description	Lookup file
<Parameter name>	The sensor produces one channel for each parameter showing if the parameter has the expected value or not.	itesys.sapparametermonitor.parameterstate.ovl

Important notes

warning

Please note that if you remove one or more parameters from the check, you have to delete all sensors running with the affected profile and then add them again because PRTG is not able to delete channels on existing sensors.

warning

To make the sensor also recognize the values of dynamic parameters in ABAP systems, make sure that the job SAP_COLLECTOR_FOR_PERFMONITOR is planned correctly as described in SAP Note 3205243. The sensor will recognize the actual value as soon as the job has been finished successfully once after the parameter changed.

Troubleshooting

Symptom	Possible solution
Sensor is not showing all parameters as a channel	Check for the correct syntax in the Parameters parameter or in your parameters file. The sensor will ignore lines with wrong syntax.
Text <parameterName> Failed to parse values for comparison! is showing up in the sensor text	Check if you used one of the following operators on a value which is not an integer or a double <<, >>, <=, >=
File <filename> could not be found! Please check your sensor parameters!	The file you specified in the parameter Parameters is not present in the folder SAP_Parameter_Monitor. Please make sure that you specify a file which exists.

Changelog

Version	Changes
2024.10	Added new preset for TLS 1.3 check Renamed existing TLS presets for better understanding
2024.04	Fixed read of parameters when having multiple application servers
2024.01	Made ABAP parameters SAPClient, SAPUsername and SAPPassword optional to make the sensor available for non-ABAP systems like SAP Webdispatcher
2023.03	Added preset based on SAP Security Baseline for S4 systems Updated existing Security.preset based on the latest SAP Security Baseline
2022.12	Added option to detect dynamic parameter changes in ABAP systems.
2022.08	Added three presets for TLS checks.
2022.05	The sensor is now able to recognize parameter values of dynamic parameters which has been changed since the startup of the system. Since the check of dynamic parameters is only available for ABAP systems, the sensor parameter DynamicCheckEnabled was introduced to explicitly enable the check for dynamic parameters. The required parameters have been corrected which are only Host, OSUsername and OSPassword now.
2021.03	Initial creation.