Enterprise Server Licensing Architectures

Knowledge Base Article: Enterprise Server Licensing Architectures

• Overview of Licensing Models
• The Standard Licensing Model
• Enterprise Root Server Configuration
• Site Server Configuration
• The Enterprise Licensing Model
• Enterprise Root Server Configuration
• Site Server (Child Server) Configuration
• Comparative Analysis: Standard vs. Enterprise
• Diagram: Standard Architecture License Model
• Standard Architecture License Model Description

Overview of Licensing Models

In Sepasoft Enterprise server environments, licensing can be architected in two primary ways: a standard, decentralized model where each site manages its own license, or a centralized enterprise model where a head server manages licenses for all subordinate servers. This document deconstructs the architecture, operational principles, and strategic considerations for each of these distinct licensing models.

The following table provides a high-level summary of their core principles.

The Standard Licensing Model

The Standard Licensing model is the most common architectural setup. Its primary strategic advantage is simplicity in server-to-server communication; it does not require any additional contact between servers for license management. The only required connection is for standard data synchronization, making it a robust and straightforward solution for many distributed environments.

See diagram of the recommended standard model below

Enterprise Root Server Configuration

In a standard setup, the Enterprise Root server functions purely as a data aggregation and analysis hub. It has no running operational responsibilities. This non-operational role is architecturally reinforced by its configuration, which ensures it does not consume a site license. Its purpose is to collect data from the various site servers for centralized reporting and analysis.

It is required to add all core modules to the Enterprise Root, even if they are not currently in use at every site. This ensures the head server is prepared to receive and process data from any new modules purchased for site servers in the future, providing architectural foresight and scalability.

Site Server Configuration

Under this model, each Site Server is licensed individually and configured autonomously based on the Equipment Model. The license is applied directly to the server that performs the operational work, consuming a single site license.

The Enterprise Licensing Model

The Enterprise Licensing model provides a centralized approach to license management, making it an ideal architecture for environments with low-latency network connections between sites. A significant benefit of this model is that it simplifies the process of expansion. However, it introduces a critical requirement: a periodic connection must be maintained between the parent (Enterprise Root) and child (Site) servers to continuously verify license status.

Enterprise Root Server Configuration

In this architecture, the Enterprise Root server acts as the central license manager. It holds the master license, which defines the total number of sites permitted across the entire enterprise, and distributes license validation to its child servers. This configuration also enables the head server to function as an operational node itself.

Site Server (Child Server) Configuration

Site Servers in this model are configured as children of the Enterprise Root. Consequently, sites and machines parameters are omitted from the child server's configuration, as it dynamically inherits its license entitlements from the Enterprise Root.

It is critical to understand that this inheritance model is mandatory and absolute. Any attempt to override it at the local level will result in a licensing conflict and operational failure.

Comparative Analysis: Standard vs. Enterprise

To clarify the fundamental differences in architecture and operation, this section provides a direct comparison of the two licensing models across key attributes.

Diagram: Standard Architecture License Model

RECOMMENDED Model: Primary strategic advantage is simplicity in server-to-server communication; it does not require any additional contact between servers for license management.