Performance testing recording and execution for SAPGUI relies on the SAP Scripting API and ActiveX the SAP R/3 application server and on all SAP GUI clients that are participating in the load test. As of date of this article, LoadRunner documentation does not have updated details on configuring SAPGUI for scripting such as supported versions.  However, the configurations are somewhat similar to other performance testing product which in this article, we refered to IBM instead.

The basic requirements for LoadRunner (or performance testing tools) to record SAPGUI is on two things: (a) the client machines to have the entire SAPGUI Client installed and (b) the SAP server to have scripting enabled.  (c) Other than the configurations, you may have to take note of the ports used by the SAPGUI, namely, TCP32## where ## represent the System Number.  This is especially important if the environment you are in is tight on opening of ports.

[1] Ensure client scripting enabled

• To ensure that scripting is available on the client-end, check that there is a Scripting directory located in the SAP GUI installation directory.  If this directory does not exist, then the SAP Scripting API is not installed and you must reinstall SAP GUI with the SAP Scripting API option.

[2] Ensure server scripting enabled

• Logon to SAP with a user with administrator privileges.  Administrator privileges is required to enable scripting on the server.
• In SAP, run the transaction rz11, and enter parameter name sapgui/user_scripting.
• If the parameter is not found, ensure that you have the correct support package level from SAP and contact SAP should you require further guidance on this.
• If the parameter exists, enable the parameter with the Current value changed to TRUE.  Save it and scripting will be enabled the next time you log on.

(Source: IBM, Configuring SAP R/3 for performance testing)

[3] Ensure communication between SAPGUI with SAP servers

Ensure that you have connectivity on TCP32##.  This is the port number used by SAPGUI to communicate to the dispatcher.

Also, before starting the scripting, for newbies, you may like to gather the following information as they will be used for the scripting work.  The user account used in the scripting (accessing the SAP system) should have sufficient privileges to the transactions.

• SAP Client
• System Number
• Authorization User Name
• Authorization Password
• SAP Router String (Optional)

In summary,

• Ensure client scripting enabled
• Ensure server scripting enabled
• Ensure communication between SAPGUI with SAP servers