NeoLoad makes it possible to load test SAP GUI applications. Recording the SAP GUI application is the first step of the load testing process.
Warning: Before recording an SAP GUI application, the SAP GUI scripting must be enabled on server and client sides. For more information, see Enable SAP GUI scripting.
The SAP GUI application recording is accessible via:
The Record > Start SAP Recording command.
The Start Recording tool bar button. The Enable SAP recording check box must be ticked in the SAP GUI tab.
The Start Recording button in the User Paths panel. The Enable SAP recording check box must be ticked in the SAP GUI tab.
The Record Here option with a right-click on a Page, Transaction or Logical Action. The Enable SAP recording check box must be ticked in the SAP GUI tab.
Warning: Before recording the scenario, it is recommended to close all HTTP client applications (other Web sessions, Twitter client, and so on). NeoLoad records all the HTTP flows going through the machine. It is necessary to close HTTP clients or define exclusion rules in NeoLoad to avoid unwanted requests in the recording.
Enable SAP recording: The check box must be ticked to record an SAP GUI application. It is ticked by default after selecting the Start SAP recording in the Record menu.
Once the recording has started, SAP Logon allows selecting the connection to be used. NeoLoad subscribes to the SAP GUI events associated with the connection selected in SAP Logon.
SAP Actions are created from the SAP GUI events and placed in the NeoLoad User Paths tree.
Warning: Passwords are not recorded therefore they must be added in the User Path in NeoLoad.
Information: The mapping between the actions carried out in an SAP GUI client and the corresponding SAP Actions in NeoLoad are managed by a mapping file. Consequently, if an SAP Action is not supported by NeoLoad, a warning message is displayed in the "neoload.log" file. The message is "Mapping for SAP event not found". In this case, please contact the Neotys support providing them with the log files.
Warning: NeoLoad only records the objects supported by the SAP GUI scripting API.
All the SAP Actions provided by NeoLoad are available in the NeoLoad Actions panel. For more information about SAP Actions in NeoLoad, see SAP Actions.
As soon as the Recording bar is displayed, the recording starts.
The bar includes the following functions:
Clicking the Stop button stops the recording and opens the Post-Recording wizard.
Clicking the Pause button puts recording on hold. Clicking the Record button again resumes the recording.
In the Record in drop-down menu, you can select a Transaction type into which the subsequent pages visited are to be recorded.
Transaction is an editable dropdown list. It is automatically populated with Transactions of the User Path you want to update. You can also enter a Transaction name for the subsequent web pages to be recorded within that Transaction. A Transaction is used to identify and collect a group of web pages. Delete the Transaction name to end the collection of new pages within the Transaction and to allow the creation of a new Transaction.
Click the Next Transaction button to place the recorded web pages in the next Transaction of your predefined Transaction list.
Click the Prefill button to define the Transaction names to use. NeoLoad can use the Transaction names coming from an existing User Path or from a .CSV or .TXT file (Separate each Transaction by a line break).
Clicking the Insert a rendezvous point icon makes it possible to insert a rendezvous point.
SAP Actions naming
During a recording phase, NeoLoad records each action carried in an SAP GUI client. Each Action is then created as a new instance and added in the NeoLoad User Paths tree. The name of the instance is dynamically created according to:
the type of action carried out in the SAP GUI client,
and the type of object the action was performed on.
The naming format is the following: SAP GUI Action name / [object type] / [SAP GUI client interface label]