Some metrics require a full specified RFC Destination Name like
RFC Destination available
- RFC Latency
The metric RFC Destination available (with logon) is more restrict. It requires a white list. Only destinations collected by the RFC destination extractor and are valid for a remote logon can be chosen. For TCP destinations (Type T) a logon check is not possible.
If the value help does not show any destination at all you should check if the extractor has been scheduled and if it is running successfully.
If you just miss one destination you should check if you can use the logon check from within SM59 of the managed system.
The information from F4 Help are usually taken Integration Directory. Here we are reading all Sender and Receiver Agreements and show the related Message Header Attributes for making the data entry more easy. This is just a help, it is still possible to enter the exact values manually (in case the Sender/Receiver Agreements do not cover required Entries). If there are no Sender and Receiver Agreements defined at all, e.g. because ICOs are used in Java-only PI, the F4 Help stays empty.
In any case the functionality for reading Sender/Receiver Agreements to get Message Header Attributes was not the best solution. But there is no possibility to really get the Message Header Attributes from Integration Directory according tot the defined Scenarios.
The recommendation to use the functionality is:
- Make sure, the PI Message Statistic extractors are running. E.g. configure an PI related Interface Channel with all '*' values and activate (this will start extraction).
- Go back to configuration and use the F4 Help to select required entries (since extractors are now running, the value help should be filled).
- Make sure, all relevant entries are selected (e.g. in case a message fails on the sender system, the receiver header attributes might not be filled yet). You can always compare with the local Message Overview Monitor or central PI Message Overview Monitor (if available).
In higher SAP Solution Manager Releases: The system is not part of the Technical Scenario for ICMon.
In higher SAP Solution Manager Releases: Make sure, the system is part of the Technical Scenario for ICMon, that you are currently setting up.
In SAP Solution Manager 7.2: Central PI monitoring is prerequisite for defining PI related Channels in ICMon. The Technical Scenario for the PI domain was not created in PI monitoring Setup.
In SAP Solution Manager 7.2: Go to PI Monitoring Setup and create the Technical Scenario for the PI domain in Step "Define Scope". Follow the PI Monitoring Setup Procedure and finally active PI Monitoring.