SAP Fiori

SAP Fiori is a predefined framework that automatically correlates the dynamic parameters of SAP Fiori and SAPUI5 applications. These applications generate values that change on every request, such as session identifiers, the Cross-Site Request Forgery (CSRF) token, and OData ETags.

When you enable the framework, NeoLoad applies predefined rules during a dynamic parameter search to extract each value and inject it into the right requests. The framework also supports the WebSocket technology that SAP Fiori uses for push channels.

Before you start

You will need to enable the framework. To do so, follow these steps:

  1. Go to Edit > Preferences > Frameworks.

  2. Select SAP Fiori in the Framework list.

  3. Make sure the parameters you need are selected in the Parameters list, then select OK.

Apply the framework to a recording

The SAP Fiori rules run during a dynamic parameter search. To correlate a recorded SAP Fiori user path, follow these steps:

  1. Record your SAP Fiori user path.

  2. Run a dynamic parameter search, either in the Post-Recording wizard or from the Design > User Paths tab with the Search button.

  3. Select the SAP Fiori rules in the list of matching framework rules, then complete the wizard. NeoLoad sets the variable extractors and replaces the recorded values with the extracted variables.

  4. Check the user path to confirm the requests return the expected responses.

Predefined parameters

The SAP Fiori framework includes the following predefined parameters. For the value each parameter handles, check out this table:

Parameter

Description

SAP_CSRF_Token

The CSRF token that secures OData write requests.

SAP_AjaxSecKey

The AJAX security key used by SAPUI5 requests.

SAP_CRB_Redirect

The client redirect value returned during application bootstrap.

SAP_JSESSIONID

The Java application server session identifier.

SAP_ZSessionID

The secondary SAP session identifier.

SAP_Route

The routing value used for server load balancing.

SAP_WS_WindowID

The WebSocket window identifier.

SAP_WS_SessionID

The WebSocket session identifier.

SAP_WS_PrSessionID

The WebSocket private session identifier.

SAP_Action_Path

The action path used in SAP requests.

SAP_Moin

The message object identification number used in SAP requests.

SAP_SessionID

The SAP session identifier.

SAP_SSO_Token

The Single Sign-On (SSO) token extracted from the MYSAPSSO2 cookie.

SAP_Contextid

The context identifier that keeps OData sessions stateful.

SAP_ETag

The ETag header used for OData concurrency control.

SAP_OData_ETag_Body

The ETag value extracted from the OData response body.

What's next

Now that the SAP Fiori framework is set up, here's what you can do next: