Oxygen XML Forum

Hi there,

We are trialling Oxygen, and were particularly drawn to oxygen because of the command line generation - we intend to run this in an automated build to create online docs when the schema is checked in. I'm just spiking this before we commit to a license, and I have hit a slight issue. The build runs fine on my OSX laptop, but when I move it to a linux machine I get:

[java] ERROR: No valid oXygen license found, image generation aborted...:
[java] --------------------------------------------------
[java] Please register a valid license key in one of the following ways:
[java] 1) Start oXygen and enter a valid license key for registration
[java] 2) Place the license key in a file named "licensekey.txt" in the same directory as this script
[java] --------------------------------------------------

despite the fact that the licensekey.txt is in the same place. Is the license machine specific, or is there a further step to perform?

I think we intend to start with a single floating license - how would this work in that case? Would the build process be one of the floating users for the few seconds it's running?

Cheers,
Dean

Hello,

I've just re-tested this in Linux and it works as expected.

I created a file named 'licensekey.txt' with the the license key (all nine lines of text located between the START and END markers). I placed this file in the Oxygen installation directory and checked if it has the correct access rights (check for read access: rw-r--r--). I would recommend double checking this if you have deployed Oxygen as root, but are running it as a different user.

Regarding the floating license question, the answer is yes, the floating license will only be used for the duration of the build process. If you use floating licenses with a floating license server, you should use the 'license.xml' file with the configuration for the floating license server instead of 'licensekey.txt'. More details can be found here:
Oxygen XML Editor User Manual - Obtaining and Registering a License Key

However, I'd like to point out that if you share floating licenses between the build process and a pool of users, you may find that the build process will sometimes fail if it couldn't acquire a license (if all the floating licenses are already in use). This is especially problematic if you have a single floating license.
If the build process does not overlap with the users, then it should be fine even with one floating license. Otherwise, it would probably be more practical to purchase the most inexpensive user-based license for the build process (Oxygen XML Developer Professional) and one or more floating licenses for the users.

Regards,
Adrian

PS: Please note that all Oxygen licenses are user-based, not machine based. So if several people will use Oxygen on one machine, each should have his/her own license or you can use a floating license for all of them if they are not using it at the same time. An automatic process that uses an Oxygen tool/script counts as a user.

Thanks Adrian.

"I placed this file in the Oxygen installation directory"

I think this is the problem, I haven't *installed* oxygen, just copied the libs onto the build machine, and the licensekey.txt is in the folder that maven is running in.

Is there a headless/unattended install?

Thanks,
Dean

Hi,

For Linux you can either:
- use an unattended install (recommended). Download the Linux installer (.sh) for your OS architecture and run it with the -q parameter. e.g. oxygen-32bit.sh -q or oxygen-64bit.sh -q
- use the All platforms distribution: Oxygen XML Editor - Download All Platforms. This requires Java SE 6 or OpenJDK 6 to be installed.

Regards,
Adrian

Thanks Adrian,

I did the install, which didn't fix the issue, but then I added the current directory to the classpath (I'd missed that in the shell script), and it now works. Not sure if both steps required.

Thanks for your help,
Dean

Hi,

The install was not necessary, but the instructions assumed you were calling one of the Oxygen scripts and now I understand that you have your own.

Alternatively you could have moved the 'licensekey.txt' file to 'Oxygen/lib'. That also works.

Regards,
Adrian