SAP RFC Monitor
Monitoring RFC connections of type ABAP (3), HTTP (G,H) and TCP/IP (T). Similar to the connection and authorization test in transaction SM59.
General
| Executable | SAP_RFC_Monitor.exe |
| Connection method | RFC |
| Ports |
|
| Lookup files |
|
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. |
| 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 |
|---|---|---|---|
| RFCName | <Name1>,<Name2>,… | empty | Names of the RFC to be monitored, comma separated. For HTTP connections (type G) you can define HTTP return codes which are accepted as a positive test result. If your RFC connection test result does not return a default HTTP code, you can also define a status text which should be accepted. Syntax:
|
| SSLCheck | true | false | false | Defines wether the named connections should be checked for the SSL option. |
Channels
| Channel name | Description | Lookup file |
|---|---|---|
| <RFCConnection> (<connection type>) | Shows the status of the RFC connection and its connection type:
| itesys.saprfcmonitor.rfcstate.ovl |
| <RFCConnection> SSL | Shows the status of the RFC connection SSL option:
| itesys.saprfcmonitor.rfcsslstate.ovl |
Lookup values
Values, states and texts defined in the lookup files of this sensor.
Lookup file: itesys.saprfcmonitor.rfcsslstate.ovl
| Value | State | Description |
|---|---|---|
0 | OK | Connection is encrypted. |
1 | Warning | Connection is unencrypted! |
Lookup file: itesys.saprfcmonitor.rfcstate.ovl
| Value | State | Description |
|---|---|---|
0 | OK | RFC working. |
1 | Error | Authorization failed! |
2 | Error | RFC does not exist! |
3 | Warning | No RFC authorization. |
4 | Error | Connection failed! |
Important notes
RFC types G and H can’t be checked with Netweaver 7.4 or older.
Troubleshooting
| Error Code | Error Message | Possible Solution |
|---|---|---|
[SCN-073-000] | The following parameters has not been provided: <parameters> Please read the sensor documentation for further information! | Specify the listed parameters in the profile or in the sensor-specific parameters. |
[SCN-073-051] | Wrong syntax for destination <destination>. Please only use valid HTTP Response codes. E.g. ADS:405,WEBSERV:404. | Use the syntax <destination>:<http_code> with valid HTTP response codes. |
[SCN-073-100] | RFC Connection error: <message> | Check the SAP connection parameters (Host, SAPInstance, SAPSID, SAPClient, SAPUsername, SAPPassword) and that the SAP system is reachable from the PRTG probe. The message from SAP tells you the cause (e.g. wrong password, locked user, missing authorization for RFC). |
[SCN-073-300] | Destination check failed for <destinations> | The connection test failed for the listed HTTP destinations. Check them in transaction SM59. |
Changelog
| Version | Changes |
|---|---|
| 2025.06 |
|
| 2023.06 | Added possibility to define accepted return codes and status texts for RFC type G connections |
| 2020.09 | The status No RFC authorization is now only checked for RFC connections from type 3 |
| 2020.06 | Extension of the “RFCConnection” channel to also monitor RFC connections of type G, H and T |
| 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 |