Oxygen XML: Understanding Floating Licenses for Automated Build Processes

When it comes to using Oxygen XML tools in an automated build process, understanding how floating licenses work is crucial. In this article, we will explore the details of Oxygen's licensing model and provide guidance on how to use floating licenses effectively.

Firstly, it is essential to note that Oxygen licenses are user-based, not machine-based. This means that each person using Oxygen needs their own license or can share a floating license with others if they are not using the software simultaneously.

For automated build processes, you may consider purchasing an inexpensive user-based license for the build process (Oxygen XML Developer Professional) and one or more floating licenses for users who will be using the tool. If your build process does not overlap with user activity, a single floating license might suffice.

However, sharing a floating license between the build process and a pool of users can lead to issues if all floating licenses are already in use. In such cases, the build process may fail due to an inability to acquire a license.

To overcome this problem, you can create a 'license.xml' file with the configuration for your floating license server instead of using 'licensekey.txt'. This approach ensures that the floating license will only be used for the duration of the build process and releases it once completed.

In addition to configuring your floating licenses, you may need to double-check the access rights for the 'licensekey.txt' file in case you have deployed Oxygen as root but are running it under a different user. Make sure to check for read access (rw-r-r-).

For our purposes, we intend to start with a single floating license. In this scenario, the build process would be counted as one of the floating users for the few seconds it is running. However, you may still need to perform an additional step depending on your machine-specific setup.

To use a floating license effectively, follow these steps:

1. Place the license key in a file named 'licensekey.txt' in the same directory as your script.

2. Start Oxygen and enter a valid license key for registration.

By following these guidelines and understanding how Oxygen's floating licenses work, you can ensure seamless integration of your automated build process with Oxygen XML tools.

Error Messages

If you encounter an error message stating 'ERROR: No valid oXygen license found, image generation aborted,' it may be due to incorrect licensing configuration or missing license key files. Make sure to review your setup and verify that the license key is correctly placed in the 'licensekey.txt' file.

In conclusion, using Oxygen XML tools for automated build processes requires a clear understanding of floating licenses. By following the guidelines outlined above, you can ensure successful integration of Oxygen with your build process and create high-quality online documentation with ease.

Oxygen xml torrent