Chat now with support
Chat mit Support

MessageStats 7.7.2 - Deployment Guide

MessageStats Architecture Overview Planning for Deployment Deployment Recommendations and Solutions

MessageStats Architecture Overview

•
Introducing the MessageStats Components
•
MessageStats Database
•
MessageStats Server
•
MessageStats Reports
•
Communication Between Components
•
Communication Requirements for MessageStats Reports

Introducing the MessageStats Components

MessageStats consists of several components, each of which performs a different function when MessageStats gathers information from a messaging environment.

You can install all the MessageStats components on the same computer. However, there are scenarios that might require that you distribute some or all of the MessageStats components to other computers. The following is a description of the MessageStats components and their responsibilities.

For information about prerequisites for installing the components and permissions required to run MessageStats, see the MessageStats Quick Start Guide.

MessageStats Database

The MessageStats database is the repository for all the gathered information. It is hosted within a Microsoft SQL Server database. If you have installed report packs, the core database is extended to include tables and columns specific to the report pack.

There is one MessageStats database in a MessageStats installation.

MessageStats Server

The MessageStats Server consists of the following three components:

•
MessageStats Task Processors
•
MessageStats Scheduler Service
•
MessageStats MMC Console
MessageStats Task Processors

In MessageStats, gathering units called Task Processors perform the following functions:

•
collect information from the messaging environments.
•
push the information to the MessageStats database so the information can be viewed through the MessageStats Reports.

A server on which task processors are installed is called a Task Execution Server. A Task Execution Server connects to the Exchange environment and gathers information from it.

You can install additional Task Execution Servers to distribute the gathering load as the amount of information to be gathered increases.

MessageStats Scheduler Service

The Scheduler Service coordinates the task processors that exist on each Task Execution Server. The Scheduler Service schedules the task processor activities (gathering tasks). The service also updates the MessageStats database with the status and progress of each task processor.

There is only one MessageStats Scheduler Service per MessageStats database.

MessageStats MMC Console

The MMC Console is the user interface that is used to manage the MessageStats gathering components. You create, update, and delete gathering tasks using the console. You also use the console to obtain an overall view of the gathering state of a MessageStats installation.

A MessageStats MMC Console can manage multiple MessageStats implementations (communicating through the MessageStats Scheduler Service). Also, multiple MessageStats consoles can be used to manage one MessageStats implementation.

MessageStats Reports

MessageStats Reports are presented through a web site that is hosted on an IIS (Internet Information Services) server. The web reports retrieve information from the MessageStats database.

You can have multiple MessageStats Reports web sites per MessageStats installation, though not on the same computer.

Communication Between Components

This section describes the type and frequency of communication that occurs between the various MessageStats components. By understanding the communications requirements between the various components, you can determine the topology and deployment options for a MessageStats installation.

Between Database and Reports
Between Task Execution Servers and Database
Between Task Execution Servers and Exchange Servers
Between Scheduler Service and a Task Execution Server
Between Console, Scheduler Service, and Database

Between Database and Reports

MessageStats Reports request and display information from the MessageStats database. This involves a high volume of communication between the two components. It is therefore recommended that the MessageStats database server and MessageStats Reports web server be closely connected.

For optimal performance, Microsoft recommends having SQL Server and IIS on the same computer. However, if the database and reports components are on separate computers, there must be high connectivity to ensure acceptable performance for MessageStats Reports.

Self-Service-Tools
Knowledge Base
Benachrichtigungen und Warnmeldungen
Produkt-Support
Software-Downloads
Technische Dokumentationen
Benutzerforen
Videoanleitungen
RSS Feed
Kontakt
Unterstützung bei der Lizenzierung
Technische Support
Alle anzeigen
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen