Home
Rational® Performance Tester
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.
Sending service requests with the generic service client
The generic service client enables you to send requests to services for which you do not have a convenient client and to view the responses returned by the service.
Adding static XML headers to a service request
You can add static XML headers to service requests to ensure compliance with WS-Addressing, WS-ReliableMessaging, and WS-Coordination specifications as well as other predefined standards.

Rational® Performance Tester
- Release Notes
  This document contains information about what's new, installation instructions, known problems 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 software, 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.
  - Creating tests
    To create a test, you record representative interactions with an application.
  - Editing tests
    After you record a test, you can edit it to include datasets (to provide variable data rather than the data that you recorded), verification points (to confirm that the test runs as expected), and data correlation (to ensure that returned data is appropriate for the corresponding request). You can also add protocol-specific elements to a test. When you edit a test, the modified items appear in italic type. The italic type changes to regular type after you save the test.
  - Compound tests
    You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
  - Simulating services with stubs
    Service stubs enable you to simulate the behavior of an actual service for a wide variety testing or integration purposes.
  - Sending service requests with the generic service client
    The generic service client enables you to send requests to services for which you do not have a convenient client and to view the responses returned by the service.
    - Creating transport protocol configurations
      Read these topics to configure various transport protocols.
    - Sending service requests with WSDL files
      You can send requests to services based on SOAP, Java Messaging Service (JMS), WebSphere® MQ, and Microsoft™ .NET that use a Web Service Description Language (WSDL) file to specify the contents of the service request.
    - Sending HTTP endpoint requests
      You can send requests to services that use an HTTP endpoint.
    - Sending a JMS endpoint request
      You can send requests to services that use a Java™ Messaging Service (JMS) endpoint.
    - Sending a WebSphere® MQ endpoint request
      You can invoke calls to services that use a WebSphere® MQ endpoint.
    - Sending OData endpoint batch requests
      To test services that use OData protocol, you can send requests in a batch. The request contains HTTP operations such as GET, POST, and PUT to manage data in the service.
    - Sending WebSphere Java MQ endpoint requests
      You can send requests to services that use a WebSphere Java MQ endpoint.
    - Testing all operations in a WSDL file
      You can use the generic service client to rapidly send requests to a service using all the operations in a Web Services Description Language (WSDL) file. The calls are generated with default values based on the type of data.
    - Viewing message content
      The Raw Transaction Data view displays the raw XML, text, or binary content of any service request or response that is selected in the generic service client.
    - Synchronizing a remote WSDL file
      For web services that make their Web Services Description Language (WSDL) file available from a URL, you might have to ensure that the WSDL that you work with is always up to date. By synchronizing the WSDL, you ensure that the local copy of the WSDL in your workspace is regularly synchronized with the remote WSDL.
    - Synchronizing a local WSDL file with GSC
      If you edit a local WSDL source file, the Generic Service Client (GSC) should display the changes in the UI. You must keep the GSC up-to-date with the WSDL changes to ensure that you test the latest service request.
    - Adding static XML headers to a service request
      You can add static XML headers to service requests to ensure compliance with WS-Addressing, WS-ReliableMessaging, and WS-Coordination specifications as well as other predefined standards.
    - Opening file attachments
      When a service sends a file attachment with the response, you must import it as a resource to open the attachment.
  - Emulating workloads
    You emulate a workload by creating a schedule and adding user groups/rate runner groups, tests, and other elements to it.
- 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.
- All Guides (PDFs)
  This page contains the release notes, system requirements, and persona guides for IBM® Rational® Performance Tester in PDF format.
- 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.

Adding static XML headers to a service request

You can add static XML headers to service requests to ensure compliance with WS-Addressing, WS-ReliableMessaging, and WS-Coordination specifications as well as other predefined standards.

About this task

Static XML headers are compliant with the web service specifications for service-oriented architecture (SOA). Checks are performed to ensure that the XML headers are valid.

Procedure

To add a static XML header to a request:

Open a service request in the generic service client. The location of the XML header depends on the product that you are using:
- For IBM® Security AppScan®, click the Request Stack tab and in the algorithm stack for the request, click Add > Static XML Headers.
- For IBM® Rational® Performance Tester, IBM® Rational® Service Tester for SOA Quality, or other products, click the Message tab and click Form.
On the Header bar, click Add () to open the menu.
Select the web service specification for the request to be comply with, or click More to open a detailed list of specifications.
The XML structure of the header is created.
Edit the header as required.
Some elements require completion or content to be specified. XML elements that are invalid or require attention are marked with a warning or an error symbol.