Installing the TMTM transaction monitoring extensions
This section describes how to install each of the TMTM transaction monitoring extensions.
Unless specifically noted, the TMTM extensions monitor only those versions supported by the manufacturer. To view a list of the supported platforms and technologies, see Supported application transaction tracing technologies for transaction monitoring.
The Extensible Agent and TMTM Configuration Agent are required for BTM monitoring. The TMTM Configuration Agent, among other things, manages BTM monitoring configurations, enabling them to be deployed to the agent host. It also enables updates to both agent and extension components to be made available remotely.
Refer to Installing for more details on installing, configuring and running the Extensible Agent and TMTM Configuration Agent.
To control and configure the various extensions after installing, refer to the relevant reference listed in the following table.
|Apache Web Server||Monitors and reports transaction activity from Apache Web servers.||Installing the Apache Web Server BTM extension|
|Microsoft Internet Information Service||Monitors and reports transaction activity on Microsoft IIS.|
|Sun Java System Web Server||Monitors and reports transaction activity on Sun Java System Web servers.||Installing the Sun Java System Web Server BTM extension|
|WebSphere Message Broker Exit|
Monitors when messages are read into the input node of a flow, when messages enter a WMB node through an input terminal, and when messages leave a WMB node through an output terminal.
|Installing the WebSphere Message Broker Exit BTM extension|
|IBM WebSphere MQ|
Monitors messages output via put or put1 APIs using a queue or topic, and messages input via get or callback APIs using a queue or topic.
|Installing the WebSphere MQ BTM extension|
|API for Java||Provides the mechanism for an instrumented application or activity to communicate business transaction information to TMTM.||Running the BTM API for Java|
|API for Java using JMX||Provides the mechanism for an instrumented application or activity to communicate business transaction information to TMTM.||Running the BTM API for Java using JMX|
|API for Java EE||Provides the mechanism for an instrumented application or activity to communicate business transaction information to TMTM.||Running the BTM API for Java EE|
|Java EE JMS Destination||Provides the capability to consume JMS messages delivered to a JMS destination (queue or topic) within a Java EE Application Server.||Installing the Java EE JMS Destination BTM extension|
|Servlet Filter||Monitors a Java EE servlet running within either a Java EE Application Server, or a Java EE Servlet Container.||Installing the BTM Servlet Filter|
|TIBCO BusinessWorks||Monitors business transactions within TIBCO BusinessWorks.||Running the TIBCO BusinessWorks BTM extension|
|TIBCO EMS||Monitors TIBCO EMS servers by attaching to the EMS servers and monitoring the traffic flowing through them.||Running the TIBCO EMS BTM extension|