...
Each application server that joins the backend configuration is represented by an a record in the config_server table in the moving_site database. Depending on your deployment scenario, you might want to optimize your environment by adjusting the settings in this table.
...
Whenever a new server joins the deployment, he will be automatically added to the config_server table. On that table you have the following configuration options.
Property | Data Type | Mandatory | Example | Description |
|---|---|---|---|---|
| String |
| SRVIAMAPP01 | The name of the server |
| TINYINT |
| 1 | Wheter Whether or not this specific server should start all available backend services or not. This is usually set to 1. |
| String |
| 127.0.0.1 | Over which network interface the server communicates with other servers. |
| Datetime | 2023-09-01 23:34:55 | The last time the server was active. | |
| Boolean |
| True | If set to true, this server will run tasks from the task lists. If set to false, the server will only execute fast tracked taskedtasks, triggered by UI interaction. In a multi line environment it is best practice to set your backend servers that server the to true and your UI servers to false. This way, they are not occupied with running tasks and can serve the UI faster. Note: If no server is marked with true, or no server is available (last_hearbeatheartbeat_time), also servers with |
...
In the application customer configuration tables, specifically the setting_values table in the appcustomer database, contain a lot off of configurations. Most of them are set through the installer or updater, but some of them might have to be changed at runtime. They are further grouped into categories, indicated by their setting_group.
...