SAP J2EE Monitor

Monitors a SAP AS Java instance

General

Executable	SAP_J2EE_Monitor.exe
Connection method	HTTP
Ports	5$$13 (http) 5$$14 (https) ($$ = instance number)
Lookup files	itesys.sapj2eemonitor.componentsstatus.ovl itesys.sapj2eemonitor.j2eeoverallstate.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
SAPInstance	number (2) | 00 - 99	empty	Instance number of the SAP system

Sensor-specific parameters

Parameter name	Possible values	Default	Description
Components		NONE	Specifies the java components to additionally monitor. There are three possible ways to maintain this parameter. Using custom set of components in Profiler GUI Syntax: <component1>,<component2>,… Using custom set of parameters from file in SAP_J2EE_Monitor folder Syntax: FILE:<filename> Using a predefined set delivered with the sensor Syntax: FILE:<filename>
Protocol	http | https	http	Used protocol for the connection to sapstartsrv

Presets

File name	Description
IDM.preset	Holds a template for the Java components which are important for SAP Identity Management.

info

If you want to customize a preset, please copy the file and maintain it under your own name. Otherwise your changes will be overwritten with the next Scansor update.

Channels

Channel name	Description	Lookup file
J2EE overall state	Status of all J2EE processes	itesys.sapj2eemonitor.j2eeoverallstate.ovl
Active users - server<n>	Number of current users
Active web sessions - server<n>	Number of current web sessions
Certificate expires in # days	Number of days until expiration of the soonest expiring certificate in the KeyStore
Expired user certificates	Number of expired user certificates
Internal server errors - server<n>	Occurred internal server errors
Max memory - server<n>	Maximum useable memory per server
Used memory - server<n>	Used memory per server
Out of memory errors - server<n>	Number of OOMs that has been occurred
Services start fails	Number of Java services not started
Threads	Number of currently used threads
GC CPU Time – server<n>	Used CPU time during the carbage collection per server within the last hour
Number of Full GC - server<n>	Counts the number of Full GC per server within the last hour
Number of GC pageFaults - server<n>	Counts the number of GC page faults per server within the last hour
<component> status	Shows the status of the component running in the AS Java depending on the parameter <Components>	itesys.sapj2eemonitor.componentsstatus.ovl

Important notes

warning

Please check the channel limits in PRTG if they fit for your alerting.

Changelog

Version	Changes
2023.09	Added parameter to use https for sapstartsrv connection
2022.08	Added possibility to monitor components running in the AS Java via the new parameter <Components>
2022.05	Added channels to monitor the JAVA Garbage Collection (GC) like amount of Full GC, number of GC page faults or CPU time of GC. Results with ‘-‘ are catched now and no «invalid integer value» error occurs anymore.
1.4.0.2	Ignore SAP Control GRAY state (suppresses wrong not int type values)
1.4.0.1	Rebuild for new signature of AddChannel method
1.4.0.0	Build for installer 1.4.0
1.3.6.0	First stable release