How does TrueSight Middleware and Transaction Monitor work?

This topic provides an overview of TrueSight Middleware and Transaction Monitor (TMTM), its components, and who uses it. The topic includes the following sections:

What can I do with TMTM?

TMTM is a monitoring tool that helps you deal with the ever-growing challenge of monitoring transactions. TMTM offers the following core capabilities:

  • Monitor all transactions passing through middleware applications across many technologies and platforms.
  • Automatically isolate infrastructure problems to specific components in an application, greatly reducing time to problem resolution. 
  • Access end-to-end middleware transaction tracing and analyse historical data to assess trends.
  • View and customize dashboards to show how captured metrics relate to the application flow.
  • View and access historical records of the past values of middleware assets.

How do I use TMTM?

Your usage of TMTM will depend on your product role, as shown in the following table.

RoleHow do I use TMTM?

System Administrator: Installs the product, sets up security

See: Planning, Installing, Upgrading, Integrating, Defining security settings

Middleware Administrator: Makes middleware changes via TSMA

See: TrueSight Middleware Administrator

Product Administrator (typically Middleware Administrator, Application Support or Middleware Developer): Sets up events/history/monitoring/etc

See: Administering, Using

Product User (typically Middleware Administrator, Application Support or Middleware Developer): Monitors the middleware environment

See: Using, TrueSight Middleware Administrator

What are the different components of TMTM?

The different components that make up TMTM are described in the following table. For further information about these components and their role in your environment, see Architecture

ComponentDescriptionReference
Monitor ConsoleWeb-based interface that enables you to view dashboards and monitored information and configure security, events, history, and policiesMonitor Console
DatabaseContains configuration information, object repository and raw and summarized history data

History data

Overview of objects

TMTM server
Topic ServiceReceives data from the Agents and functions as a broker for the subscriber servicesTopic Service
Subscriber services

The following subscriber services can receive data from the Topic Service:

  • Application Service: makes data available to user in dashboard
  • History Service: stores data into the database for reporting and analysis
  • ProactiveNet Service: streams data to TrueSight Infrastructure Management or ProactiveNet
  • Event Service: detects and alerts on conditions
Service administration
Agentless serviceProvides an optional way in which you can monitor some applications through an "agentless" configuration where no TMTM software is installed on the monitored technology hostAgent architecture
Monitored host
ExtensionsSpecific to each technology, extensions capture data from each corresponding technology and then passes it to the Agent that publishes itExtensions
AgentsInstalled on each system, there is one operating-specific Agent that accepts the data from all extensions and publishes it to the Topic ServiceAgent architecture

While the monitoring of WebSphere MQ objects is done using TMTM, the actual management of WebSphere MQ objects, including creating and defining the WebSphere MQ queue manager objects such as queues, topics, channels, etc, is done using TrueSight Middleware Administrator (TSMA).

TSMA manages each WebSphere queue manager via a WebSphere MQ client connection. Within TSMA, the client connection and its properties are defined by a WMQ Connection (see below).

How TMTM uses agents and extensions: a brief overview

TMTM enables you to monitor WebSphere MQ, largely through the monitoring and discovery of WebSphere MQ objects and by registering the objects of interest for monitoring.  

TMTM uses local or remote agents and WebSphere MQ extensions to monitor WebSphere queue managers. When remote, monitoring is also performed via a WebSphere MQ client connection. A remote configuration is also known as "agentless" as there is no agent physically installed on the remote system. However, there is still an agent installed locally, which can lead to some confusion when talking about agentless configurations. 

When the TMTM agents and WebSphere MQ extensions have been deployed they can be used to create the WebSphere MQ server connection channel to support the TrueSight Middleware Administrator (TSMA) client connections and create the TSMA WMQ connection. For further information on the integration and connection with TSMA, see TrueSight Middleware Administrator integration options.


In this documentation, the IBM MQ and MQSeries product is referred to as WebSphere MQ.

Also, this documentation refers to the following IBM products as WebSphere Message Broker:

  • New Era of Networks Rules and Formatter
  • MQ Series Integrator
  • WebSphere MQ Integrator
  • WebSphere Business Integration Message Broker
  • IBM Integration Bus

Where to go from here

For further information on policies and objects and how they work in TMTM, see Overview of policies and Overview of objects.

To get started with TMTM, see Getting started for system administrators and Getting started for users.

Was this page helpful? Yes No Submitting... Thank you

Comments