Setting up a Load-Balanced Server

Describes the required setup for scaling a deployment to a larger number of users.

To scale a deployment to a larger number of users and to increase the availability, Oxygen XML WebApp Component can be deployed on a set of load-balanced servers. This topic describes the required setup for such a scenario.

Configure Session Stickyness

Every Oxygen XML WebApp Component server keeps the state of the edited documents in memory for performance reasons. This implies that every user should connect to the same back-end server for the duration of an editing session. To achieve this result in a load-balanced setting, you should enable session stickyness.

Configure Server Health Checks

To detect unhealthy servers, Oxygen XML WebApp Component offers a health check REST API. The endpoint has the following interface:

URL: rest-public/status
Response status code: 200 for a healthy server and 503 for an unhealthy server.
Response body: For an unhealthy server, the response body contains a text description of the problem.

Configure the License Server

All Oxygen XML WebApp Component servers can use the same pool of floating licenses. To this end, they all need to be configured to use the same license server.

Share Options Between All Instances

The configuration options are stored in the file system in a directory that can be changed using the oxygen.data.dir system property. In order for all instances to use the same options, oxygen.data.dir should point to the same directory on a shared file system.