Installing and configuring Transaction Tracking Data Collector plug-ins
The Data Collector plug-ins required are determined by the systems that you want to monitor in your environment.
With the exception of MQ Tracking, CICS TXSeries Data Collector, and Data Collector for WebSphere Message Broker that can be installed by the Transaction Tracking installer, the Transaction Tracking Data Collector plug-ins each have their own installer and are installed separately. Use the information in this section to help you determine the Data Collector plug-ins that you require.
Selecting Data Collector plug-ins to install
Table 1 describes some domain tracking scenarios and the Data Collector plug-ins required.
| Scenario | Data collector plug-in required |
|---|---|
| Track WebSphere Application Server. | ARM with WASTT, or ITCAM for Application Diagnostics |
| Track interactions between ARM-instrumented applications on WebSphere Application Server and WebSphere MQ. | WASTT |
| Track transactions flowing from WebSphere Application Server through the CICS TG Gateway Daemon into CICS on z/OS. |
|
| Track ECI, DPL, IBM MQSeries and SOAP transactions on z/OS. | CICS Tracking |
| Track transactions onCICS TXSeries and CICS TG ECI V1 C Clients. | CICS TXSeries Data Collector |
| Track transactions flowing from WebSphere Application Server through the IMS to WebSphere MQ on z/OS. |
|
| Track WebSphere MQ transactions on z/OS and distributed systems. | MQ Tracking |
| Track transactions in .NET. | .NET Data Collector |
| Track transactions in the Tuxedo application. | Tuxedo Tracking |
| Track interactions between applications that pass through WebSphere Message Broker environments. | Data Collector for WebSphere Message Broker |
| Track transactions between WebSphere Message Broker and WebSphere MQ. |
|
| Track transactions from WebSphere Message Broker to SOA |
|
| Track interactions between SOA instances. | ITCAM for SOA |