Supported Excel extensions include:

Excel Extension = string: .xlsx

Excel Extension = string: .xls (this is default)

Optional. Vector listing the fonts that Report Server should use to render UTF8-based unicode special characters. The number of fonts in the list is unlimited.

The first font should always be Lucida Sans Console. If this parameter is not included in the Report Server.cfg file, Report Server uses only Lucida Sans console to display text.

Report Server uses the first font in the list to render all characters until it encounters a character that it cannot render. It then uses the second font in the list to render that character. If that font does not render the character, Report Server uses the third font in the list to render that character, and so on, until it reaches the end of the font list. If the correct font is not listed in the vector, Report Server displays the hexidecimal value for the character.

Note: Do not make changes to this parameter while Report Server is running.

Gamma setting for .png file output. The default value is 1.6.

Note: Adobe does not recommend changing this value.

Optional. You need to modify the parameters in this vector only if you contact Adobe's license server through a proxy server.

Section identifier for parameters you set to contact Adobe's license server through a proxy server.

Section identifier for parameters you set to configure which data workbench server machines Report Server must connect to generate reports. This includes a number indicating how many items are listed in this vector.

For each server, add a serverInfo entry and complete the parameters as necessary.

The amount of memory (in KB) that you want to make available for reports and alerts. The default value is 50000.

When running reports, Report Server checks this value first, then checks the value in the Maximum Slice Size parameter. For example, if you set this parameter to 50,000 and the Maximum Slice Size to 50, Report Server runs only 50 workspaces at a time even if space is available to run more workspaces.

Note: This limit should never exceed the value set in the data workbench server's Query Memory Limit parameter, and, ideally, should be set a little lower than the Query Memory Limit to provide some leeway to other users who may be running reports at the same time.

Indicates whether to allow this Report Server's software to be updated by the data workbench server. The options are true or false. The default value is true.

Following is an example of this parameter that you can use a model:

Update Software = bool: false

Controls whether Report Server uses hardware rendering (such as the machine's graphics card) to produce report output. The options are true or false. The default value is true.

This parameter should be set to false only when you are experiencing problems with your graphics card. When set to false, Report Server does not attempt to use hardware rendering and uses software rendering by default.

The frequency (in seconds) with which Report Server prints completion status messages when queries are being run during report or alert generation. The default value is 120 seconds.

Example: Workspace queries are 62.145672% complete.

Completion messages are written to the reportserver.log and are synched to the server. This setting controls the status.txt files that are sent back and forth for each report set, so that the percent complete can be shown with thumbnails. The messages are sent whenever a report set completes or when the interval is reached, whichever comes first. Setting this higher does not effect the rate at which you see report generated in the client interface by the thumbnails, but does effect how many interim messages you see. Specifying a low value can cause the system to spend a large amount of time synchronizing data, because data is synched from Report Server server to the profile, across all the DPUs and to all connected clients each time a status.txt message changes.

The system always sends a status.txt file when a report set completes, regardless of the setting of this configuration parameter.

Number indicating how many items are listed in this vector. For each profile for which reports are to be created, add a ReportProfile entry in the Profiles vector and complete the Server and Profile parameters.

Server - The name which Report Server uses internally to identify the data workbench server. This name must be the server common name listed on data workbench server's SSL certificate.

Profile - Name of the profile for which reports are to be created. This name must match the named profile on the data workbench server machine.

The address of the SMTP server from which you want to send Report Server errors via email.

Example: mail.mycompany.com

An SMTP server is required for use of the described capabilities.

The password for logging in to SMTP server. This parameter is optional unless login is required to send mail.

An SMTP server is required for use of the described capabilities.

The email address(es) to which alerts are sent.

Example: adm1@company.com,adm2@company.com

An SMTP server is required for use of the described capabilities.

The user name for logging in to the SMTP server. This parameter is optional unless login is required to send mail.

An SMTP server is required for use of the described capabilities.

The frequency (in seconds) with which Report Server generates and sends status information to data workbench server to be displayed in Detailed Status .

The default value is 120 seconds. It is not recommended to set this to a small value, such as two minutes, because a reporting queue can take hours to run. In that case, you might consider a setting of 600 to 1200 seconds.

For more information about Detailed Status , see the Administrative Interfaces chapter of the Insight User Guide .

The frequency (in minutes) with which Report Server monitors all of the profiles listed in the Profiles vector for new reports and alerts. The default value is 10 minutes.

The time that you specify is divided among all of the profiles listed. For example, if your interval is set to 10 minutes and you are monitoring two profiles, each profile is monitored for 5 minutes. If a profile is being monitored when a new or modified report or alert is saved to the profile, the report or alert is immediately available for generation.

If the Update Interval is configured to monitor more than one profile, it is important that this setting is high enough to load all profiles within the configured time. In systems with many large dimensions configured, for example, where it might take several minutes to retrieve the initial data connection with all the element names, this setting must be long enough for that full synchronization to occur. Otherwise, the system issues a profile synch error.