Architecture
The following reference architecture diagram and table provide an overview of the components that compose the TrueSight Middleware and Transaction Monitor (TMTM) product.
For more information about how to plan your installation and architecture, see Planning.
TMTM basic deployment
Tip
Click the Architecture diagram to download and view the presentation as a slide show for an interactive experience.
The TMTM services do not receive data directly from the Agent. Instead, the services register with the Topic Service as subscribers for the data that they are interested in. The Agent then sends one copy of each piece of information to the Topic Service, which then forwards a copy to each registered subscribing service. This publishing/subscribing architecture minimizes the amount of data that needs to be sent, and the corresponding overhead. This architecture also makes it much easier to support new technologies since the bulk of the components are unaffected (a new extension is simply added).
| Component | Description | Reference |
|---|---|---|
| Monitor Console | Web-based interface that enables you to view dashboards and monitored information and configure security, events, history, and policies | Monitor Console |
| Database | Contains configuration information, object repository and raw and summarized history data | |
| TMTM server | ||
| Topic Service | Receives data from the Agents and functions as a broker for the subscriber services | Topic Service |
| Subscriber services | The following subscriber services can receive data from the Topic Service:
| Service administration |
| Agentless service | Provides an optional way in which you can monitor some applications through an "agentless" configuration where no TMTM software is installed on the monitored technology host | Agent architecture |
| Monitored host | ||
| Extensions | Specific to each technology, extensions capture data from each corresponding technology and then passes it to the Agent that publishes it | Extensions |
| Agents | Installed on each system, there is one operating-specific Agent that accepts the data from all extensions and publishes it to the Topic Service | Agent architecture |
Comments
The reference architecture diagram seems to be missing from this page.
Hi, Joel. Thank you for pointing out the issue with the content! We have corrected the topic with your feedback.