Chat now with support
Chat con el soporte

MessageStats 7.5.1 - Administrator Guide

What is MessageStats? MessageStats Information Sources Creating a Connection to Exchange Using the Console Interface Creating Gathering Tasks Default Gatherings Extending Gathering Tasks Configuring Audits Setting Configuration Properties Setting MessageStats Server Properties Setting Exchange Organization Properties Setting Exchange Server Properties Setting Task Execution Server Properties Setting Task Default Properties Compressing Tracking Log Files Using the MessageStats Reports Console Database Management Appendix A:Microsoft ASP.NET Configuration Issues Appendix B: Gathering Task Dependencies Appendix C:Troubleshooting Permission Problems

Configuring the MessageStats Server

The server on which you installed the MessageStats Scheduler Service is called the MessageStats Server. You might also install the MMC-based client console and task processors on the same server. In the treeview, the MessageStats Server is the child node of the root.

The properties tabs associated with the MessageStats Server contain the settings for the MessageStats database, the service (application) logs, and the IIS server on which the MessageStats web-based reports are installed.

To access the MessageStats Server property tabs
1
Select the MessageStats Server in the treeview.
2
Right-click and select Properties.
3
Select the tab for the properties tab that you want.

The following MessageStats Server properties tabs are available:

•
Database. See Specifying the MessageStats Database Settings .
•
Service Logging. See Configuring Service Logging .
•
Service Logging Archive. See Setting Up Archiving for Service Logs .
•
Reports. See Specifying Reports IIS Settings .
•
Scheduler Service Credentials. See Updating Security Credentials for the Scheduler Service .

Specifying the MessageStats Database Settings

The Database tab displays the MessageStats database location, the timeout settings, and the maximum number of database records per database update.

 

 
Table 1. MessageStats database settings.
Option
Definition

Locate the database on the following SQL server

Defines the location of the MessageStats database. By default, the Database tab contains the name of the database server that you specified during installation. You can edit the location if required.

Long command timeout (in seconds)

Defines the amount of time after which the task processors will time out for the gathering commands.

For a long command (such as most of the gathering tasks), the default is 3600 seconds (or one hour).

Short command timeout (in seconds)

For short commands (such as read or write tasks), the default is 60 seconds.

Use the long command timeout when connecting to the database

Used only if you want to use only the long command timeout value.

Maximum number of records per update

Sets the maximum number of database records for a database update.

Configuring Service Logging

MessageStats creates log entries during several processes. You can set scheduler service logging to record the activity of the scheduler service on the MessageStats server.

These logs can help diagnose problems. If you contact Quest Support for assistance, you may be asked to enable or change the logging level of these logs to assist in resolving your problem.

 
Table 2. Setting logging for the MessageStats scheduler service.
Option
Definition

Enable service logging

Select this option to identify the location and detail level of the logs. The Enable service logging check box is cleared by default.

Store service logs in

Specify the path location in which the log files should be stored.

Log detail level

Set the level of detail that should be included in the log files. For information about the different levels of details, see About Logging Levels .

Record errors in the Windows Application Event Log

Select this option and MessageStats also records errors in Windows Application Event logs.

You can also set logging at the task level, using the Task Logging tab.

About Logging Levels

You can define the logging level for your service logs. The following log levels are available, from the most detailed to the least detailed:

 
Table 3. Logging levels for the MessageStats scheduler service.
Log Level
Detail

Trace

Trace level logging is extremely detailed logging that includes errors, warnings, and status messages, and also low-level event details. Trace logging is only used with custom components provided by MessageStats development for diagnostic purposes. This level of logging can generate large log file and can affect system performance.

Debug

Debug level logging includes errors, warnings, and status messages, and also low-level event details. Quest Support might ask you to set logging to the debug level to identify and resolve an issue. Use debug-level logging only at the request of Quest Support, since the log files can grow rapidly and can affect system performance. These logs contain very detailed entries.

Status

Status level logging includes warnings and errors, as well as the regular flow of major events within MessageStats. Use the Status level for a new installation to include more detailed logs.

Warning

Warning level logging includes errors that appear at the Errors level. The Warning level also includes errors that occurred but from which MessageStats recovered and continued gathering. Use this level for established and stable implementations.

Errors

Errors level logging includes errors that caused a gathering task to terminate.

It is recommended that you periodically remove obsolete logs. In general, retaining one month of service logs should be sufficient for most enterprises.

The configuration for service logs does not apply to the QMSCompress.log files. The compression logs are external to the MessageStats product. The Gathering Status report includes Errors and Warning details regardless of the detail level that you selected on the General tab.

Setting Up Archiving for Service Logs

As part of service logging configuration, you can enable and configure service log archival. Use the Service Logging Archive tab to configure the following.

 
Table 4. Service logging archive settings.
Option
Definition

Enable archiving for MessageStats Service logging

Select the option to specify the time that you want to retain the service log files, and the method for handling the files once the time limit is reached. The check box is cleared by default.

Number of months to keep

Specify the length of time, in months, that you want to keep the service log files.

Time to execute archiving

Set the time at which you want the archiving process to be run.

Service Logging Management Method

Select one of the following options to handle the service logs once the time limit for keeping them has been reached:

Select Delete Files if you want the archived service log files to be deleted when the number of months you selected to retain the files has expired.

Select Move Files to Backup Location to copy the files to the path location that you specify and delete them from the MessageStats server.

Select Compress Files to Backup Location to compress the files and copy them to the path location that you specify. The compression option uses the PKZIP 2.0 file archive format.

You can also set log archiving at the task execution server level, using the Task Logging Archive tab.

Documentos relacionados