The generic interface monitoring setup in SAP Focused Run is explained in this blog. This blog will zoom into monitoring of RFC connections.
RFC’s between SAP systems
RFC’s with fixed user ID
The basic setup of monitoring RFC’s was explained as example for the generic interface monitoring setup in this blog already.
Trusted RFC’s
This RFC was an RFC with a fixed user ID. If you have to setup an RFC monitoring for a trusted RFC (for example between Netweaver Gateway system and ECC system), then you have to take care of the user ID’s and rights. The system from which the SM59 test will run, will use that Focused Run user ID to log on to the other system. If your user ID’s are unique for each system you have to create the user ID in the other systems with the rights to be able to execute a ping and logon for the test.
End result RFC checks
The end results of the RFC is list of RFC’s with the latency time, availability and logon test overview:
Transactional RFC towards external system
To monitor transactional RFC (type T) towards an external system like TIBCO, Mulesoft, etc, you first need to model the external system in the LMDB. To do this goto the LMDB maintenance FIORI app:
Then select Single Customer Network and select the option Technical Systems. In this section choose the Type Unspecific Standalone Application System:
And press Create:
Fill out the details and Save. Make sure the status is Active.
Now the system can be added in the configuration of technical systems in the Interface monitoring configuration:
Now you can model the tRFC interface connection monitoring:
OSS notes
Relevant OSS notes:
- 3146957 – TRFC & QRFC monitoring issue fix
- 3147628 – tRFC monitoring issue – skipping current day entries
