oXygen WebApp uses a floating license model, where the license key is stored on a server and
individual users consume license seats from a common pool.
How it works
The license key contains the maximum number of users that can simultaneously access the
WebApp at any given moment. After a period of inactivity, the license allocated to that user
becomes available.
While no personal information is sent to the server, a cookie that identifies the user is
auto-generated. Note that the use of two different browsers (for example, Firefox and
Chrome) by a single user, will consume two floating licenses. However, using two or more
windows or tabs of the same browser, consumes a single floating license.
Licensing
Follow these steps to license a deployment of Oxygen XML WebApp:
- To obtain a license key, please contact support@oxygenxml.com.
- Install a floating license server. If you decide to use an HTTP license server,
you can deploy it in the same Tomcat server, alongside with Oxygen XML WebApp.
- Configure the license server connection.
Configuring the license server
The connection to the server should be configured in a file located at
WEB-INF/license.properties. It should have the following keys.
- licensing.server.type
- Type of licensing server. Can be one of http or
standalone.
For an HTTP server, configure the following parameters:
- licensing.server.url
- The URL of the license server
- licensing.server.user
- The user name used for the license server
- licensing.server.password
- The password used for the license server
For a standalone server, configure the following parameters:
- licensing.server.host
- The host name of the licensing standalone server
- licensing.server.port
- The port of the licensing standalone server
A configuration file might look like this:
licensing.server.type=http
licensing.server.url=http://example.com:8080/oxygenLicenseServlet/license-servlet
licensing.server.user=admin
licensing.server.password=******