Zum Hauptinhalt springen
Deutsch
|
English

LOADBALANCERMODEON - Detailed description

FM-Portal

IC0000
FM-Portal

Overview

Parameter:LOADBALANCERMODEON
Category: LoadBalancer
Default value: 0
Product: eTASK.Other (LoadBalancer)

What does this parameter do?

Determines whether the FM portal is operated behind a load balancer. If the value 1 is entered, LoadBalancer mode is active. The default value is 0. When enabled, the portal uses a centrally configured base URL for all generated links and redirects instead of determining the URL from the current HTTP request. This ensures that all portal instances behind the load balancer generate identical URLs, regardless of which server processes the request.

What is this parameter used for?

  • Operating multiple portal instances behind a load balancer

  • Ensuring consistent URL generation across all servers

  • Preventing session issues caused by inconsistent URLs

  • Horizontal scaling in production environments

  • High-availability scenarios with multiple backend servers

  • Cloud deployments with auto-scaling groups

  • Preventing the exposure of internal server names in generated links

  • Support for SQL Server Session State without sticky sessions

Technical Details (for Administrators)

Format: Integer (treated as Boolean)
Default value: 0

Valid values:

  • 0 = LoadBalancer mode is not active (default)

  • 1 = LoadBalancer mode is active

Important notes:

  • When disabled (0), each instance dynamically determines its URL from the HTTP request

  • When enabled (1), all instances use the centrally configured URLBASE

  • This parameter affects URL generation for links, redirects, and API responses

  • Requires the URLBASE parameter to be configured correctly

  • Affects URL generation in database functions

  • No changes required for single-server installations

Interaction with other parameters:

  • EXECUTETIMERJOBS: Prevents duplicate execution of background jobs across multiple instances—should only be set to 1 on a single instance

  • URLBASE: Contains the public portal URL used in LoadBalancer mode

When should you change this value?

Set the value to 1 (enable LoadBalancer mode) if:

  • You are running multiple portal servers behind a load balancer

  • Horizontal scaling is implemented to handle higher loads

  • High availability needs to be ensured through server redundancy

Leave the value set to 0 (default) if:

  • Only a single portal server is being operated

  • No load balancer infrastructure is available

Important Notes

  1. URLBASE must be configured
    correctly Before activating load balancer mode, the URLBASE parameter must be set to the public, externally accessible URL (e.g., https://portal.firma.de). Incorrect URLBASE values result in broken links.

  2. Coordination with EXECUTETIMERJOBS required
    In a multi-server environment, EXECUTETIMERJOBS should only be set to 1 on one instance to prevent duplicate execution of timer jobs. All other instances should have EXECUTETIMERJOBS=0.

  3. Thorough testing after activation
    After switching to LoadBalancer mode, all critical functions should be tested: login, navigation, report generation, workflow transitions, API calls.

  4. Changes possible during operation
    Activation can be performed without downtime. However, the switch should be coordinated with other configuration changes.

Security

Does changing this parameter affect security?

No, changing this parameter has no impact on security.

Practical example

Initial situation: A company operates a portal server (PORTALSERVER-A) without a load balancer using the public URL https://portal.firma.de. Users report longer access times during peak load periods, e.g., morning logins. The configuration shows LOADBALANCERMODEON=0.

Configuration: The administrator sets up a second server with a portal installation, sets URLBASE=https://portal.firma.de, and changes LOADBALANCERMODEON to 1 on both servers. Additionally, EXECUTETIMERJOBS=1 is set on PORTALSERVER-A and EXECUTETIMERJOBS=0 on the other server.

After the change:

  • All generated links uniformly display https://portal.firma.de, regardless of the processing server

  • Load peaks are distributed across two servers

  • Timer jobs run on only one server; no more conflicts

  • The load balancer can use round-robin

Result: A stable multi-server environment with consistent URLs and improved user experience. Session stability is significantly increased, and the infrastructure is prepared for further growth.

Recommended setting

For standard installations:0(LoadBalancer mode disabled)

Reason:

  • Most installations run on a single server

  • No load balancer is present, so it is not required

  • Dynamic URL detection works reliably in single-server mode

  • Simpler configuration without additional dependencies

  • Default setting for typical enterprise installations

War dieser Artikel hilfreich?