This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
CRM WEB UI 7.0 version Performance Testing process. For more information, visit the Customer Relationship Management homepage.
Summary
This document describes about the performance testing of SAP CRM WEB UI using Vugen, Load runner and HP Performance Center (Controller and Load runner) tools. This document consists of Baseline, Load and Stress test procedure for SAP CRM WEB UI.
Author: Jataprolu Krishna Prathyusha
Company: Accenture Services Private Limited
Created on: 12 June 2011
Author Bio
Author is having above 5 years of experience in SAP CRM. Author has experience in Sales, Service,
Marketing, Interaction Center modules in CRM and has precise expertise in understanding the CRM system.
Pre-requisites of Performance Testing: .............................................................................................................. 4
Installation details for Performance Testing: ...................................................................................................... 4
Test Script Preparation: ...................................................................................................................................... 6
Uploading the script to Performance Center: ................................................................................................ 24
Test Script Execution: ....................................................................................................................................... 26
Test Analysis and Final Report: ........................................................................................................................ 36
Issues Faced while Executing PT: .................................................................................................................... 39
Related Content ................................................................................................................................................ 41
Disclaimer and Liability Notice .......................................................................................................................... 42
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
This documents describes about the performance testing of CRM WEB UI 7.0 using Loadrunner and HP Performance Center tools. With the rigorous load-testing functionalities of the SAP LoadRunner application, organizations can better deliver high-performing business processes and can execute, upgrade,or modify existing processes on time and within budget.
Introduction:
Performance Testing is testing that is performed, to determine how fast some aspect or scenario of a system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage. Performance testing can refer to the assessment of the performance of the system. This is used to determine the speed or effectiveness of a system, network, software program or device. This process can involve quantitative tests like measuring the response time of the server or the Transactions Per Second (TPS) etc.,
Types of Performance Testing Related to SAP-CRM – Web - UI:
Types of Performance Testing for SAP CRM WEB UI:
There are three types of performance testing can be done for SAP CRM UI.
1) Baseline Testing
2) Load Testing
3) Stress Testing
1) Baseline Testing: Single user executes each of the identified online activity and reports one at a time. The objective of Baseline testing is to determine baseline performance of the application and identify individual actions requires for fine tuning of the application. The Response Time of the server is key measure of this Testing.
For Ex: Search accounts on search screen with default option with one user login
2) Load Testing: Load testing is the simplest form of performance testing. A load test is usually conducted to understand the behavior of the application under a specific expected load. This load can be the expected concurrent number of users on the application performing a specific number of transactions within the set duration. This test will give out the response times of all the important business critical transactions. If the database, application server, etc. are also monitored, then this simple test can itself point towards any bottlenecks in the application software.
For Ex: Search accounts on account search screen with default option with „n‟ number of users login at the same point of time.
3) Stress Testing: Stress testing is normally used to understand the upper limits of capacity within the application landscape. This kind of test is done to determine the application's robustness in terms of extreme load and helps application administrators to determine if the application will perform sufficiently if the current load goes well above the expected maximum. It will be useful to test, in order to see what happens when an acceptable load is exceeded –does the system crash? How long does it take to recover if a large load is reduced? Does it fail in a way that causes collateral damage? Etc.,
For Ex: Search account on account screen with „n‟ number of user login initially and increase the user login till the system crashes
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
It can demonstrate that the system meets performance criteria.
It can compare two systems to find which performs better.
It can measure what parts of the system or workload causes the system to perform badly
Pre-requisites of Performance Testing:
The stable application which must resemble the Production environment is possible to do the performance testing. This is dangerous as if an UAT or Integration test or other tests are going on in the same environment, then the results obtained from the performance testing may not be reliable. As a best practice it is always advisable to have a separate performance testing environment resembling the production environment as much as possible.
Test conditions: In Performance Testing, it is often crucial or difficult to create the test conditions similar to the expected actual use. It is not entirely possible in actual practice to exactly replicate production system workload variability in the performance testing application.
Timing: The timing of the test conditions also crucial in the performance testing. It is critical to the cost performance of a new system which performance test efforts begin at the inception of the development project and extend through to deployment. The later a performance defect is detected, the higher the cost of remediation to fix the defect.
Installation details for Performance Testing:
Tools for Performance Testing:
HP load runner software is an automated performance and load testing product. It is used to examining the system behavior and performance, while generating actual load. HP Load Runner can emulate hundreds or thousands of concurrent users to put the application through the rigors of real-life user loads, while collecting information from key infrastructure components. The results can then be analyzed in detail, to explore the reasons for particular behavior. HP Load Runner consists of several different tools: Virtual User Generator (VuGen), Controller, load generators, Analysis and Launches. In this SAP CRM WEB UI Performance Testing Virtual User Generator and HP Performance Center have been used to prepare test scripts and execute the scripts accordingly. HP Performance Center login details should be created by the admin team of HP PC.
1. Virtual User Generator: This tool is used to prepare the test scripts for the performance testing. The
Virtual User Generator (VuGen) is used to emulate the steps of real human users. VuGen can also run
scripts for debugging. VuGen lets the user record and/or script a test to be performed against an
application under test, and play back and make modifications to the script as needed, such as defining
Parameterization (selecting data for keyword-driven testing). Vugen can be installed on the system from
HPQC Performance Center.
Vugen is used to record the scenario in WEB UI. After the recording, it will create a code in C language
automatically. We can test the scenario from the Vugen itself for one user and can correct it or modify it
if any errors occurred at the time of creation. We can even update the code at Vugen according to our
scenario. Once the script is running fine in Vugen, we can execute the script from performance center to
For Ex: Create a vugen script by executing the scenario like search accounts from account search
screen with one user login to WEB UI.
HP Load Runner supports more than 51 protocols including Web HTTP/HTTPS, Remote Terminal
Emulator, Oracle and Web Services. A protocol acts as a communication medium between a client and
a server. For example an AS400 or mainframe-based application can use a terminal emulator to talk to a
server, and an on-line banking application can use HTTP/HTTPS with some Java and Web services.
Load Runner can record scripts in both single and multi-protocol modes.
The protocol used for CRM WEB UI is: SAP-WEB.
During recording, VuGen records a tester's actions by routing data through a proxy. The type of proxy
depends upon the protocol being used and affects the resulting script. For some protocols, various
recording modes are available to further refine the resulting script. When recording web activity, HP
Load Runner allows a user to choose one of three types of recording modes:
GUI based, URL based and HTML based.
The recording mode for CRM WEB UI is HTML based.
Parameterization: Load Runner allows users editing a script with VuGen to replace recorded values in
a script with parameters. This is called parameterization. Parameterization is often used:
1. When the application needs unique data (such as user name)
2. Data dependency (such as passwords)
3. Data cache
4. Date constraints
Correlation: HP Load Runner uses Correlation to handle dynamic content. Dynamic content refers to
page components that are dynamically created during the execution of a business process, and the
value may differ from the value generated in a previous run. For Examples of dynamic content include
the multiple users‟ login to WEB UI and most importantly the unique session ID that is created each time
a user logs in. Such dynamic values must be correlated in order to run the recorded script. The script
while running will return an error if such a dynamic value has not been correlated, since the value
changes each time the user logs in.
If the dynamic content is a part of a previous server response, Load Runner can correlate that value with
future instances in which it must be sent back to the server. HP Load Runner saves the changing values
into parameters, which are used during emulation.
For Ex: Create a test script from Vugen for account search scenario for different levels (For Ex: 8 levels) of users in Organization hierarchy. The script will be created to check the timelines for each and every level user to search the accounts created by them at CRM WEB UI. For this scenario one script will be created with account search scenario by passing 8 level users as parameters.
2. Performance Center: HP Performance Center is the de-facto standard for enterprise performance
testing. Built on HP Load Runner, it includes the management framework for a web-based, globally
accessible platform that facilitates enterprise-wide testing. The login details for HP Performance
Center. Using Performance Center, you can standardize and centralize your testing resources and
build a testing CoE that supports distributed teams and enables them to collaborate across the
application lifecycle. And you can give everyone from executives to LOB managers to testers‟
visibility into project status and application quality.
Select the script as „Account Search_Me‟ from the dropdown under script field.
Assigned the number of Vusers „8‟ (i.e., the number of users assigned for Baseline Test scenario), Load Generator (Which generates Load) , Running VuGen scenarios (i.e., Simultaneously or Gradually) and Duration of Run (15 minutes, For: Time Specific running scenarios, Indefinitely: No Time Bound) for Load
Test. Then the scenario Duration of Vusers to run
Select Duration „for‟ 15 minutes to run the baseline testing for all 8 users simultaneously. End vusers also
simultaneously at a time once the duration of the time is over.
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Set the total duration of the scenario for 30 minutes (15 minutes for script execution and 15 minutes for
report generation).
Note: If the load generator connection failed at the time of executing the scenario. Go to „Project‟ in the left side options and click on „Hosts‟ to check the load generator server is active or not. Check with the PC admin team if the load generator server is showing red status at hosts screen.
Hosts Screen shot:
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Note: To cancel the run of the scenario click on „Cancel‟. Timeslot booked for this scenario have to be deleted from „Project‟ -> Timeslots. Select the timeslot booked on the screen and click on „Delete‟. Then only the timeslot
assigned for this scenario will be deleted and can be used for next run.
Timeslot Screenshot:
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Click on „Test run‟ on the HPQC and click on result URL which will display the following Rawresult page
Click on Raw Results and save the results zip file on the desktop. Open the LRA file to check the summary report. Select the required graphs and add it to the report to show the client according to their requirement.
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
The ICM (Internet Communication Manager) parameters should be noted initially before the test is
conducted. Supposing the threads at ICM is maintained as 50 and request sent by the user is more than 50,
server will start giving error as “Connection got shutdown prematurely. Hence maintain the no of requests
sent less than the thread parameter maintain at ICM”
(T-code: RZ10 and SMICM)
1. Maintain „CPIC_MAX_CONV‟ parameter in ITS Internet Transaction Server) at OS level, as after CRM 5.0 version onwards the ITS is a part of SAP CRM package.
2. For executing BI report, maintained co-relation parameters for Drill down scripts. 3. Co-relation parameters should be maintain for „F4 help‟ and „New‟ button in CRM web UI
4. Need to work with the Basis team closely while executing the scripts at on peak and off peak levels.
Network settings should be changed according the number of users used in baseline\load testing.
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
5. Most of the issues we faced while running the test script. We need to check the problem areas by keeping debugging points in the test script. We faced the issues with Correlation function modules syntax and coding errors.
6. According to the client requirement 1 – 2% errors in PT can be acceptable. 7. If the test run is giving more than the above mentioned errors, then runtime settings should be
adjusted like Network Simulation timings etc., We changed it from 129 to 999 to stop the erros. 8. According to the scenario test scripts can be executed by keeping all the coding in „Action‟ part of by
dividing the test scripts. 9. As we created one test scripts with different users we faced most of the issues at the time or
correlating the scripts only. 10. Need to work closely with the performance testing developers while creating the test scripts for the
scenarios.
SAP CRM WEB UI 7.0 - Performance Testing
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.