Application Server Configuration

Owned by Silvan Grüter, created
Last updated: 08. Aug 2024
1 min read

Introduction

There are various general settings that affect the application server.

Server Configuration Tables

Each application server that joins the backend configuration is represented by 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.

Properties

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

Property

Data Type

Mandatory

Example

Description

Name

String

SRVIAMAPP01

The name of the server

load_all_services

TINYINT

1

Whether or not this specific server should start all available backend services or not. This is usually set to 1.

ip_servicenetwork

String

127.0.0.1

Over which network interface the server communicates with other servers.

last_heartbeat_time

Datetime

 

2023-09-01 23:34:55

The last time the server was active.

enable_scheduled_tasks

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 tasks, triggered by UI interaction.

In a multi line environment it is best practice to set your backend servers 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_heartbeat_time), also servers with enable_scheduled_tasks set to false will run tasks. Once another server is marked with true, or an existing server has recovered, it will stop processing the tasks.

© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.