Application Model: EPM for SAP GUI Scripting

Transcription

1 Application Model: EPM for SAP GUI Scripting Application Name Version Language SAP GUI 640, 710, 720 (all patch All supported SAP GUI versions) Languages 10}

2 Table of Contents Table of Contents... 2 Application Model... 3 Application usage... 3 User Identification... 4 Captured Data... 4 EPM Modules... 5 Captured Data... 5 EPM Screens: Top Level Screen... 6 Captured Data... 6 EPM Screens: Dialog Screen... 7 Messages... 8 Captured Data... 9 Operations Standard SAP GUI Toolbar Buttons Standard SAP GUI Buttons Standard SAP GUI Shell Toolbar Buttons Standard SAP GUI Dialog Buttons Standard SAP GUI Image Buttons Standard SAP GUI Tab Buttons Standard SAP GUI Web Buttons F4 Dialog Monitoring }

3 Application Model Based on the feasibility analysis performed on the SAP GUI application, Knoa can instrument its standard EPM monitoring and metrics for this application. The following is an assessment of how Knoa will report the standard EPM monitoring metrics for this application: Application usage The specific instance of SAP GUI that will be identified as the highest level context for user activity will be defined as when the SAP GUI window is launched. An instance of SAP can be accessed in any of the three following ways: 1) SAP Logon Pad The pad contains a list of SAP Systems to log on to. The figure below illustrates this case. 2) Desktop Shortcut Double click on a desktop shortcut to a T-code 3) Embedded inside of a portal web page SAP GUI instance can be launched within an instance of SAP Portal. The figure below illustrates this case with Enjoy Mode turned off. 30}

4 User Identification The user name used to login to the active SAP GUI session will be tracked. The user name is always available in the bottom right expandable menu. Above: An example of the bottom right expandable menu. The user name can be found here. In this case, the user name is SOLMANADMIN Captured Data The following data will be captured for the Application level of context: Application Name 40}

5 Definition: The name of the Application contains the following attributes: - SAP System name - SAP Server name - SAP Client ID Default Maps: The SAP System name will be used as the application name by default. EPM Modules Modules represent the second highest level of application grouping within EPM. Modules represent the second highest level of application grouping within EPM. Knoa EPM Modules are defined as SAP GUI T-Codes. A T-Code is the code name for a SAP transaction. These are application modules which encapsulate and represent business workflows. The following figure shows the SAP T-Code SESSION_MANAGER: 1) SAP Menu 2) SAP Command Field A new EPM Module is considered to be started when a new T-Code is entered. Captured Data The following data will be captured for the Module level of context: Module Name The name of the Module contains the following attributes: - SAP T-Code 50}

6 Default Maps: The T-Code name will be used as the EPM Module name by default EPM Screens: Top Level Screen Top Level Screens represent the third highest level of application navigation grouping within EPM. Screens exist within the context of a Module. Knoa EPM Top Level Screens are defined as the various pages accessed within a T- code. The EPM Screen name is defined as the top level title on each of the pages. A new Top Level Screen is considered to be started when the top level title changes. Captured Data Screen Name Definition: The name of the Module contains the following attributes: - Top level title on the active page - SAP Program of the active page The following figure illustrates the EPM Screen name with Enjoy Mode turned on: Above: Above is an example of an EPM Screen. The top level title in this case will be Info Records per Material 60}

7 The following figure illustrates the EPM Screen name with Enjoy Mode turned off: Above: Above is an example of an EPM Screen. The top level title in this case will be Info Records per Material Default Maps: The top level title of the active page will be used as the name of the Top Level Screen by default. EPM Screens: Dialog Screen The following dialog types have been discovered: 1) Windows dialogs 2) SAP GUI dialogs An EPM Dialog Screen parent can be another EPM Dialog Screen, and EPM Panel Screen or a Top Level Screen. A new EPM Dialog Screen is considered to be started when a Windows dialog or an SAP GUI dialog is generated. Dialog Screen Name Definition: The name of the Dialog Screen contains the following attributes: - Window title of the dialog 70}

8 Above: Above is an example of a SAP GUI dialog. The window title in this case will be Material Number (1) Above: Above is an example of a SAP GUI dialog. The window title in this case will be Error Default Maps: The window title of the dialog will be used as the name of the Dialog Screen by default. Messages Messages are defined as any text that is used to communicate with the user. Messages can either report the status of an application, or prompt the user for an action. Messages are defined as two types: 1) Non-dynamic messages in the status bar 2) Text within SAP GUI message dialogs that prompt the user for an action or report an error 3) Text within Windows dialog boxes prompting the user for action or report an error 80}

9 Above: An example of a non-dynamic message in the status bar. The messages that will be reported in the above case are: - Name or password is incorrect. Please re-enter Above: Above is an example of a SAP GUI message dialog. The messages that will be reported in the above case are: - The number does not lie within the number range interval Captured Data Message String Definition: The name of the EPM Message contains the following attributes: - The string within the dialog box or the status bar that is visible to the user Default Maps: The string within the dialog box or status bar will be used as the Message contents by default Message Details Definition: Along with the string of the message, other data points are collected about the message to lend enhanced context and to allow messages to be mapped easily. These attributes will be collected when they are available. Icon Name This is the filename of the icon that is present along with a message Icon Tool Tip This is the tooltip label associated with the icon 90}

10 Message Type Defined using the SAP scripting API as one of the following: o Success o Warning o Error o Abort o Information Operations Operation response times are defined as how long it takes for the target application to execute the specified task in which the end time can be defined as any point that characterizes the end of the execution. Standard SAP GUI Toolbar Buttons - Button tooltip label - Icon file name if available Operation-inducing click End of Interpretation Time, which ends with content of the page being rendered to the Examples: Above: A sample of standard SAP GUI Toolbar Standard SAP GUI Buttons - Button tooltip label - Button text label - Icon filename if available Operation-inducing click 100}

11 End of Interpretation Time, which ends with content of the page being rendered to the Examples: Above: A sample of standard SAP GUI buttons Standard SAP GUI Shell Toolbar Buttons - Shell button tooltip label - Button text label when available - Icon filename if available Operation-inducing click End of Interpretation Time, which ends with content of the page being rendered to the Examples: Above: A sample of standard SAP GUI buttons Standard SAP GUI Dialog Buttons - Dialog button tooltip label - Icon filename when available Operation-inducing click End of Interpretation Time, which ends with content of the page being rendered to the 110}

12 Examples: Above: A sample of standard SAP GUI dialog button Standard SAP GUI Image Buttons - Image button tooltip label - Icon filename when available Operation-inducing click End of Interpretation Time, which ends with content of the page being rendered to the Examples: Above: A sample of standard SAP GUI image buttons Standard SAP GUI Tab Buttons - Tab Button Operation-inducing click End of Interpretation Time, which ends with content of the tab being rendered to the Examples: Above: A sample of standard SAP GUI tabs 120}

13 Standard SAP GUI Web Buttons - Web button tooltip label - Icon filename when available Operation-inducing click End of Interpretation Time, which ends with content of the tab being rendered to the Examples: Above: A sample set of standard SAP GUI web button types Standard SAP GUI Shortcuts - Shortcut combination entered to trigger operation Operation-inducing keyboard press End of Interpretation Time, which ends with content of the tab being rendered to the Examples: F1, Shift+Ctrl+0, Ctrl+R 130}

14 F4 Dialog Monitoring The SAP Windows GUI scripting API has a known issue with amodal dialogs generated by hitting the F4 key. These dialogs are not supported by the GUI Scripting API as per the following SAP note: _scripting_not_supported_in_control_mode_f4.pdf For dialogs of this type, the Knoa monitoring template: - Will monitor usage - Will not monitor Messages - Will not monitor Operations Please see the following section of the EPM 7.0 documentation for more information about configuring the SAP GUI Scripting API in preparation for Knoa monitoring: 140}