Home
Rational® Integration Tester
Reference Guide
This guide provides the topics to help the Integration tester use the product by using the user interface, commands or scripts. This guide is intended for Integration testers.
Messages
Rational® Integration Tester can publish and subscribe to messages as part of a test. A message normally consists of two parts: a header and a body. The header usually adheres to a predefined logical construction, while the structure of the body can be more arbitrary.
Message headers
Message headers contain metadata about the message itself (for example, sender and destination details, message properties, message type). Headers for different transports contain different types of information.

Rational® Integration Tester
- Release Notes
  This document contains information about What's new, installation, known issues, and contact information of IBM Support.
- System Requirements
  This document includes information about hardware and software requirements for IBM® Rational® Integration Tester.
- Getting Started
  This guide provides an overview and describes the tasks to get you started with Rational® Integration Tester.
- Administrator Guide
  This guide describes how to install Rational® Integration Tester. After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
- Tester Guide
  This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
- Test Manager Guide
  This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
- Troubleshooting
  While working with Rational® Integration Tester, you might encounter some problems that you can easily troubleshoot.
- Reference Guide
  This guide provides the topics to help the Integration tester use the product by using the user interface, commands or scripts. This guide is intended for Integration testers.
  - Rational® Integration Tester overview
    This section provides an overview of Rational® Integration Tester, including information about projects and files, the Rational Integration Tester user interface, environments, and project settings and preferences.
  - Architecture School
    Use the Architecture School perspective to build a system under test by using the logical, physical, and synchronization views. You can also use this perspective to manage the schemas available in your project.
  - Recording Studio
    With Rational® Integration Tester, you can record events (messages or database interactions) sent to and from the system under test. Use Recording Studio to control what parts of the system should be recorded. These parts could be specific parts of the system infrastructure or specific services using that infrastructure. You can then use the recorded events as a source of tests and other interactions with the system. In Recording Studio, you can record the traffic over a number of different transports.
  - Test Factory
    The Test Factory perspective is one of the main areas in Rational® Integration Tester. You can create all the tests and the required artifacts/data to support them.
  - Test Lab
    You use the Test Lab to execute test assets, repair tests, and open test assets for editing directly from this perspective. You can execute all of the tests, test suites, and stubs that are created in Test Factory.
  - Results Gallery
    You use the Results Gallery perspective to view an execution summary and detailed coverage, error, and performance reports for executed test suites and for test cases that were executed within a suite or as part of a test cycle.
  - Messages
    Rational® Integration Tester can publish and subscribe to messages as part of a test. A message normally consists of two parts: a header and a body. The header usually adheres to a predefined logical construction, while the structure of the body can be more arbitrary.
    - Selecting transports and formatters
      The first step in building a message is to select a transport and formatter, available at the top of the message Config tab.
    - Message headers
      Message headers contain metadata about the message itself (for example, sender and destination details, message properties, message type). Headers for different transports contain different types of information.
    - Message bodies
      The message body is constructed below the message header in publishers and subscribers.
    - Using repeating and optional elements
      You can use Rational® Integration Tester to create repeating elements within a message from a test data set or to read all values from repeating elements in a received message.
    - Formatting a message with MIME, S/MIME, DIME, and multipart content
      When you are working with messages that can contain multiple parts, you must format the message as a Multipurpose Internet Mail Extensions (MIME) message. You can also apply a MIME or a Direct Internet Message Encapsulation (DIME) schema to the message. You can apply the secure MIME (S/MIME) standard to encrypt or digitally sign outbound messages.
    - Adding attachments to a message
      Attachments can be added to parts of a message by right-clicking the wanted node and selecting Add Attachment from the menu.
    - Configuring the XML message properties for test actions
      By using message properties in Rational® Integration Tester, you can configure how message content is treated in test actions (for example, Publish, Subscribe).
    - Creating messages and applying them to tests
      You can create a message that contains requirements and drag that message onto an action in a test. After you create a message, you can build it by specifying the transports and formatters.
    - Messaging transports, formatters, and dynamic formatters
      Rational® Integration Tester uses a decoupled, plug-in architecture to provide maximum flexibility in regards to the messaging transport software in use by a system under test. A formatter translates messages from the native transport format (for example, TIBCO Rendezvous) to the internal format understood by Rational Integration Tester, known as A3 (Accelerated Adaptor Architecture).
    - The Field Editor
      Use the Field Editor to specify that a message field (data attribute) be populated by using or fulfilling certain criteria. Open the editor by double-clicking a field or element name within a message or a stub, by or right-clicking the field and selecting Contents > Edit.
    - Troubleshooting: Messages
      You can use a workaround to a problem that you might encounter when you work with message fields.
  - Schemas
    Rational® Integration Tester can handle many types of content. For the product to be able to interpret the variety of content types, it must associate a content format description, or schema with the content.
  - Database resources, connections, and bindings
    Rational® Integration Tester can interact with any database that supports connectivity through the JDBC specification. These interactions can be used to extract or update data where necessary, and test data sets can be taken directly from database table content.
  - Identity stores and SSL
    An identity store can group a collection of one or more certificates that can be used in IBM® Rational® Integration Tester to validate and authenticate connections that use SSL. After you create an identity store, you can use it to enable SSL communications in various messaging transports.
  - Scripting within tests and stubs
    You can use scripts in Rational® Integration Tester that include the Rational Integration Tester legacy scripting language, ECMAScript (such as JavaScript™), or any third-party scripting language that you install.
  - External tools
    Rational® Integration Tester is primarily GUI-based, but you can also run or view tests, suites, and stubs outside of the Rational Integration Tester.
  - Test actions
    Actions are the building blocks of a test. A test consists of a series of steps and each step is an action. Actions can be defined for tests and stubs.
  - Formatting and parsing date-time patterns
    For some fields in Rational® Integration Tester, you can define patterns for date-time formatting. Pattern letters are repeated, as their number determines the exact presentation of the date-time information that they represent.
  - The Add Numbers service
    The Add Numbers service, included with Rational® Integration Tester, provides a simple way to generate messages that you can observe with topology discovery or capture in Recording Studio.
- 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 product documentation.

Message headers

Message headers contain metadata about the message itself (for example, sender and destination details, message properties, message type). Headers for different transports contain different types of information.

JMS

The following images illustrate a few different transport configuration dialogs, each containing different message header fields:

TIBCO Rendezvous

HTTP

In case of HTTP transport, Rational® Integration Tester supports both the Content-Encoding header and the Transfer-Encoding header that are present in reply messages. The encoding types supported for each header are gzip and deflate. Image of the HTTP Headers tab in messages

Image of the HTTP Headers tab in messages

These header values are used in the send request message as well as in the reply or response received.

GraphQL

When you create messages that are based on the GraphQL schema, the Content-Type header is automatically set with the value as application/gql.

Note: You cannot configure or change the default value of the Content-Type header.

JSON

When you create messages that are based on the JSON schema, the Content-Type header is automatically set with the value as application/json.

Note: You cannot configure or change the default value of the Content-Type header.

You can find more details about configuring protocol-specific transports and headers in Integration Testing.