Getting started with Rational

Integration Tester
You can use IBM Rational Integration Tester to create and run tests for various
purposes by using a broad range of tools for tasks such as synchronizing with WSDLs
and validating messages and data.
Examples are described that use SOAP/HTTP (it is not possible to show examples that
use every supported messaging product). Regardless of the messaging that is used in
your environment, the basic principles are the same and you are able to relate the
examples to your own environment. For information about installing Rational
Integration Tester, see Installing Rational Test Workbench. Detailed descriptions
of Rational Integration Testerfeatures, syntax, and functionality can be found
in Rational Integration Tester reference. More detailed examples for specific
messaging systems can be found the various plug-in guides that are provided
with Rational Integration Tester.

Rational Integration Tester overview

Before you can use IBM Rational Integration Tester, the product must be
installed and the project database must be created IBM DB2, Microsoft
SQL Server, MySQL, and Oracle are supported.

Work with Rational Integration Tester

The following is an overview of the IBM Rational Integration Tester interface
(the Workbench) and the perspectives and views that it contains.

Web services overview

How to import a WSDL into IBM Rational Integration Tester, and how to create

and run tests that are based on the operations and input parameters that are
defined in the WSDL.

Data validation
Data validation is used throughout the exercises that are illustrated. When
validation is enabled for a selected field, the returned value is matched against
the expected value.

Test data sets

So far, all of the data that are used in our example tests are hardcoded. A
more practical approach to testing, however, would be to decouple the tests
from the data. One of the more common requirements of functional testing is
to run a test through several iterations with different data used each time. To
run these tests, you need to use test data sets. Data sets, along with the
Iterate Test Data action, can be used to map test data into tags that are used
to populate data fields in a test.

Functions and decisions

A fundamental requirement for some tests is to apply logic that tests
something and takes alternative action that depends on the outcome. One of
several built-in or custom functions in IBM Rational Integration Tester can be
used to apply the logic, and you can use a Decision action to create one or
more expressions that evaluate the outcome of the function. Two possible
execution paths can be taken from the decision.

Integration and SOA testing

The following are details about the components and other terminology that are used
to describe SOA and how it can be tested in IBM Rational Integration Tester.
Terminology
Component
An element of the system under test, including both the providers of services
and infrastructure elements.
Host
A logically named machine on which components run.
Infrastructure Component
tThe applications on which our SOA depends (for example, messaging
transports, databases). Infrastructure components are logically named
objects, which have physical realization in an environment.
Interaction Pattern / Type

A template, devoid of application semantics that describes a generic pattern

for the exchange of information between agents. These templates define the
manner of interactions that take place between components (for example, one
way, request response). These templates are not limited to messaging / web
services and are the more generic description that supports testing of other
exposed operations (for example, database stored procedures).
Logical Component
A provider of services through defined operations, these components are
either the items that are to be tested or the dependencies of other
components and thus need to be stubbed or monitored.
Logical View
A view of the components, their operations, dependencies, and associated
schemas.
MEP (Message Exchange Pattern)
The defined list of interaction patterns for a selected operation, including the
interaction type (publish, subscribe, publish/subscribe, or request/reply),
schema, and bindings.
Operation
A well-defined point of exposed functionality that is provided by a service.
Operations can be both private and public (that is, whether they are visible
outside of the component within which they are defined). Also known as Entry
Point, End Point, API Call.
Performance Test
A distributed test that runs a configured load profile (for example, virtual
users) to capture key performance indicators (for example, transactions per
second, CPU load).
Physical View
A series of configured components for all of the items in the infrastructure that
is grouped into environments.
Reference (Dependency)
The relationship from an operation to another operation or component that
indicates when used, the operation requires an implementation of the
reference to be available in order to provide its functionality.
Schema
An object source that provides information about services to be tested, and
can contribute information to infrastructure components and to physical
architecture values. Specific schema types that are supported in Rational
Integration Testerinclude WSDL, XSD, DTD, Java DTO, File, and COBOL

Copybook. Other specialized schemas (for example, TIBCO BW Private Process

and Active Enterprise, SAP BAPIs, and webMethods IS schemas) are added to
a project when you are synchronizing with the associated external source.
Stub
A stand in / replacement for an actual operation, its capability depends upon
the extent that the user has "programmed" it. Stubs can also be known as
"mock objects."
SUT (System Under Test)
Ultimately is the entire enterprise-based SOA (if the Rational Integration
Tester project spanned that much content).
Synchronization Source
An object source that provides information about processes to be tested
(Operations) and connection details to infrastructure resources (infrastructure
components and physical architecture values).
Test
A series of actions that exercise a particular operation and validate its
correctness.

Get to know Rational Integration

Tester
IBM Rational Integration
Tester provides a wide range of
features and functionality that give
users the ability to test their
integration and SOA projects
successfully.

Service-oriented architecture
(SOA)
Service-oriented architecture (SOA)
explained.

SOA test strategies

SOA is more than simple web services
that provide interfaces to existing
applications.

Who uses Rational Integration

Tester?
The following profiles describe
different types of users who might

use IBM Rational Integration Tester in

helping to test an SOA.

SOA and Rational Integration

Tester
IBM Rational Integration Testers
primary intent is to simplify the
process by which the user builds tests
(that is, schema-driven message
creation, test driven development, and
so on).