Skip to main content

Application settings

Application metrics

Options:

  • Application log retention: The number of days that application log entries are saved. After this specified time limit, older entries are removed from the application log table in the database.

    The time limit setting (how many days worth of log information is saved) will affect the displayed log information if you filter for a specific time frame (using the Before text box).

  • Application log verbosity: This allows you to determine how much information is written to the Data Hub database table.

Options:

All

Writes all events to the table.

Off

Writes no events to the table.

Critical

Writes only Critical Error events to the table.

Error

Writes only Error and Critical Error events to the table.

Warning

Writes only Warning, Error, and Critical Error events to the table.

Information

Writes only Information, Warning, Error, and Critical Error events to the table.

Verbose

Writes details about Information, Warning, Error, and Critical error events to the table.

Activity Tracing

Writes Activity, Information, Warning, Error, and Critical Error events to the table.

Note

Take care when using this setting as some options can lead to large amounts of space being used for data retention. In general, the settings record more information as you move down the list, with ActivityTracing retaining the most information.

  • Background Task Log Retention. This allows you to control how long entries are saved in both the activity log and the application log within the database. This setting's value represents the number of days these log entries are saved. The default value is 30 days.

  • Log User Actions. This allows you to save all user application interactions to a database table that can be analyzed to trace performance issues. (Its default setting is True).

    • Use the pre-built auditing solution (included with the Data Hub data model feature) to analyze the information in this database table.

  • Send product usage data. This allows you to control if application usage information is periodically collected by the LicenseReports.json file in the diagnostics package. This information is not automatically sent for diagnostics support.

    • To disable data collection, change the default True settings to False.

Optional

  • Seq API Key. Enter the API key for the specified SEQ logging service if needed, to enable identification of multiple Data Hub instances logging to the same server. Changes made to this setting are applied during the next application pool recycle.

  • SEQ URL. Enter the address of an existing SEQ logging server that will receive events logged by Data Hub. This SEQ log, if configured, is populated in parallel with the default internal application log. Both logs will be available for review and contain comparable information. Any changes made to this setting are applied during the next application pool recycle.

    Note

    SEQ is a third-party, structured logging server. It provides rich event data and powerful filtering tools to make the analysis of large and complex event logs easy. To use SEQ with Data Hub, you first need to purchase and install it.

  • User Action Log Retention: Specify the number of days that user application interaction table entries are saved. Once this time limit is reached, these older entries are removed from the corresponding table in the Data Hub database.

    Note

    Do not set this limit too high and save too many days' worth of information as it can lead to a large amount of space being used for data retention. The recommended default value is 30 days

Background tasks

Options:

  • Background tasks check interval. Uses a Windows scheduled task to ensure the event engine is running so that models are processed and publications are received on time. Setting the value to zero removes the check. Changes will apply to the next application pool recycle.

  • Background tasks evaluation interval. Sets the time in seconds between the event engine checking if any events have been triggered. Setting the value to zero prevents publications and model processing from being triggered by events.

  • Maximum simultaneous background tasks. Sets the maximum number of worker threads allocated to the event engine for use in generating publication distributions and processing data models.

  • Maximum slice recipient. Limits the number of recipients for a sliced publication rule.

  • Publication rule timeout. Sets, in minutes, the maximum waiting time to generate a publication for a single recipient.

Data modeling

Options:

  • Data Source process connection timeout. The maximum amount of time, in seconds, provided for a data source process to start.

  • Data Source process idle timeout. The time, in seconds, until an idle data source process is removed from the pool.

Legacy features

You can use the Legacy Features options to specify whether legacy resources are available in the Data Hub application.

Note

You need specific license permissions to access these legacy options and the corresponding resources and features.

The following legacy resources/features can be controlled:

  • Cube Configuration Resource.

  • Deploy to cube Option.

  • Reporting Services Resource.

  • Scorecard Resource.

  • Slicer Resource.

Features that are selected (checked) will be available in the application, while any non-selected features will not appear.

Licensing

Options:

  • License report retention: License report records older than this value (in days) will be automatically deleted from the database. A value of "0" (zero) will allow the database to retain the records indefinitely.

  • License update check frequency: The frequency, in seconds, that the license update schedule is checked.

  • License update schedule interval: The schedule time interval for the next background license update. A setting of 00:00:00 means that this setting is ignored and an entire month is used as the interval.

Mail

Options:

  • Enable SSL: To specify whether the SMTP client uses Secure Sockets Layer (SSL) to encrypt the connection

  • SMTP Port: The port used to establish a connection to the SMTP Server. The default is port 25.

  • SMTP Server Name: The network's SMTP server's name or IP address through which emails are sent.

  • SMTP User Name and SMTP User Password: (optional) The account and associated password to use if authentication to the SMTP server is required.

  • Service Email: The email address from which publication rules are sent. (Ensure that the address is allowed by the SMTP server.)

Miscellaneous

Options:

  • Allow Insecure Gateways - Enabling this option allows New Data Gateways to be downloaded from insecure Data Hub instances.

    Important

    Enabling this option is a security risk. It is recommended that you use a security certificate to protect data and credentials during transmission.

  • Allow Scripts in Rich Text - If this setting is set to False (the default), it prevents JavaScript from being executed inside Rich Text Object resources to reduce the attack surface. Change the setting to True only if you explicitly need to allow scripts to run inside the Rich Text Object resource

  • External Router URL - This is the URL of the application router, which must be resolvable from any client. If you are using a web farm, this should be set to the external URL of the master node. This URL should be entered if you are using a data gateway and web farm is enabled. If this setting is left blank, the value of the External URL setting will be used instead.

  • External URL - Represents the base URL of the application. This URL must be resolvable by any client.

  • Microsoft Translator Text API Key - Enter a Microsoft Translator Text API Key to enable translations Auto -translate feature.

  • Prevent Consumer Default Drill-through - This allows you to control the default drill-through feature for users in the Consumer view.

    • When the setting is set to True, the Create Drill-through option will then no longer appear in analyses and other resources for users in both the Designer view and the Consumer view, nor can these users double-click an analysis cell to drill through on it. They can still drill up and down within an analysis and open custom drill across resources if these have been added to the resource.

    • When set to False (the default value), no restrictions are placed on the drill-through capability.

Performance

Choose BelowNormal to improve server responsiveness during periods of high load on printing services, for example, while publishing multiple publication rules with large attachments. Options:

  • Active Directory Limit. Sets the maximum number of returned users or groups from a single Active Directory search. This value must be greater than 0 and equal or less than 1000. For more information on this type of search, see Adding Users and Groups to a Policy.

  • Cache Timeout. Sets the number of minutes until the cache expires.

  • ConnectionTimeout. Set, in minutes, the amount of time a connection will remain open.

  • CubeCacheTimeout. Sets, in minutes, the amount of time until cube-related caches (including the query cache) expire.

  • Cube Last Changed Checking. Sets thoroughness when determining whether or not to drop cube-related caches. In general, the more thorough the checking, the longer the operation takes to perform.

    Optional settings:

    • Thorough - Checks if any part of the cube has been changed.

    • TopLevel - Checks if the entire database has been updated.

  • None - No checks are performed, and the cache is dropped after the period specified by the Cube Cache Timeout setting.

  • Database Clean-up Period. Specify how many days between database clean-ups. The default is set to 14 days.

  • Database Clean-up Time. Hour of the day during which database clean-up begins. Possible values start at 0 for midnight.

  • Database Command Timeout. Sets, in seconds, the execution timeout for a query to run against the Content database.

  • Default Columns Per Screen. Sets the default number of columns displayed per screen on new analysis and Drillthrough resources. This setting only impact reports displayed online (in the application). Printing is not affected.

  • Default Drill-through Row Limit. Sets the default value for the maximum number of rows displayed in new Drillthrough resources.

  • Default Query Timeout. Sets, in seconds, the default query timeout used by cube servers.

  • Default Rows Per Screen. Sets the default number of rows displayed per screen on new analysis and Drillthrough resources. This setting only impact reports displayed online (in the application). Printing is not affected.

  • Maximum Cube Connections. Limits the number of OLAP connections open at any time.

  • Named Set Display Cell Limit. Sets the maximum number of Named Set cells to display on the Named Set resource designer and Rich Text Objects

  • Pagination Measurement Timeout. When rendering a PDF file from a print preview or other operation, a separate service is used. If the service doesn't respond within the specified number of milliseconds, an error popup message is displayed.

  • Pagination Service Lifetime. When rendering a PDF file from a print preview or other operation, a separate service is used. After the specified number of uses, the service is closed and a new one spawned.

  • Printing Service Pool Size. Allows you to control the standard printing service as well as publication rules that distribute PDF files (as these files are also generated using the printing service). The default setting, BelowNormal, prevents printing or publication rules from generating too many printing requests, which can reduce system performance. You can use the alternate setting, Normal if system performance doesn't seem to be impacted by the printing service (if you are not generating too many printing service jobs).

  • Printing Service Process Priority. This setting determines the priority of processes used for printing.

    • Choose Normal to improve the printing speed at the expense of server responsiveness.

    • Choose BelowNormal to improve server responsiveness during periods of high load on printing services, for example, while publishing multiple publication rules with large attachments.

  • Slicer Item Limit. Sets the maximum number of members with which to populate slicer selectors.

  • Tree View Child Limit. Sets the maximum number of child elements displayed under each folder/node of the Resource Explorer, Functions Explorer, and Dimension Tree.

Once you have completed your changes, click Save.