Configuring HyperServer Applications

Adding a new application to HyperServer is done by adding a section to the CFG file of your HyperServer instance.

Here is a typical configuration section for a HyperServer application:

example.cfg

[application-0]
enabled=1
alias=fishfacts
binary_name=fishfacts.exe
max_nodes=4
persistent_node=0

1

Create a new application section

For each new application add a new section in the CFG file. Section name should be application- followed by a unique sequential number. Examples: application-0, application-1, application-2.

2

enabled

Controls whether this application is active.

• enabled=1 — application is enabled and will be used.

• enabled=0 — application is disabled and will be ignored by HyperServer.

3

alias

The alias identifies the application when accessed from a URL. It must be unique among all configured applications in the cluster. Examples: accounting, stock, orders.

These aliases are used to access the application in the URL. Examples:

• http://mywebserver.com/accounting

• http://accounting.mywebserver.com/

4

binary_name

The executable file of the uniGUI application. It should exist in the same folder as HyperServer.

Example: web_accounting.exe

5

max_nodes

Determines the maximum number of Nodes reserved for this application.

• max_nodes=0 — HyperServer will automatically calculate the maximum number of Nodes for the application based on the HyperServer root max_nodes and the total number of applications.

• If all applications have max_nodes=0, HyperServer distributes Nodes evenly among applications (including the default application).

Example: If HyperServer max_nodes = 32 and you have 3 configured applications plus the default application, then: Maximum number of Nodes reserved for each app = 32 / (3 + 1) = 8

You can set explicit values for max_nodes to prevent even distribution and allocate more Nodes to frequently used applications or limit Nodes for rarely used applications (e.g., 1 or 2).

6

persistent_node

Determines if the application requires a Persistent Node.

• persistent_node=1 — application will own a Persistent Node that is always available.

• persistent_node=0 — no Persistent Node.

See Terminology for more details on Persistent Nodes: https://unigui.com/doc/online_help/terminology.htm

In a HyperServer cluster, persistent_node for a given application must be enabled on only one HyperServer instance. Enabling it on multiple instances will result in multiple Persistent Nodes running simultaneously for the same application.