All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Oracle is a registered trademark of Oracle Corporation.
|Published (Last):||2 January 2005|
|PDF File Size:||2.25 Mb|
|ePub File Size:||15.95 Mb|
|Price:||Free* [*Free Regsitration Required]|
All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Oracle is a registered trademark of Oracle Corporation. Java is a registered trademark of Sun Microsystems, Inc.
The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials.
SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting.
The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.
Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.
Caution Note or Important Example Recommendation or Tip Cross-references to other documentation Example text Emphasized words or phrases in body text, graphic titles, and table titles Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.
Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. This can be essential for establishing a comfort level around expected performance, and to validate that sizing estimates are accurate.
Unfortunately, it can be difficult to design real life scenarios. This guide will provide the information necessary to design HP LoadRunner scripts and scenarios that represent actual user scenarios. It also provides advice on what questions to ask your user community and functional experts to ensure you have the necessary details to create representative scripts and scenarios.
Refer to section for more information. This section provides an overview of what types of information to gather before you start developing scripts and scenarios. You will find a list outlining these skill sets and their expected contributions to the project below: Application Consultant s o Assists in identifying possible pain points o Assists in resolving business process and logic related performance problems Load Runner Consultant s o Documents, Creates and Executes Load Runner Scripts and Scenarios to be executed o Analyzes results and engage the appropriate teams for issue remediation Business Process Expert s o Creates and reviews business processes to be tested o Provides input on parameterization in scripts o Provides details on Scenario design o Works with Application Consultants to document, test and approve business process or logic changes o Provides details on SLA s BPC Technical Resources o Performs any necessary hardware upgrades or system tuning based on test results.
This scenario will be replayed against a Business Planning and Consolidation landscape to gain additional understanding of its impacts. A scenario includes a series of LoadRunner scripts. Each script contains a series of operations relevant to the business process that you are testing. Note The next section will review LoadRunner scripts in more detail. The scenario also includes the details of how the scripts should be executed, for example: How many virtual users Vusers are assigned to each script?
How should user behavior be emulated for each script in the scenario, i. When do they login? How quickly do they login? How long do they execute transactions? When do they logout? How quickly do they logout? Lastly, you are given the option to add systems to monitor during the execution of the scenario.
This is very important as it allows you to determine resource bottlenecks and correlate other metrics, such as response times, to physical system resources. When designing a scenario, the first question is What goals do we hope to achieve through testing? This is a key question, because without defining it, it will be very difficult to gauge the success of your testing.
Some potential answers to that question include: Performance testing of a particular business cycle, such as a quarter close Stress testing to validate hardware sizing with respect to the business processes that will be supported. Performance testing of logic or landscape design where you design a baseline test, make a modification to logic files or your system landscape and re-test the original scenario to verify the impact of your changes. Next, you should outline which user interactions or scripts need to developed to adequately represent the business process es that you are testing.
This can be fairly high level at this point, but should include details such as the script owner as well as a descriptive name. Note The script owner referenced above refers to a SAP BusinessObjects Planning and Consolidation user that is an expert on the business processes being represented within the script. The script owner need not have HP LoadRunner skills, but will provide more specific information on what the script should include. The next step would be for July. Lastly, you should determine what servers in your landscape will be active in your scenario so that they can be monitored during scenario execution.
Important Appendix A includes a template that will assist you in creating a high level plan for your Scenario s. More specifically, the HTTP requests from the client tier to the. This section was added to help explain what you are actually capturing with the HP LoadRunner tool. BPC communicates between the Client and. Most operations, like submitting an input schedule or retrieving a report consist of a single web service request and response. The SOAP request outlines the information you are requesting from the server.
The response details the results or status of your request. Since different users will request or submit distinct information for most reports and input schedules, we must vary some requests to reflect this variation. This is done through parameterization. The responses will vary depending on the type of call being made. For example, SOAP responses for report requests will generally contain the values returned for your query while SOAP responses to an input schedule will detail how many records were accepted, rejected, etc.
Using the information in the SOAP responses we can write functions to validate that the requests were successful. This type of validation should be included in order to create reliable scripts. Instead, it replays the communications, i. SOAP requests, which the client submits to the. This accurately reproduces system load as well as server request response times.
Note This guide will refer to this program as VuGen for the rest of this document. These scripts use an underlying protocol to capture what a script does, and later uses the same protocol to replay the script. Important Ensure that your LoadRunner Controller license includes one of these three protocols.
Before creating the scripts, it is important to plan what their purpose will be and what operations they include. An operation, in this case, refers to a unit of work.
An example of an operation could be submitting an input schedule, or running a report. Each operation should be encapsulated in a LoadRunner transaction or sub-transaction after a script is recorded. This will allow LoadRunner to effectively report the time each operations takes. Another consideration when planning scripts is parameterization. It may be helpful to further expand upon this topic. During a business process multiple users perform similar operations, like submitting data during a planning process.
In order for multiple users to submit data successfully they must submit data for different dimension members. Each user may enter data for a different entity, or account or combination of the two. The detailed data that is specific for each user entities and accounts from the example above must be represented in the script through parameterization. Parameterization allows you to configure values that will change for each iteration or user in a script which allows you to more accurately reflect actual user interaction with BPC.
Parameterization is configured for each SOAP call where appropriate. Another key aspect that must be considered is verification. Each request that is sent to the. Once your scenario and scripts have been planned you can start recording and refining your scripts. The third, Web Services, works in a slightly different way than the others. Some examples of this are during login, or when viewing Audit reports. Because of this, it is impossible to write a full coverage LoadRunner script only using the Web Services protocol.
How To Script Design When you have reached the point where you have completed the design phase, you are ready to begin recording LR scripts.
How-To Use the SAP BusinessObjects Planning and Consolidation (BPC) Toolkit for LoadRunner
Thank you provide valuable informations and iam seacrching same informations,and saved my time SAS Online Training. Lots of people are not familiar with this. Many of us studies every issue beforehand and offers you the optimised solution. We've got experienced people to give you the figure. We are going to also provide you with the figure within your budget which you are able to get in the future from now.
Download How-To Use the SAP BusinessObjects Planning and Consolidation (BPC) Toolkit for LoadRunner