The PHD tab stores the settings used by the selected RFC Destination used to retrieve performance history data, and contains a summary of the last set of data that was collected. Performance history data may be retrieved from a LiveCompare remote function call, from a native SAP remote function call or from an External Data Source. These last two options may be used on SAP systems that do not have LiveCompare’s transports installed on them.
The performance history data that has been retrieved for an RFC Destination may be accessed in a workflow using the Read Performance History Data action.
To download performance history data for the selected RFC Destination, complete the ‘Keep this many months of data’ (n) field and click ‘Update Data’. The most recent n months of usage data is retrieved and the Data Summary section includes the following details.
|Rows of Application Statistics:||The number of rows of application statistics retrieved.|
|Rows of Users Statistics:||The number of rows of users statistics retrieved. Users statistics are not available if performance history data is obtained from an External Data Source.|
|Last run time:||The time when performance history data was last retrieved for the RFC Destination.|
|Start date:||The start date used for the retrieval of performance history data.|
|Keep this many months of data:||The number of months of performance history data requested.|
Click ‘Update Data’ to update the performance history data for the specified RFC Destination by retrieving the specified number of months of data (the most recent performance history data is retrieved). Click ‘Delete Data’ to delete the retrieved performance history data. A confirmation dialog is displayed, and the run time for the delete operation is shown.
If the ‘OnlyAdminEditsRFCDest’ option has been set in the Configuration - Security screen or during the installation of LiveCompare, the performance history data available for an RFC Destination may not be updated or deleted by users with LiveCompare Editor privileges.
Use the Source section to specify the source for the RFC Destination’s performance history data.
- Select ‘LiveCompare RFC’ to retrieve performance history data using a function provided by LiveCompare’s installation transports.
- Select ‘SAP Native RFC’ to retrieve performance history data using a native SAP function. The function called is specific to the RFC Destination’s SAP kernel release.
- Select ‘External Data Source’ to retrieve performance history data from the specified External Data Source. The ‘External Data Source to use’ drop-down list contains External Data Sources that have been created with type ‘Performance History Data’. If LiveCompare is project-controlled, only the External Data Sources in the currently selected project are listed.
If the Source field is set to either ‘LiveCompare RFC’ or ‘SAP Native RFC’ Usage data for BSP Applications (including Fiori/UI5 BSP Applications) is retrieved (if this has been configured for an RFC Destination).
Use the Scheduling section to specify scheduling details for the retrieval of performance history data. Scheduling details may only be specified if the ‘Source’ field is set to ‘LiveCompare RFC’.
|Update performance history data according to this schedule:||Select this check box to enable the schedule, or deselect the check box to disable the schedule.|
|Run monthly on this day of each month:||Select this radio button to retrieve performance history data monthly on the selected day of the month, at the scheduled start time.|
|Run at this time:||The run time for the schedule.|
|Keep this many months of data:||A value (n) between 0 and 99 specifying how many months of data to retain. When the schedule runs, the most recent <n> months of performance history data is retrieved, and any previous performance history data stored for the RFC Destination is overwritten.|
If the ‘OnlyAdminEditsRFCDest’ option has been set in the Configuration - Security screen or during the installation of LiveCompare, the performance history data retrieval schedule for an RFC Destination may not be modified by users with LiveCompare Editor privileges.