You can filter the messages that a stub receives, separating traffic from client and
server applications that need to use the live system as opposed to a virtual system.
In
Rational® Integration Tester 8.0.1 or later:
Consider the scenarios illustrated in the following diagram.
- Route 1 (green): The client application sends traffic addressed to the live system. The
intercept technology decides not to intercept the traffic, so it continues to the live system. If
the message type is request/response, then the live system sends a response (not shown on diagram).
- Route 2a (solid blue): The client application sends traffic addressed to the live system. The
intercept technology decides to intercept it and sends it to the stub. The stub is either not
performing sift and pass-through, or it examines the message and accepts it. If the message type is
request/response, then the stub sends a response (not shown on diagram).
- Route 2b (solid blue & dashed blue): The client application sends traffic addressed to the
live system. The intercept technology decides to intercept it and sends it to the stub. The stub is
performing sift and pass-through, examines the traffic and rejects it, passing it back to the
intercept technology, which passes it on to the live system. If the message type is
request/response, then the live system sends a response (not shown on diagram).
The following topics describe how to use the sift-and-pass-through
capability.