Oxygen XML Web Author 18.1.0

Chapter 1: Introduction
Chapter 2: Using Oxygen XML Web Author
- 2.2.1: Web Author Interface
- 2.2.2: Creating or Opening Documents
  - 2.2.2.1: Predefined Document Types (Frameworks)
- 2.2.3: Editing Documents
  - 2.2.3.1: Editing Actions
    - 2.2.3.1.1: How to Perform Common Editing Tasks
    - 2.2.3.1.2: How to Perform Common Review Tasks
  - 2.2.3.2: Content Completion Assistant
  - 2.2.3.3: Smart Paste Support
  - 2.2.3.4: Validating XML Documents
  - 2.2.3.5: Automatic Spell Checking
- 2.2.4: Accessing a File Repository
  - 2.2.4.1: Using a Git Repository
  - 2.2.4.2: Using a WebDAV Server
  - 2.2.4.3: Using a SharePoint Repository
- 2.2.5: Browser Compatibility
- 2.2.6: License Issues
Chapter 3: Deploying Oxygen XML Web Author
- 3.3.1: Installation
  - 3.3.1.1: Increasing the Memory Allocated to Oxygen XML Web Author
  - 3.3.1.2: Restarting Oxygen XML Web Author
- 3.3.2: Licensing
  - 3.3.2.1: Setting Up a Floating License Server
    - 3.3.2.1.1: Setting up an HTTP Floating License Server
      - 3.3.2.1.1.1: Upgrading Your HTTP Floating License Server
      - 3.3.2.1.1.2: Replacing a Floating License Key in an HTTP Floating License Server
      - 3.3.2.1.1.3: Getting More Information From the Report Page
- 3.3.3: Upgrading
- 3.3.4: Administration Page
  - 3.3.4.1: Configuring the License Server Connection
  - 3.3.4.2: Adding and Configuring Plugins
    - 3.3.4.2.1: Creating a Plugin Configuration Page
  - 3.3.4.3: Adding or Removing a Framework
  - 3.3.4.4: Configuring Proxy Settings
- 3.3.5: Supported Plugin Integrations
  - 3.3.5.1: Configuring a Git Plugin to Use GitHub Authentication
  - 3.3.5.2: Configuring WebDAV Support
  - 3.3.5.3: Configuring a SharePoint Plugin Integration
- 3.3.6: Customizing Options
  - 3.3.6.1: How to Set a System Property
- 3.3.7: Adding Custom Dictionaries for the Spell Checker
- 3.3.8: Setting up a Load-Balanced Server
- 3.3.9: Configuring Minimal File Access Permissions
- 3.3.10: Sharing a Tomcat Instance
- 3.3.11: Using an IIS Reverse Proxy
- 3.3.12: Locating and Configuring Logs
- 3.3.13: Troubleshooting Oxygen XML Web Author Errors
Chapter 4: Form Controls
Chapter 5: Oxygen XML Author Options Supported by Oxygen XML Web Author
Chapter 6: Feature Matrix
Copyright

Setting Up a Floating License Server

Installing a License Server to Manage Floating Licenses

Oxygen XML Web Author uses floating licenses. To manage them you need to install an Oxygen XML Web Author floating license server.

Activating Floating License Keys

To help you comply with the Oxygen XML Web Author EULA (terms of licensing), all floating licenses require activation. This means that the license key will be locked to a particular license server deployment and no multiple uses of the same license key are possible.

During the activation process, a code that uniquely identifies your license server deployment is sent to the Oxygen XML Web Author servers, which in turn will sign the license key.

Split or Combine License Keys to Work with Your License Servers

A license server can only manage one license key (which can cover any number of floating licenses). If you have multiple license keys for the same Oxygen XML Web Author version and you want to have all of them managed by the same server, or if you have a multiple-user floating license and you want to split it between two or more license servers, please contact support@oxygenxml.com and ask for a new license key.

Was this helpful?