---
title: "09.02. Deployment: Post-installation configuration"
description: ~
---
[Skip to content](https://support-beta.brokeree.com/help/484057349341#main-content)
Open main navigation
Close main navigation
How can we help you?
- There are no suggestions because the search field is empty.
1. [Brokeree Documentation Hub](https://support-beta.brokeree.com/help?hsLang=en)
2. [Dealing Desk](https://support-beta.brokeree.com/help/dealing-desk?hsLang=en)
3. [User manual](https://support-beta.brokeree.com/help/dealing-desk?hsLang=en#user-manual)
# 09.02. Deployment: Post-installation configuration
### Manager (Dealer) rights
The minimum required rights for MT4 Manager, on behalf of which Dealing Desk will process the requests, are the following:
- Supervise trades;
- Dealer;
- Configure server plugins.
If MT server’s admin wants to allow a manager to edit the Dealing Desk’s rules (to connect to the rule editor and add/change the rules), he should also check the *Configure server plugins* right and allow the *Configurable by managers* option in the plugin configuration’s window.
Same applies to MT5 Manager settings. You can also simply choose the **Dealer** preset from the drop-down list.
MT5 subordinate Admins of Trade servers should also be granted with the *Connect using MetaTrader 5 Manager* permission to configure the rules.
### MT4 group configuration
Open MT4 *Administrator → Groups → \[required group\] → Securities → \[required security\].* Securities of groups working under the Dealing Desk supervision must have the Execution option set to “Manual only, no automation”. In the case of an Instant execution of orders, correct behavior is guaranteed only if the *“Fast confirmation on IE with deviation specified”* parameter is checked in the Securities section and check the box as shown in Figure below:
ℹ️
**NOTE**: If “Fast IE confirmation” is not enabled, all requests will be confirmed at the requested price, thus, no slippage will be applied.
### **MT5 routing settings**
In the MT5 Routing rule for Dealing Desk, choose the *Perform action: Process to dealers* option\*,\* and, on the Dealers tab, specify the Manager on whose behalf Dealing Desk operates.
To avoid request filling conflicts with MT5 routing, it is necessary to uncheck the *“Price”* request types.
#### **Dealing Desk Manager API version configuration**
After all the necessary configurations are complete, users need to initiate a first technical launch of the application. The application may not launch successfully for the first time, but it will create the default configuration files as a result. Subsequent launches will be successful from this moment on.
##### **App.json configuration file**
This configuration file stores the [default rule](https://support-beta.brokeree.com/help/484043746496?hsLang=en), sets up the connectivity between MetaTrader and Dealing Desk Manager API service and other parameters of the application.
- **MTCredentials:{}** section of the file sets up the connectivity credentials for the app to be used to connect to a MetaTrader server. Here users need to specify Dealer credentials.
- **DealersCount** - A number of simultaneous Manager connections to the server to parallel processing. If the default value of 3 results in processing with a slight delay, try increasing it gradually with an increment of 2 (5, 7, 9 and so on), measuring the app’s performance and its load on the server. Depending on the individual features of your hardware and software setup, the number resulting in the best performance and in the optimal load may vary.
- **RestartInterval -** The time interval to restart dealer connections (in seconds). It is recommended to use the default value.
- **RulesPath** and the **Default:{}** section of the file are duplicating the configuration of the Default rule.
- **RemovePendingAfterMarginFilter** - if *true*, pending orders whose activations were rejected by the [Exposure limit filter](https://support-beta.brokeree.com/help/484043746497?hsLang=en) filter are to be removed (same as MT does when pending activation is not possible because of lack of margin). Please note: when it is set to *false*, the pendings left after rejection will not be activated for 200 seconds even if they begin to pass the conditions (a restriction of MT4 Manager API version only).
- **ConnectionTimeout -** Time, after which connection attempts are stopped. Specified in milliseconds.
#### **Dealing Desk Plugin version configuration**
Open MetaTrader *Administrator → Plugins* section. You will find your DealingDesk plugin in the list. Click on it to enter parameters as follows:
- `AppId`
The ID of the plugin. Must be a unique number across the plugin instances on the server.
Example value:
```
345
901
```
- `DealerAccount`
The MetaTrader login of the dealer (manager) account on behalf of which Dealing Desk will process the requests.
Example value:
```
2
```
- `RulesPath`
The path to the *rules.json* file where settings for all rules currently available in the Rule editor will be stored. By default, the *rules.json* file will be automatically created in the *MetaTrader Server → Plugins → Dealing Desk* folder.
Example value:
```
rules.json
```
- `UseAsyncProcessing`
***For MT4.*** Enables (*true*) or disables (*false*) requests’ processing in parallel threads. Multi-thread processing may increase the plugin’s performance.
Default value is *true.*
Example value:
```
false
```
- `RemovePendingAfterMarginFilter`
Same as in the Manager API version’s *app.json*.
Example value:
```
true
```
- `Jobs.ReloadCacheTimer`
Cache update timeout. Lower the value to get more precise results of exposure calculations (but this may increase the server load).
Example value:
```
7200
```
- `Logging.LogLevel.Default`
Determines the level of messages written into .log files. Higher levels include all previous ones. Levels:
1. `Error`
2. `Warning`
3. `Information`
4. `Trace`
#### **Rules.json**
This file contains the rules in a text format. By default, it is located in the plugin’s folder on the MetaTrader server (or in the Manager API’s installation folder).
The file is modified every time the *Save* button is pressed in the Rule Editor, and the Plugin and Manager API get the rules from the file upon the server restart. However, the Rule Editor loads the updated rules also in the Plugin and Manager API in real time, so the server restart is not required when updating the rules.
[](https://support-beta.brokeree.com/?hsLang=en)
[mailto:email@email.com](mailto:email@email.com)
Copyright © 2026, brokeree.com