Displaying RFC Profiles

Use

In the workload monitor, you can display the workload in different Analysis Views, each of which displays a particular aspect of the workload. One of these aspects is the workload caused by Remote Function Calls (RFC).

By displaying the RFC profiles, you can answer the following questions:

Which transaction, which function module, and which user caused what workload through RFC calls as an RFC client or an RFC server?
What workload do the transactions, function modules, or users cause in which local or remote RFC destinations?

Note

For transaction steps with RFC, the kernel writes subrecords with additional information about the processing time, the destination, and the function module used. The parameter stat/rfcrec (default: stat/rfcrec = 5) specifies the maximum number of subrecords of each type (RFC client, RFC server, RFC client destination, and RFC server destination) that the kernel writes. If more RFCs are performed during a transaction step, only the five calls with the longest execution time are therefore logged, Which is sufficient for performance analyses. The restriction to a maximum of five records represents a compromise between the required accuracy on one side and the workload created by the performance collector on the other side. A larger value for stat/rfcrec can lead to performance problems in the collector (see also Configuring the Workload Monitor).

The RFC client and RFC server records contain data such as execution time and called function for individual RFCs. The RFC destination records contain the total of all RFC calls per destination and therefore no additional information about the called function modules.

Procedure

Start the Workload Monitor by calling transaction ST03.
In the Workload tree, choose the instance and period to be analyzed.
Choose Analysis Views → RFC Profile, and choose the desired RFC profile.
The system displays the usual output area, in which the requested workload is displayed.

Result

Depending on the RFC profile selected, the output area shows the following tab pages:

Tab Page	Meaning
Function Module Transaction User	What workload is caused by the function modules, transactions, or users (depending on the selected RFC profile, as the RFC client or the RFC server)?
Remote Destination Remote Server Local Server	Where is the RFC workload created?

Workload Monitor start page