--- title: "System Settings" slug: "system-settings" tags: ["Licensing"] updated: 2026-11-05T06:44:56Z published: 2026-11-05T06:44:56Z canonical: "docs.biztalk360.com/system-settings" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.biztalk360.com/llms.txt > Use this file to discover all available pages before exploring further. # System Settings In this article, we provide a detailed overview of the System Settings in BizTalk360. The common configurations updated in system settings will apply to all configured environments. These configurations include data access settings, date/time settings, cache settings under global configurations, as well as monitoring and notification settings. ## **Global Configuration** To configure the global settings, navigate to **Settings ->System Settings->Global configuration.** #### **1) Date Time Settings** The time zone and date time format configured here will be applied to all the features across the application, wherever date and time settings are used. - **System Time Zone** - Set up the system time zone based upon your requirements. - **System Date Time Format** - Set up Date Time format based on need. - From version 10.1 onward if any new user is created, the user will be assigned with the above-configured system time zone and date-time format by default. If they want, they can edit and modify in the user profile. #### **2) Service Account Credentials** When dealing with lots of IBM queues, user might find difficult to provide account details for each one by hand. So, we have added an option in system settings where users can enter the service account credentials. Once the user adds the credentials here, it can be used in IBM MQ configuration for Monitoring. This configuration is also used to scan Best Practice Analyzer report. #### **3) Cache Settings** By default, the Active Directory cache is stored for 2 hours. Click the "Clear Cache" button to clear the Active Directory cache. If any user or group permissions are modified in the Active Directory, use this option to reflect the latest changes. ## ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1791386068535.png) ## **Administration Settings** #### **1) Data Access** This configuration is designed to facilitate a user-friendly experience for operations involving queries, downloading archive files to specific locations, displaying row counts for SQL queries, and general UI rendering options like pagination and URL access. - **Max matches** - These values define the number of results that can show up for different query types. - **Service instances download location** - The folder in the BizTalk360 server where service instance details can be saved from the Message Box queries. - **Secure SQL Row Count** - The maximum number of records a Secure SQL Query can return. - **BizTalk60 Host URL -** Update the URL where BizTalk360 is hosted. Which is used to redirect from email to the specific section in the application. - **Allow Stored Procedure Execution** -By enabling/disabling this you can manage if any stored procedure can be executed from the Secure SQL query. By default, this will be enabled. #### **2) BizTalk Health Monitor** - After installing and configuring BizTalk Health Monitor (BHM) on the server where the BizTalk360 Monitoring service is running, specify the **BHM installation directory path** to enable integration with BizTalk360. - **Ignore Known Issues in Monitoring-** BizTalk360 allows you to mark repetitive BHM findings as **Known Issues**. To exclude these known issues from threshold evaluation and prevent repeated alert notifications, enable the **Ignore Known Issues in Monitoring** option. This ensures alerts are triggered only for newly detected or critical issues. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1791390249845.png) ## **Monitoring Settings** #### **1) Data Monitoring Configuration** The configurations on the monitoring settings page are commonly used for setting monitoring thresholds and processing Data Monitoring schedules. The values configured in monitoring settings such as archive location, minimum frequency will be applied to all the data monitoring schedules and values such as Auto Correct retry count and reset interval and number of threads will be applied to all the artifacts monitoring - **Service instance archive location -** You need to specify a valid file location in order to be able to archive the service instance information. - **Limit Actionable Service Instances** - Enable this to set a maximum limit for service instances that can be Resumed, Suspended, or Terminated in Message Box Data Monitoring. Leave disabled to allow actions on all matching instances. - **Email error description - List count -** You can set the count of error description based on the list. - **Email error description - Char count - You** can set the count of error description based on the character count. - **Enable Group by Description -** Toggle the button to enable group by description. - **Data Monitoring Minimum Frequency** - Users can set the minimum number of minutes that can be set as frequency for schedules. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1791390394921.png) #### **2) Notification** These configuration options provide better control over auto-correct behavior and file handling in email/download operations. Users can customize retry attempts, reset intervals, attachment limits, and file size thresholds for efficient system performance. - **Auto Correct Retry Count** - Users can set the number of retries that must happen for auto correct. It is set to 5 by default. - **Auto Correct Reset Interval -** Users can set the time to reset it when the maximum limit is reached. However, it can be time-consuming to set the reset interval time for every configured auto correct. To overcome this, an option to set the default auto-correct reset interval is introduced in the System setting section. - **Maximum number of attachments in email/download -** You can increase the maximum number of attachments in email/download. - **Total file size allowed per email/download -** You can set the maximum number of file size (MB) allowed per email/download. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1791390437471.png) #### **3) Monitoring Service Configuration** #### **Auto - Restart Monitoring Service** Enable Auto Restart to automatically restart the Monitoring Service when it consumes a high amount of memory on the monitoring server. The Monitoring Auto-Restart feature supports two scheduling options: Specific Interval and Specific Days of Week, providing flexible control over restart timings. 1. **Schedule Type –** Users can choose between Specific Interval or Specific Days of Week. 1. **Specific Interval –** Allows users to define a particular day or interval for restarting the monitoring service. 2. **Specific Days of Week –** Enables users to select one or more days on which the monitoring service will be restarted automatically. 2. **Schedule Time -** Users can specify the Schedule time to restart the monitoring service. 3. Preferred Monitoring Server - Set a preferred server for the BizTalk360 Monitoring service. the service on the preferred server automatically becomes active, and BizTalk360 makes sure it stays up and running. #### Parellel Execution 1. **Maximum number of threads per core -** The maximum number of threads the Monitoring service can run on each logical processor. Lower this value to reduce CPU usage on the monitoring server. 2. **Maximum number of threads to run simultaneously -**The maximum number of alarms, applications and Data Monitoring schedules the Monitoring service can process at the same time. 3. **Maximum number of Data Monitoring Schedules to run simultaneously-** The maximum number of Data Monitoring schedules the Monitoring service can process at the same time. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1791390565340.png) #### **4) Threshold Monitoring Configuration** Health of the Database will be monitored based on the threshold values entered in this section. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-ESTYL1NT.png) ## **Reports Settings** **1) Reports Archive Location** Whenever reports are generated, the report will be sent to the users via E-Mail. If users provide any path in this reports archive location, whenever reports are generated the PDF/Excel file will be saved to this location. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1791390703097.png) ## Security The Security tab in System Settings has two sections Security Protocol and Content Security Policy. #### **1)Security Protocol** Set the TLS protocol version that BizTalk360 uses for its own connections, for Azure endpoints and for web endpoints. By default, BizTalk360 uses the TLS version configured on the server's operating system. You only need to change this setting if BizTalk360 must use a different TLS version from the rest of the server. The Enable TLS Configuration toggle controls this behavior: - Disabled (default): BizTalk360 uses the TLS version that the operating system negotiates. - Enabled: You can set a TLS version separately for BizTalk360, Azure endpoints and web endpoints. > Note > > The TLS version you select must also be enabled on the BizTalk360 server. BizTalk360 cannot use a TLS version that the operating system, a Group Policy or your organization's security policy has disabled. > > For example, if you select **TLS 1.2** but a machine or organization policy blocks TLS 1.2, the connections that use that setting will fail. The features that depend on them, will stop working. #### 2)Content Security Policy A Content Security Policy (CSP) tells the browser which sources the BizTalk360 web interface may load content from. It protects against attacks such as cross-site scripting by blocking scripts and connections from sources you have not trusted. #### Directive modes Each CSP directive has its own mode: | Mode | What it does | | --- | --- | | Off | No header is sent for this directive. | | Report Only | Policy violations are logged in the BizTalk360 log, but requests are not blocked. | | Enforce | Requests from sources that are not allow | #### Directives | Directive | Controls | Settings | | --- | --- | --- | | base-uri | What the page's `<base href>` is allowed to point to | Mode,trusted domains | | worker-src | Where web workers can be loaded from | Mode, trusted domains | | connect-src | Destinations for fetch, XHR and WebSocket calls | Mode, trusted domains | **Additional Report-Only Policy:** Extra directive fragments, such as `style-src 'self'`, that are appended to the Report-Only header exactly as entered. Click **+** to add another fragment. **Excluded Paths:** Requests under these paths get no CSP header at all, for example `/Services.REST/`. Click **+** to add another path. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-DTHAF1JR.png) With Auto-Correct functionality, administrators can set up monitoring on any state based artifact and let the monitoring service try to automatically heal the artifact any time when there is a mismatch between the Expected State and the Current State.