Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Architecture
The following reference architecture diagram and table provide an overview of the components that compose the MainView Middleware Monitor (MVMM) product.
For more information about how to plan your installation and architecture, see Planning.
MVMM basic deployment
Tip
Click the download icon 
to download and view the presentation as a slide show for an interactive experience.
The MVMM 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).