Home
Rational® Performance Tester
Reference Guide
This guide describes, additional topics to gain more knowledge about Rational® Performance Tester.
UI preferences
Read the UI preferences topics.
Test editor references
To understand the relevance of different UI fields in the test editor of various test extensions, read these topics.
SAP test editor reference
In SAP testing, the test editor information is divided into nine categories. This section describes the fields in each category that can be edited manually.
SAP batch input transaction details
In the SAP batch input tests, SAP batch input transactions are located in transactions and are recorded transactions that are to be run at a low level, without a SAP GUI, in order to produce a load on the SAP server.

Rational® Performance Tester
- Release Notes
  This document contains information about what's new, installation instructions, known issues in IBM® Rational® Performance Tester, and contact information of IBM Customer Support.
- System Requirements
  This document includes information about hardware and software requirements for IBM® Rational® Performance Tester.
- Getting Started
  This guide provides an overview and describes the task flows to get you started with Rational® Performance Tester. This guide is intended for new users.
- Tutorials
  This section contains the tutorials which explains the main features of Rational® Performance Tester.
- Samples
  This section describes about the sample project which can be used with Rational® Performance Tester to test the functionality of an application.
- Administrator Guide
  This guide describes how to install Rational® Performance Tester. After you install the product, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Test Author Guide
  This guide describes how to create test scripts in Rational® Performance Tester and enhances tests by applying different test elements such as dataset, variables, and verification points. This guide is intended for testers.
- Test Execution Specialist Guide
  This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending Rational® Performance Tester to support other protocols. This guide is intended for testers or test execution specialists.
- Test Manager Guide
  This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
- Troubleshooting Guide
  This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with Rational® Performance Tester.
- Reference Guide
  This guide describes, additional topics to gain more knowledge about Rational® Performance Tester.
  - Rational® Integration Tester accessibility features
    Users who have a physical disability, such as limited vision, can review the available accessibility features to use Rational® Integration Tester.
  - General reference for performance testing
    See these performance testing topics for general reference.
  - UI preferences
    Read the UI preferences topics.
    - HTTP preferences
      You can change the product behavior by changing these HTTP-related settings.
    - SAP test preferences
      You can change the product behavior by changing these SAP-related settings.
    - Citrix recorder preferences
      Citrix recorder preferences control the behavior of the recording wizard.
    - Socket Test Generation preferences
      With the socket test generation preferences, you can change how the test recorder generates new socket tests.
    - Citrix monitoring panel reference
      The Citrix monitoring panel is an optional panel that displays detailed information and control commands for each virtual user during the run of a schedule. When enabled, the Citrix monitoring panel is available during the run of a schedule.
    - Proxy recording preferences
      Use these preferences to specify a list of endpoints to ignore when recording a test with the proxy recorder.
    - Test editor preferences
      The General preferences control what happens when you move test elements, and how digital certificates are substituted. The Colors and Fonts preferences control how the editor displays dataset and correlation data. The Search and Replace preferences control the behavior of search and replace.
    - Report preferences
      Report preference settings apply to all protocols.
    - Test editor references
      To understand the relevance of different UI fields in the test editor of various test extensions, read these topics.
      - HTTP test editor reference
        In HTTP testing, the test editor information is divided into five categories. This section describes the fields in each category that can be edited manually.
      - SAP test editor reference
        In SAP testing, the test editor information is divided into nine categories. This section describes the fields in each category that can be edited manually.
        SAP test details
        In the test editor, the test element is the first element in the test suite. These settings apply to the entire test.
        SAP connection details
        In the test editor, SAP connection elements are at the top of the test site and describe the connection to the SAP server. These settings apply to the entire test.
        SAP screen details
        In the test editor, SAP screen elements are located in transactions and are the basic performance measurement unit for the test. These settings apply to the selected get event.
        SAP set details
        In the test editor, SAP sets are located in SAP screen elements and describe a user input action in the SAP GUI client. These settings apply to the selected SAP set.
        SAP get details
        In the test editor, SAP get events are located in SAP screen elements and provide a way to retrieve data from a SAP GUI object to implement verification points. These settings apply to the selected get event.
        SAP call details
        In the test editor, SAP call elements are located in SAP screen elements and describe various recorded interactions with the SAP server. These settings apply to the selected SAP event.
        SAP server request details
        In the test editor, server request elements are located at the end of every SAP screen and provide information that the server returns for the selected screen.
        SAP batch connection details
        In SAP batch input tests, SAP batch connections contain the basic connection information for a batch input test to connect to the SAP server without a SAP GUI. In most cases, these details are the same as those used when you connect manually to SAP with the SAP GUI.
        SAP batch input transaction details
        In the SAP batch input tests, SAP batch input transactions are located in transactions and are recorded transactions that are to be run at a low level, without a SAP GUI, in order to produce a load on the SAP server.
      - Citrix test editor reference
        In Citrix testing, the test editor information is divided into eleven categories. This section describes the fields in each category that can be edited manually.
    - VU Schedule editor reference
      Most VU Schedule editor settings apply either to the entire schedule or to individual user groups.
  - WSDL security editor reference
    With the Web Service Description Language (WSDL) security editor you can create and edit security configurations for a WSDL file.
- All Guides (PDFs)
  You can find the link to view or download the content of the release notes, system requirements, and persona guides of Rational® Performance Tester as a PDF file.
- Security Considerations
  You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
- Notices
  This document provides information about copyright, trademarks, terms and conditions for the product documentation.

SAP batch input transaction details

In the SAP batch input tests, SAP batch input transactions are located in transactions and are recorded transactions that are to be run at a low level, without a SAP GUI, in order to produce a load on the SAP server.

SAP element label: This is the name of the selected SAP test element as it is displayed in the Test Contents. Use this field to rename the test element, or click Restore Default to revert to the default name.

SAP Batch Input Transaction

Code: This is the SAP transaction code of the recorded transaction.
Mode: This is the mode of the batch input transaction as it was recorded in the SAP GUI.
Data table: This is the data table of the batch input transaction as it was recorded in the SAP GUI. See the SAP documentation for details on the contents of the recording.