This is the central note for information and updates on End-User Experience Monitoring (EEM)

Solution Manager EEM End-User Experience Monitoring UX Monitor

Release Information

End-User Experience Monitoring (EEM) is available as part of SAP Solution Manager.

Documentation

The official documentation for Solution Manager 7.1 can be found here:
http://help.sap.com/solutionmanager71
Use this link to directly jump to End-User Experience Monitoring:
http://help.sap.com/saphelp_sm71_sp01/helpdata/en/37/2dad5728904975beb24c8e87239aab/frameset.htm.

Additional information on EEM can be found in the SAP Developer Network Wiki:
https://wiki.sdn.sap.com/wiki/display/EEM/Home.

The wiki space contains overview material on the functionality of EEM and also e.g. information on installation, using, troubleshooting, and release notes for EEM.

In addition a user guide for the EEM editor is bundled with the EEM Editor installation package (EEM_Script_Editor_Guide_EN.pdf).

Support

In case of problems with End-User Experience Monitoring open support tickets on component SV-SMG-MON-EEM. Note, however, that the following limitations apply:

• SAPGUI scripts are limited to the scripting functionality in SAPGUI. Operations like file upload, file download, and screens with embedded complex or external controls (e.g. browser control) may fail. The EEM team cannot support such cases. Additional information on SAPGUI scripting limitations can be found in the EEM Wiki mentioned above and in SAP Note 587202.

• HTTP scripts are sensitive to changes in the user interface or the infrastructure of the monitored application. If some technical aspect is changed, e.g. upgrade or implementation of a support package, login mechanism, layout of the user interface this might break the EEM script. SAP is not responsible to keep your scripts up and running after such changes, even though SAP will try to giv e some guidance.

• HTTP scripts are not limited to SAP scenarios. But additional manual parameterization may be needed (in both SAP and non-SAP scenarios) in case a scenario is not yet covered by the built-in parameterization engine. The effort to perform adequate manual parameterization for scripts is considered as customizing and not as defect in EEM. Only limited support for additional customizing can be delivered via support tickets.

• Script complexity: Keep your scripts simple. Although there is no technical limitation, SAP will not provide support for scripts with more than 10 clicks / steps because the effort for support is too high.
• Script correctness: SAP tries to detect functional problems during script replay as good as possible automatically. The reliability of this automated detection depends, however, heavily on the type of application and on the business content. To ensure correct execution of a script SAP strongly recommends using response checks to ensure that individual clicks deliver the expected results. Example: Trying to select an item might display "item not found" (maybe due to incomplete parameterization), but the server still delivers response status "200 OK". This could not be detected automatically. Add a response check here to ensure correctness.
• A mixture of different protocol types (HTTP, SAPGUI and RFC) in one script is not possible.