Configuring transports to use the sift-and-pass-through capability

The sift-and-pass-through capability is provided by IBM® DevOps Test Integrations and APIs (Test Integrations and APIs) to 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.

The following table outlines the options to configure transports that use the sift-and-pass-through capability, which is provided by Test Integrations and APIs 8.0.1 or later.

Table 1. Transports that use the sift-and-pass-through capability
Transport	Version of Test Integrations and APIs	Options to configure transports
CICS®	8.5.0 or later	You can configure these transports to have a default pass-through action (see Table 2).
HTTP	8.0.1 or later
IMS™	8.5.1.1 or later
Java™ application	8.5.0 or later
WebSphere® SI Bus	8.5.1 or later
MQ telemetry transport	8.6.0 or later
SAP System	8.6.0 or later
webMethods Integration Server	8.0.1 or later
JMS application	8.7.0 or later
WebSphere MQ	8.0.1 or later	The options are as follows: Configure a default pass-through action (see Table 2). Configure a default stubbing mode for each new transport created (see the procedure below). Modify the stubbing mode of each transport irrespective of the version of Test Integrations and APIs that was used to create it. For information about configuring the stubbing mode of WebSphere MQ transports, see Stubbing settings for MQ transport.

Click Project > Preferences or Window > Preferences on the menu bar. The Preferences window is displayed.
Click Virtualization. The Virtualization page is displayed.
In the Pass-through section, double-click the transport to configure. The Pass-through Configuration window is displayed. In that window, the options that are in the Pass-through list depend on the transport that you selected.

Specify the settings for the sift-and-pass-through capability. For details about the settings, see the following table.

Table 2. Specifying the Pass-through configuration options on the Virtualization page in the Preferences window
Option	Transport	Description and instructions
Discard	HTTP IMS MQ telemetry transport WebSphere SI Bus WebSphere MQ JMS application	Test Integrations and APIs discards any message that the stub cannot process and does not send a reply.
Pass-through	CICS HTTP IMS Java application MQ telemetry transport SAP System WebSphere SI Bus WebSphere MQ JMS application webMethods Integration Server	Any message passes through to the original target of the operation. Optional: In the Delay field, enter a delay (in milliseconds).
Simulate Error	CICS	Test Integrations and APIs simulates an exception or abend. For CICS Transaction Gateway based stubs: Select a CICS return code. Optional: If CICS Abend is required, enter an abend code. For CICS Transaction Server based stubs: Enter an abend code.
Simulate Error	HTTP	Test Integrations and APIs sends a fake error message back to the client or server application. Optional: In the Delay field, enter a delay (in milliseconds). From the Status Code list, select a status code for the error. Optional: In the Status Text field, enter status text for the error.
Simulate Error	webMethods Integration Server	Test Integrations and APIs sends a fake error message back to the client or server application. Optional: In the Delay field, enter a delay (in milliseconds). In the Exception list, click a supported exception type for the error. Optional: In the Message field, enter text for the error.

Click OK to close the Pass-through Configuration window.
If you want to modify other settings in the Preferences window before you close it, click Apply to save your changes. Otherwise, click OK to close the Preferences window.