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:
|
Channels
Channel name | Description | Lookup file |
---|---|---|
<RFCConnection< (<connection type>) | Shows the status of the RFC connection and its connection type:
| itesys.saprfcmonitor.rfcstate.ovl |
Important notes
warning
RFC types G and H can’t be checked with Netweaver 7.4 or older.
Changelog
Version | Changes |
---|---|
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 |