User Experience is now part of the SAP EarlyWatch Alert Dashboard
Highly requested and now delivered: In the SAP EarlyWatch Alert Dashboard, that is accessible via SAP for Me, there are now seven new User Experience (UX) charts available which provide you with an overview of your Fiori success metrics. In this article I would like to run you through the new content and explain the diagrams briefly.
Please note: If you can’t see the User Experience section at all that could mean that for the monitored system no OData traffic has been detected. If you miss some of the charts could indicate that the minimum system requirements are not met. Please refer to SAP note 2939430.
Within the Dashboard are two help sources available: The Web Assistant, which you can enable via the question mark button in the Launchpad header bar, shows help content as an overlay on top of the application and the [ i ]-icons on the right upper corner of each chart, that leads you to the diagram’s KPI catalog.
You can classify the new UX segment in three sections:
- UX Adoption
- System Performance
- System Health
With the time traveller UI element on the right upper corner of the User Experience (UX) segment you are able to view information that is even further back.
This section includes the two charts Usable SAPUI5 Applications and Application Components. Both charts give you a picture of how far SAP’s Fiori UX Strategy is adopted on the system.
The Usable SAPUI5 Applications chart shows the number of correctly configured UI5 applications for the last five weeks in a timeline chart. The chart legend explains the three lines.
Correctly configured means that the app’s ICF service is active, its (leading) OData service is registered in transaction /IWFND/MAINT_SERVICE, a system alias has been assigned, and some additional minor checks where performed successfully. The correct backend configuration cannot be checked since it is app specific.
With the Application Components diagram you figure out to which SAP Application Components the apps belong.
The next two charts provide you with an overview about the OData performance respectively workload. The Top OData Service Calls chart on OData level and the OData Requests chart on system level.
With the perspective switch (dropdown field) on the Top OData Service Calls chart you are able to select between three performance relevant views.
You can also click on the Detail View button on the right upper corner to open the OData Requests detail page.
In the table on the left side of the page you can select and unselect specific OData services to display their timeline on the right side in order to visualize the performance history of the last 14 weeks. However, the time frame period can be adjusted with the date range selection field above the timeline chart.
A click on the OData service name opens the Fiori Apps Reference Library application page of the Fiori app which uses this Odata service. Of course, this works only for SAP standard OData services.
As already mentioned, the OData Requests diagram displays data on system level. On the first view you see the average time of all OData calls in the last five weeks and on the second view, which you can access via the perspective switch, the total number of all OData calls.
The last section consists again of two diagrams and indicates how healthy the OData communication of the system is. The first one Top Gateway Errors is self-explanatory and shows, alterable by the perspective switch, either the five most frequently occurred errors or the top five of errors that affected most users.
This chart is also connected to a detail page which you can reach via the dedicated button. The page lists all Gateway errors of the selected week – you can time travel here, too – and provides detail information. The trend arrows for the fields Number of Occurrences and Distinct Users compare the values of the displayed week with the values of its preceding week.
The second diagram, with the title Gateway Errors, reflects the total number of Gateway errors on system level for the last five weeks.
And what’s about the remaining ICF Security chart?
We actually created it because we figured out that administrators tend to activate Internet Communication Framework (ICF) services which are later not used. However, as mentioned in the SAP S/4HANA Security Guide, you should handle ICF services in a restrictive manner in order to
minimize the attack surface on the web. That’s why we compare in the chart the number of activated ICF services within the UI5 repository with the ones of the apps which are configured correctly.
In an ideal system configuration the Activated ICF Services bar should be slightly higher than the Usable Apps bar, since there are some ICF service, like e.g. for Reuse Libraries, which should be enabled and are not directly linked to a Fiori app.
To know which ICF service is unused and are candidates for deactivation you can open the chart’s detail page via the dedicated button on the right upper corner.
Per default, the left tab is selected and the page lists all active ICF services within the UI5 repository. You can use the three tabs on the right that serve as filters to gather more information. The services under tab Not Used are the ones you may disable.
Please be careful and double-check the ICF services on your system to prevent switching off Fiori apps that your users actually would like to use.
If the list of unused but active ICF services is long you can use the ICF Mass Processing Tool to deactivate ICF services. How you exactly do this is described in SAP KBA 2989913.
If you encounter any strange behavior within the Dashboard, when you think the shown data cannot be correct, or you have an idea to improve the user experience then please don’t hesitate to comment on this SAP Blog to let us know. We are delighted to contact you and give our best to improve the EarlyWatch Alert cloud applications.