Configure EEM to Monitor Your End Users’ Application Issues

  • by Valton Berisha, Co-Founder, Corealm
  • April 1, 2011
Learn how to set up SAP End User Experience Monitoring (EEM) in SAP Solution Manager with enhancement package 1. See how to configure and ready SAP Solution Manager to support EEM functionality, including the proper SAP Notes you need to use.
Key Concept
SAP Solution Manager supports six phases of application life cycle management based on information technology infrastructure library (ITIL) best practices. End User Experience Monitoring (EEM) is part of the Operate phase of application life cycle management. It was introduced in SAP Solution Manager starting with Support Package 20. EEM functionality is part of SAP Solution Manager and falls under the technical operations process.

Running SAP Enterprise applications requires monitoring the end-user experience to ensure that the end users are not having any application issues. End User Experience Monitoring (EEM) in SAP Solution Manager gives you the ability to monitor your key business processes before end users are affected. EEM simulates the execution of recorded end-user business transactions as the end user was doing it by measuring availability and response times.

EEM supports both Web-based business (HTTP) and SAP GUI (thick-client) translations. Examples of Web-based end-user translations include time entry in SAP NetWeaver Portal employee self-services or creating a sales order in the ABAP stack using SAP GUI.

EEM is fully integrated into SAP Solution Manager and is the only monitoring tool that supports central administration and distributed SAP GUI support, HTTPS support, trace technology, realistic scenario, performance data, availability data, and alerting and monitoring of your productive systems from a client-side perspective. EEM has three main components:

  • Design time: The key business processes to be monitored are identified and recorded using EEM recording tools. Depending on which GUI you have deployed, the recording tools support both Web-based and thick SAP GUI transactions.
  • Configuration time: Recorded business translation scripts are taken and distributed in different locations via SAP Solution Manager diagnostic agents (sometimes called robots). The key here is that you record these transactions once and distribute to as many diagnostic agents as you need. In configuration time, the service level agreements (SLAs) are set for the end-user experience scripts as well. If the SLAs are breached, an alert can be sent out to the owners of applications or operation team in charge of supporting these applications.
  • Run time: Real-time monitoring of recorded business transactions are executed via diagnostic agents in SAP Solution Manager. Based on how often you want to execute those recorded scripts, the execution of the run time and response time is reported back to EEM dashboards.

Valton Berisha

Valton Berisha has more than 15 years of consulting experience in managing, developing, and implementing software solutions, including SAP solutions. He has been associated with several SAP implementations in various capacities. Valton is the co-founder of Corealm Consulting Company, specializing in SAP consulting — in particular, application life cycle management, SAP Solution Manager, and third-party solutions that are integrated with SAP Solution Manager. He is Microsoft, Red Hat Platform, and Novell certified.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.