Application Model:

EPM for SAP Portal

Application
Name

Version

Language

Supported IE Versions

Product Name

SAP Portal

SAP NetWeaver 7.0

(2004s)
SAP NetWeaver 7.3

All languages
supported by the
target application are
supported

IE8, IE9, IE10, IE11

epm-sapportal

SRM Business
Package 7.0

Table of Contents
Table of Contents ................................................................................................................ 2
Application Model .............................................................................................................. 3
Application usage............................................................................................................ 4
Captured Data ............................................................................................................. 6
EPM Modules ................................................................................................................. 6
Captured Data ............................................................................................................. 7
EPM Screens: Top Level Screen .................................................................................... 8
Captured Data ............................................................................................................. 8
EPM Screens: Dialog Screen ........................................................................................ 10
EPM Screens: Panel Screen .......................................................................................... 10
Messages ....................................................................................................................... 11
Captured Data ........................................................................................................... 11
Operations ..................................................................................................................... 15
Content Loading Operations ..................................................................................... 15

Application Model
The following is an assessment of how Knoa will report the standard EPM monitoring
metrics for this application
Knoas model is built off of the core design principles used by the Netweaver Portal.

Above: SAP Netweaver Portal follows the layout structure of the above figure
These concepts can be extended to version 7.0 and 7.3.

Masthead/Tools
7.3 Nav Bar
(This is unique
to 7.3)
Top Level
Navigation

Page Title Bar

Navigation
Panel

iView

Above: SAP Netweaver Portal 7.3

Masthead
Tools
Top Level
Navigation
Page Title Bar

Navigation
Panel

iView

Above: SAP Netweaver Portal 7.0

Application usage
The specific instance of SAP Portal that will be identified as the highest level context for
user activity will be defined as when the SAP Portal window is launched.
An SAP Portal instance is accessed through the web by opening the SAP Portal website
and logging in via the front page. The following figure illustrates this case:

Above: An example of the login page

Above: Two examples of SAP Portal application landing pages

Captured Data
The following data will be captured for the Application level of context:
Application Name
Definition:
The name of the Application contains two attributes:
1) Window Title
2) URL

EPM Modules
Modules represent the second highest level of application grouping within EPM.
The top-level navigation in SAP Portal is defined around the Top Level Navigation (TLN)
concept in the SAP Portal interface. Knoa EPM Module names are constructed from the
combination of active elements from the two TLN bars. The user is considered to have
entered a new module when an active element of either navigation bar has changed.
Following figure illustrates an example of a module in SAP Portal.

Above: An example of an EPM Module.

Captured Data
The following data will be captured for the Module level of context:
Module Name
Definition:
The name of EPM Modules is defined as the name of the active top level tab
concatenated with the active tab in the submenu.

Above: An example of an EPM Module. The module name in this case will be Guided
Procedures - Runtime

Above: An example of an EPM Module. The module name in this case will be HomeOverview

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 Screens are defined as the various web pages within the SAP Portal
instance.
SAP Portal screen can be accessed in several different ways once a new module is
entered. These include, but are not limited to, selecting an item from left-hand menu or
clicking on a form button or a hyperlink. The user is considered to have entered the
screen when the text of the element representing the screen name changes

Captured Data
Screen Name
Definition:
The name of EPM Top Level Screens are defined as the string value of the window title.
This corresponds to the Page Title Bar concept in the SAP Portal interface.

Above: Example of the User Photo Maintenance (Administration) Top Level EPM
Screen.

Above: Example of the Content Editor Top Level EPM Screen.

EPM Screens: Dialog Screen

Dialog screens are typically the fourth highest level of application navigation grouping
with EPM. We have been exposed to the following dialog types:
1) Windows dialogs
2) SAP Portal web dialogs
An EPM Dialog Screen parent can be another EPM Dialog Screen, and EPM Panel
Screen or a Top Level Screen.
Dialog Screen Name
Definition:
The name of EPM Dialog Screens is defined as the window title of the Windows or Web
dialogs generated by the user.
The following image illustrates a SAP pop up window.

Above: Above is an example of an EPM Web Dialog. The dialog screen name in this
case will be SAP NetWeaver Portal

EPM Screens: Panel Screen

EPM Panels are defined as iViews within the active SAP Portal Top Level Screen or
SAP Portal Dialog Screen. Multiple panels in SAP Portal can exist at once. A user is
considered to have entered a panel with the panel becomes visible, and is considered to

have left the panel when the panel is closed, a new page is navigated to, or the
application is closed.
Panel Screen Name
Definition:
The name of EPM Panel Screens is defined as the name of the iView that is visible to
the user.

Above: an example of iViews in SAP Portal. The names of each of three iViews are
Portal Favorites, Top News and Inbox.

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.
Knoa EPM Messages are defined as errors that are displayed within the SAP Portal
window.

Captured Data
Message String
Definition:

The string of EPM Messages is defined as the inline error message as displayed within
the SAP Portal window.
The following figures illustrate various status messages.

Above: Example of an error message being displayed within the SAP Portal instance.
The message that is captured in this case is Portal Runtime Error

Above: Example of an error message being displayed within the SAP Portal instance.
The message string that is captured in this case is Item not found

Above: Example of an error message being displayed within the SAP Portal instance.
The message string that is captured in this case is There are no items to display

Above: Example of an error message being displayed within the SAP Portal instance.
The message string that is captured in this case is The name you entered already exists
in your Favorites menu. Would you like to overwrite it?

Above: An example of in-page errors reported by SRM and Shopping Cart within SAP
Portal
The messages that will be reported in the above case are:
-

Enter Confirmation number

Message Details
Definition:
Along with the string of the message, other data points are collected about the message
to enhance the context. These attributes are only collected if they are available in the
interface. Messages can be contained within Top Level Screens, Panel Screens and
Dialog Screens.
These details are also contained in the Message name as attributes, and can therefore
be used to map the message as well.
Icon File Name

This is the filename of the icon that is present along with a message

Above: An example of an icon appearing with a message.

Icon ID

This is the HTML id attribute of the icon web element

Message Text ID

This is the HTML id attribute of the message itself

Icon Class

This is the HTML class attribute of the icon web element

Text Color

This is the color of the text as it appears to the user. The value is in hexadecimal.

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.
Operations can be contained within Top Level Screens and Dialog Screens.

Content Loading Operations

Operation Name:
If the button press is a on a web button, then the name of the button or tab that is clicked
to induce the operation is the name.
If a dropdown menu is used to instigate content loading, the operation name is the
selection that was made.
Operation Attributes:
The following attributes are tracked when available for each operation.
- Press Type
- Icon File Name
- Element Class
- Element ID
- Element Name
Start Time:
Operation-inducing click
End Time:
Depending on the results of the operation, one of the following end times can apply:

Content of the resulting page has completed loading.

Dialog is opened
Dialog is closed

Examples:

Above: In addition to the operation attributes, the Operation Names are Select All,
Deselect All, Refresh, Synchronize

Above: In addition to the operation attributes, the Operation Names are: Alerts,
Notifications

Above: In addition to the operation attributes, the Operation Name is: New and In
Progress Tasks

Above: In addition to the operation attributes, the Operation name is: Unification
Synchronization

Above: Button presses introduced by SAP Netweaver 7.3. The operation names are the
string labels of the menus and hyperlinks that are pressed.

Above: Examples of operations monitored in SRM within SAP Portal

Above: Examples of operations monitored in SRM within SAP Portal include the yellow
button as well as the tabs along the top