Advanced Server Configuration

Overview

This section describes advanced configuration options for the beA Message Server.

These settings are only required in special scenarios and should generally be handled by technical administrators.

Configuration File

All advanced configurations are managed through the following file:

appsettings.json

Default path:

C:\Program Files\STP AG\beA Message Server\appsettings.json

Multiple DMS Servers

If multiple DMS systems are connected, they must be registered in the configuration file.

Example

{
  "DmsServerSettings": {
    "Servers": [
      {
        "SystemId": "ID1",
        "Description": "DMS Server 1"
      },
      {
        "SystemId": "ID2",
        "Description": "DMS Server 2"
      }
    ]
  }
}

Note
An incorrect JSON format can prevent the server from starting.

Multiple Input Management Systems

It is possible to connect multiple input management systems.

Each system is assigned to a DMS server.

Example

{
  "DmsToImMapping": [
    {
      "DmsServerSystemId": "ID1",
      "ImUrl": "https://tenant1.example.com/",
      "ImUser": "USER_1",
      "ImPassword": "PASSWORD_1"
    }
  ]
}

Note
If no mapping is defined, the default settings will be used.

Synchronization Behavior

You can configure whether messages are moved to STP subfolders after synchronization.

Example

{
  "Preferences": {
    "AfterSyncMoveBrakInboxMessagesToStpSubfolder": true,
    "AfterSyncMoveBrakSentMessagesToStpSubfolder": true
  }
}

Options true → Messages are moved to STP subfolders false → Messages remain in their original folders

When is advanced configuration needed?

These settings are only necessary if:

multiple DMS systems are used multiple input management systems are connected you want to adjust the synchronization behavior

Important Notes

Note
After making changes to the configuration file, you must restart the beA Message Server.

Note
Always validate configuration changes before applying them in production environments.