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.
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.
General actions
A list of general actions available for Rational® Integration Tester.
Compare Records
The Compare Records action is used compare record layout files such as semicolon delimited files. This action does not support comparing XML files. Two distinct records can be compared for equality, or multiple records can be summed and compared to the value of a single summary record.
Configuring comparison options
After the file resources, record mappings, and (optional) filters are defined, use the Assert tab to configure the comparisons that are to be carried out within matching records.

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.
  - 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.
    - General actions
      A list of general actions available for Rational® Integration Tester.
      - Comment
        The Comment action adds comments or notes within the actions of a test.
      - Log
        Use the Log action to write a specified Output Message to the console and to an optional logging file.
      - Compare Records
        The Compare Records action is used compare record layout files such as semicolon delimited files. This action does not support comparing XML files. Two distinct records can be compared for equality, or multiple records can be summed and compared to the value of a single summary record.
        Selecting file resources and record mappings
        The file resources to be compared (expected and actual) are configured in the top half of the Config tab, and the details of each resource are configured in the same way.
        Configuring file resource filters
        Select the Filter tab to create filters that can limit the potential number of records that can match and get compared within a file resource.
        Configuring comparison options
        After the file resources, record mappings, and (optional) filters are defined, use the Assert tab to configure the comparisons that are to be carried out within matching records.
        Specifying the logging options
        To define the type of logging information and level of logging detail that is to be displayed in the console when the action is executed, use the Logging tab.
      - Map
        You can use the Map action to transform XML-based data.
      - Function
        A Function action runs a single function or composite set of functions from the registered set. Functions and expressions are loaded from a folder that is contained within the Classes folder in the project and is available to all users of the project.
      - The Run Command
        The Run Command action runs one or more commands or programs that are normally run from the command line or shell. This action can validate or store the commands output, or stop and start system resources that might be used within a test or scenario.
      - User Interaction
        The User Interaction action can present the user with information or request user input during the execution of a test (for example, to confirm an event outside of Rational® Integration Tester).
    - Flow actions
      The flow-related actions that you can use are: action group, assert, decision, pass, fail, run test, sleep, fetch test data, lookup test data, iterate test data, iterate while, and iterate through multi-value tags.
    - Message actions
      A number of messaging-related actions are available for Rational® Integration Tester.
    - Database actions
      Working with messages is a large component of the tests that you create with Rational® Integration Tester. However, in most systems, you also interact with databases. For example, you might want to check that data was added or removed from a database correctly. Or, you might want to insert data, or run a stored procedure on a database as part of a larger test. If you have the appropriate JDBC drivers and can specify the locations of these drivers to the Library Manager, Rational Integration Tester can interact with any JDBC-compliant database. After the JDBC drivers are set up, you can create a database within the Architecture School perspective, just like you do for any other infrastructure component, and can work with the database by adding actions to your tests. You can use three database actions: the SQL Command action, the SQL Query action, and the Stored Procedure action.
    - Performance actions
      Performance related actions available for Rational® Integration Tester.
    - Stub actions
      Some actions in Rational® Integration Tester are available to message-based stubs only.
  - 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.

Configuring comparison options

After the file resources, record mappings, and (optional) filters are defined, use the Assert tab to configure the comparisons that are to be carried out within matching records.

About this task

Note: The comparison of fields between configured sources is case-sensitive.

Assert tab

Procedure

Select the type of comparison to apply at runtime (Equality or Sum of) from the Comparison Type combination list.
Click to add a comparison or click to remove an existing comparison.
In a new or existing comparison row, select the columns to compare in matching records under the <Expected Source> and <Actual Source> columns.
Note: Columns that are used as record mappings are not available for comparison.
If the selected columns are numeric types (as defined in the associated record layout), you can enter an optional value under Tolerance.
Note: If a tolerance value is used, the values or sum comparison must be within + or - the tolerance value to be considered a match. If no tolerance is used, the values or sum comparison must be equal to be considered a match.

Below the comparison table, you can configure the reporting of rows that are found in one resource and not the other by enabling the wanted options.

Missing rows are reported in the test console when the action is executed.