SAP performance testing guidelines
SAP configuration
The SAP GUI client software must be installed on the same computer as Rational Performance Tester.
The following versions are supported with the latest patch levels:
- SAP GUI 6.20
- SAP GUI 6.40
- SAP GUI 7.10
SAP GUI 7.10 is mandatory for Windows Vista, Windows Server 2003, and Windows Server 2008
The product is optimized by default for SAP GUI 6.40 and 7.10.
To improve performance with other versions, go to...
C:\IBM\SDP\plugins\com.ibm.rational.test.lt.runtime.sap
...and run...
SAP GUI 6.20 mv bridge2java.dll bridge2javaV7.dll
mv bridge2javaV6.dll bridge2java.dllSAP GUI 7.10 mv bridge2java.dll bridge2javaV7.dll
mv bridge2javaV8.dll bridge2java.dllIf you are deploying tests on remote computers to simulate a large number of users, install the following on each remote computer:
- The SAP GUI client software, configured with the same logon properties as the client on which the tests were recorded
- The IBM Agent Controller software bundled with RPT v8
SAP performance testing relies on the SAP Scripting API and ActiveX. Verify that these options are selected when installing the SAP GUI client.
Performance test SAP recording and running requires that scripting be enabled on the SAP R/3 application server and on all SAP GUI clients installed on remote computers.
Limitations
During playback of the performance tests, each virtual user runs SAP GUI in silent mode by default (the user interface is not displayed on the screen). However, some modal dialog boxes from the SAP GUI might briefly flash on the screen.
Avoid recording tests with the SAP GUI low speed connection setting. You cannot run with a normal speed connection tests that you recorded with this setting.
Batch input tests
You can use batch input tests to simulate a large number of virtual users while minimizing the load on the virtual user computers.
Batch input tests access the SAP R/3 server at a low level, bypassing the SAP GUI interface, and therefore cannot contain any verification points or SAP GUI elements. Their main purpose is to simulate a load on the server when added to a test schedule that already contains SAP performance tests. Only the SAP performance tests will provide accurate SAP application performance measurement.
Batch input transactions are recorded in the SAP GUI and exported to the file system. You can then generate batch input tests that are based on those recorded transactions.
Rational Agent Controller requirements
By default, the Rational Agent Controller is launched as a process whenever the workbench records or runs a test. However, if you are running Windows Server 2003, 2008, or Windows Vista, and you have installed the optional Rational Agent Controller service, manually launch the Rational Agent Controller as a process before running SAP performance tests in order to display the SAP GUI during the tests.
To do this, run the ACServer.exe program, which is located in...
C:\Program Files\IBM\IBMIMShared\plugins\org.eclipse.tptp.platform.ac.win\agent_controller\bin
You must launch the Rational Agent Controller each time you log in to Windows.
Performance
When deploying performance tests it is important to use a relevant number of virtual users on a given computer.
For example, if you deploy too many virtual users on a single computer, the results produced will reflect more the load of the test computer than the load of the SAP R/3 application server.
For best results with performance tests on an average test computer with a 1 GHz processor and 1 GB of RAM, do not exceed 50 concurrent virtual users. With batch input tests, the maximum number of concurrent virtual users is approximately 500.
If you exceed the number of virtual users that a single test computer can run, the measured performance of the server will be affected by the performance of the test computer, which will invalidate the final results. When editing a schedule for long performance tests, use these recommendations:
- In the schedule editor, reduce the Test log level to None.
- In the schedule editor, set the Statistics sample interval to approximately 1/60 of the run time, for example 12 minutes for an estimated 12-hour session.
- When possible, use loops inside test suites rather than loops in the schedule. Using loops inside test suites avoids connection problems that might occur over long duration tests and emphasizes measurement of the actual SAP transactions rather than the logon process.
Long duration test runs
When running long duration test schedules that exceed 24 hours, use the long run mode to reduce resource consumption with the SAP GUI client. This mode increases the reliability of long duration test runs by running the tests in multiple process. You must enable this option for each user group in the schedule.
In long run mode, a new process is created each time the number of SAP test instances reaches a specified number.
Related
SAP performance testing overview Record an SAP test Insert a new recording into an SAP test Record a session with HTTP SAP Portal Record an SAP batch input test Change SAP test generation preferences Configure SAP R/3 for performance testing Configure the environment for batch input tests Running long duration tests