Running application transaction tracing (transaction monitoring) extensions
This section describes how to run the application transaction tracing (transaction monitoring) extensions (see also Supported application transaction tracing technologies for transaction monitoring), as listed below:
- Running the Apache Web Server BTM extension
- Running the Microsoft Internet Information Service BTM extension
- Running the Sun Java System Web Server BTM extension
- Running the WebSphere Message Broker Exit BTM extension
- Running the WebSphere MQ BTM extension
- Running the BTM API for Java
- Running the BTM API for Java using JMX
- Running the BTM API for Java EE
- Running the Java EE JMS Destination BTM extension
- Running the BTM Servlet Filter
- Running the TIBCO BusinessWorks BTM extension
- Running the TIBCO EMS BTM extension
- Examples of processes and methods
- Working with AIX clustering
- Prerequisites for BTM Extensions
For information about the Extensible Agent or the performance and availability (middleware monitoring) extensions, see Running performance and availability monitoring extensions.
The following sections provide details about each technology. Each section has a technology information needed section that pertains to the transaction pathway configuration details specific to that technology. In particular:
- the details for an activity implementation
- the associations defining input and output of an activity
- the technology data usable for payload or filters
In addition, each section includes details on how to install, implement and use the extension.
Where needed, details for enabling logging to assist in configuration or troubleshooting are provided.