Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to clarify the understanding of the Technical Scenario and the relation to EEM Scripts and managed systems.

Overview

A Technical Scenario of type End-User Experience is a group of systems that belong together from an end-user point of view or are relevant for a business scenario. For example a user is calling a CRM application via Enterprise Portal and the CRM application is using a ECC system for some planning activities. Then the Technical Scenario should contain the Enterprise Portal, the ECC and the CRM System.

This Technical Scenario is then assigned in Solution Manager Configuration (SOLMAN_SETUP) to one or several EEM scripts calling the Enterprise Portal, ECC or CRM system.

When a script is assigned to a Technical Scenario you can use:

  • Work mode integration
    A planned downtime for a managed system will automatically stop the scripts when the downtime begins and starts them again when the workmode ends. See also Workmodes
  • E2E Trace integration
    Detailed server side system data (statistic records and traces) can be collected automatically for each EEM script execution. See also FAQ
  • Reporting
    You can use reporting to display the development of the most important monitoring data over time, to identify potential problems early, and to obtain an overview of the availability and performance.
    See also Interactive Reports for Scenarios

Side effects

Scenario is too generic

You can put also all scripts to measure availability of many systems into one scenario but then:

  • You cannot use the work mode integration in a meaningful manner because a downtime of one managed system would stop all scripts of this scenario.
  • E2E Trace collection would take longer because all systems of the technical scenario are called for each execution to collect the server side data.

 

  • No labels