Introduction
Each application server that joins the backend configuration is represented by an 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.
Properties
Whenever a new server joins the deployment, he will be automatically added 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 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 tasked, triggered by UI interaction. In a multi line environment it is best practice to set your backend servers that server the 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_hearbeat_time), also servers with |
