Skip to Content
Technical Articles
Author's profile photo Rittika Sood

User Experience Monitoring(UXMON) Set-Up Solution Manager 7.2

Hello All,

In this blog post we will discuss about User Experience monitoring setup steps. This will be helpful for solution manager consultants to understand the functional and technical aspects of UXMON set-up.

User experience monitoring(UXMON) is a tool to monitor and evaluate the performance and availability of technical scenarios from multiple client locations, in real time. It simulates the behavior of users who access central servers from different physical locations and run business processes.

User experience monitoring setup consists of three technical steps:

  1. Recording the script (Http/Https or GUI Scripts)
  2. Editing the script in script editor(EEMEditor)
  3. Deploying the script on robots(Diagnostic Agent)

 

Preparation:

  1. Perform Solution Manager mandatory configuration
  2. Identify scenarios for scripting
  3. Identify diagnostic agents at global locations to be used as robots
  4. Identify monitoring parameters and thresholds for alerting

 

1. Recording the script: We will record a http script for order creation and schedule it to run every 2 mins.

Download EEM recorder from service marketplace and extract it.

Launch EEM recorder:

 

Business Transaction Name: BBP_WEBSHOP_INT_OTC

Executed Step Name: Step-1_Launch

Click on Launch -> Start Transaction

Internet explorer window will open in background, open the URL for which you want to record the script.

 

Click on New Step

Executed Step Name: Step-2_Login

Similarly, execute rest of the steps for script recoding as per the requirement. Once you are done click on “Stop transaction” and “Exit” recorder. Recorded script will be saved in logs folder.

 

 

2.Editing the script with script editor:

Download EEM editor from service market place as per your Solution manager SP level.

Launch Eemeditor.exe

 

Establish a connection between EEM Editor and Solution manager.

Go to File -> Editor configuration -> Editor -> Solution Manager connection and provide the required details and test connection

 

Create a project to upload the script

 

Once project is created, upload script which was recorded earlier to EEM editor.

 

After uploading the script, we can add dynamic variables to the script in editor.

As we want to execute same script for various hostnames and various server nodes, we have added two dynamic variables: hostname and server node.

 

Create txt files bbp_server_nodes.txt and hostnames_bbp.txt files for hostname entries and server nodes entries.

 

Create variables for hostname and for server nodes.

Save

 

Execute the script and resolve the errors, if any

 

Once script is executed successfully, right click on script and Upload to EEM repository.

 

3.Deploying the script on EEM editor

Execute the guided procedure from System Monitoring-> User Experience Monitoring

  1. Overview

 

2.Configure Infrastructure

 

Carefully choose the robots at various client locations for global monitoring.

 

 

3. Create the Scenarios in which scripts will be deployed.

 

Assign script to the scenario

 

4. Monitoring: User experience monitoring (UXMON) is delivered with a basic configuration containing meaningful values for all EEM parameters. These parameters can be modified as per requirement.

 

5. Alerting

 

6. Reporting

 

7. Standard Users

 

User Experience Monitoring dashboard:

Login to FIORI UI workcenter:

User experience monitoring can also be viewed in a mobile optimized view.

There are various display options (Overview, graphical, pie chart etc).

Hope this blog post helps you in understanding the key concepts of User Experience Monitoring for Solution Manager 7.2.

Please share your comments or queries. Please use below URL to post the questions.

https://answers.sap.com/tags/01200615320800000636

SAP Sources:

https://support.sap.com/en/alm/solution-manager/expert-portal/user-experience-monitoring.html

https://help.sap.com/viewer/82f6dd44db4e4518aad4dfce00116fcf/7.2.06/en-US/372dad5728904975beb24c8e87239aab.html

 

 

 

 

 

 

Assigned Tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Tim Karl
      Tim Karl

      Hello Rittika,

      very great blog! Thank you very much for sharing the knowledge

      Best regards

      Tim

      Author's profile photo Bahringer Kuhn
      Bahringer Kuhn

      Thanks for the step by step tutorial. Works like a charm! The solution worked for me thanks to the community and the members for the solution.

       

      MyMileStoneCard Login

      Author's profile photo Kavitha P
      Kavitha P

      Clear explanations , it is very useful . Thanks a lot.

      Author's profile photo Jose De La Cruz
      Jose De La Cruz

      Excellent information.

      I wonder if there is a infoprovider/infocube that could provide the 10-MIN granularity we see in the EEM Technical Monitoring to use it for Alerting in case the Availability response is not Code 202 after 2-3 pinging attempts.

      We are able to get the results after each hour, but it is a long wait to know that a system may not available after 1 hour.

      I appreciate any comments on how to find that information regarding an infoprovider/infocube that could store the 10-MIN granularity data.

      Thanks,

      Jose