EXECUTETIMERJOBS - Detailed description

Overview

Parameter:EXECUTETIMERJOBS
Category: LoadBalancer
Default value: 1
Product: eTASK.Other (LoadBalancer)

What does this parameter do?

This parameter determines whether automated background tasks (timer jobs) should be executed on a portal instance behind a load balancer. Timer jobs are recurring system tasks such as email sending, data cleansing, or status updates.

What is this parameter used for?

• Controlling timer job execution in load balancer environments

• Preventing conflicts caused by multiple simultaneous executions of the same jobs

• Central control over which portal instance handles background tasks

• Ensuring that automated processes are executed exactly once

Technical Details (for Administrators)

Format: Integer
Default value: 1

Valid values:

• 0 = Timer jobs are not executed on this instance

• 1 = Timer jobs are executed on this instance

Important notes:

• In load balancer environments, the value 1 set

• If multiple instances have the value 1 , timer jobs may be executed multiple times

• This can lead to data inconsistencies, duplicate emails, or system conflicts

• In single-server installations, the default value 1 be retained

When should you change this value?

Set the value to 0 (disable timer jobs) if:

• The portal instance is running behind a load balancer with multiple servers

• This instance is not intended for running timer jobs

• Another dedicated instance handles the timer jobs

• Resources on this instance should be reserved for user requests

Set to 1 (enable timer jobs) if:

• It is a single-server installation

• This instance is configured as a dedicated timer job instance

• In a load balancer environment, this instance is intended to handle background tasks

• No other instances are running timer jobs

Important Notes

1. Load balancer configuration
   In a load balancer environment with multiple portal instances, exactly one instance must have the value 1 . All other instances must be set to 0 .

2. Dedicated Timer Job Instance It is recommended
   to use a dedicated Portal instance for timer jobs that is not integrated into the load balancer for user requests. This prevents performance degradation during resource-intensive background processes.

3. Single-server installation
   For single-server installations without a load balancer, the value must 1 must remain set to 1, otherwise timer jobs will no longer run and important system functions will fail.

4. Relationship with LOADBALANCERMODEON
   This parameter should be configured in combination with the LOADBALANCERMODEON parameter to set up the system correctly for load balancer operation.

Security

Does changing this parameter affect security?

No, this parameter has no direct impact on security.

Practical example

Initial situation:
A company operates eTASK behind a load balancer with three portal instances (servers A, B, and C). All three have EXECUTETIMERJOBS set to the default value 1. Scheduled jobs, such as nightly email delivery, are executed three times; users may receive the same notifications

three times.

Configuration:
The administrator sets the value EXECUTETIMERJOBS to 0. Only Server A retains the value 1.

After the change:

• Server A executes all timer jobs as scheduled

• Servers B and C process only user requests

• Emails are sent only once

• Data cleansing is performed in a controlled manner without conflicts

• The load is optimally distributed between user requests (B, C) and background tasks (A)

Result:
Elimination of duplicate executions and optimal resource utilization in the load balancer environment.

Alternative configuration:

A dedicated fourth instance (Server D) is set up that is not integrated into the load balancer for users. Server D receives EXECUTETIMERJOBS = 1, while A, B, and C are set to 0 . This completely separates background tasks from user interaction.

Recommended setting

For standard installations:1(Single server without load balancer)

Reason:

• In single-server installations, timer jobs must run on this instance

• Without timer jobs, important system functions will fail

• The default value ensures proper operation

Exceptions (load balancer environments):

• Only one instance should 1 (ideally a dedicated timer job instance)

• All other instances must be set to 0 set

• With three servers: Server A = 1, Servers B and C = 0

Tip: In load balancer environments, set up a dedicated instance for timer jobs that is not responsible for user requests. This maximizes performance and stability.