Need documentation on 'HTTP servers to stitch to when tracking' parameter

Technote (FAQ)


What is the usage of the new parameter 'KT5STITCHEVENTFILTER' added for T5 agent in Fixpack 1?


This has been identified as a DOC APAR IV36433


The new parameter shows up in the Data Analysis tab of the Web Response Time agent configuration.
The field is labeled 'HTTP (App) Servers to stitch to when tracking (comma separated list):

This configuration option was added to configure WRT for prescribing when to create outbound
stitch data for ITCAM for J2EE to use when stitching. This is to avoid extraneous stitching occurring
between the client and the application servers.

Description: HTTP (Application) Servers to stitch to when tracking
Format: comma separated list
Enter list as IPAddress:TCPPort. (Wildcards are supported)
Empty results in \*:\*.


This is a new configuration item added to specify IP addresses of WAS servers to generate Stitching data in TTAPI events.

This is only applicable if "Transaction Tracking Integration" is enabled in the WRT agent configuration, and is not required to be specified.

The default is to generate the Stitching data as previously occurred.

NOTE: If specified, it will restrict when Stitching data is generated to only those occasions when the destination IP address matches an IP address in the list.

The following scenario explains the new parameter -

Consider the following HTTP/S traffic flow:

Client ----> HTTP Server -----> Application Server

WRT is tracking the following interactions:
Client ---->HTTP Server
HTTP Server -----> Application Server

and WRT generates the TTAPI events for these interactions. These TTAPI events are then passed to the Transaction Collector and Transaction Reporter to generate a three-node topology that is equivalent to:

Client ----> HTTP Server -----> Application Server

However, an abnormal condition may occur (e.g. missing/dropped packets) between HTTP Server -----> Application Server. This loss of data may generate TTAPI events that result in a second link in the topology directly from Client ----> Application Server, skipping the HTTP Server node. The end result is that there are now two paths to Application Server:

| |
| V
Client ----> HTTP Server -----> Application Server


KT5STITCHEVENTFILTER = <Application Server IP>:<Application Server Port>

prevents stitching information being generated unless the destination IP and Port number is that of the application server. This prevents the erroneous link in the topology directly from the client to the application server.

Rate this page:

(0 users)Average rating

Document information

More support for:

Tivoli Composite Application Manager for Transactions

Software version:


Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation