Installing Oxygen XML Developer on Windows Server

Choosing an Installer

You can install Oxygen XML Developer on Windows using one of the following methods:

Install using the Windows installer.
Install using the Windows installer in unattended mode.
Install using the All Platforms installer. Choose the all platforms installer if you have trouble installing using the Windows installer.

System Requirements

System requirements for a Windows Server install:

Operating systems

Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

CPU

Minimum - Intel Pentium III™/AMD Athlon™ class processor, 1 GHz
Recommended - Dual Core class processor

Memory

Minimum values per user - 512 MB of RAM
Recommended values per user - 2 GB of RAM

Storage

Minimum - 400 MB free disk space
Recommended - 1 GB free disk space

Java

Oxygen XML Developer requires Java. If you use the native Windows installer, Oxygen XML Developer will be installed with its own copy of Java. If you use the all platforms installer, your system must have a compatible Java virtual machine installed.

Oxygen XML Developer supports only official and stable Java Virtual Machines with the version number 1.6.0 or later (the recommended version is 1.7) from Oracle available at http://www.oracle.com/technetwork/java/javase/downloads/index.html. Oxygen XML Developer may work with JVM implementations from other vendors, but there is no guarantee that those implementations will work with future Oxygen XML Developer updates and releases.

Oxygen XML Developer uses the following rules to determine which installed version of Java to use:

If you install using the native Windows installer, which installs a version of Java as part of the Oxygen XML Developer installation, the version in the jre subdirectory of the installation directory is used.
Otherwise, if the Windows environment variable JAVA_HOME is set, Oxygen XML Developer uses the Java version pointed to by this variable.
Otherwise the version of Java pointed to by your PATH environment variable is used.

If you run Oxygen XML Developer using the batch file, oxygenDeveloper.bat, you can edit the batch file to specify a particular version to use.

Install Using the Windows Installer

To install Oxygen XML Developer using the Windows installer, follow these steps:

Make sure that your system meets the system requirements.
Download the Windows installer.
Validate the integrity of the downloaded file by checking it against the MD5 sum published on the download page.
Run the installer and follow the instructions in the installation program.
Start Oxygen XML Developer using one of the following methods:
- Using one of the shortcuts created by the installer.
- By running oxygenDeveloper.bat, which is located in the install folder.
To license your copy of Oxygen XML Developer go to Help > Register and enter your license information.

Install Using the All Platforms Installer

To install using the all platforms installer, follow these steps:

Download the all platforms installation package (oxygenDeveloper.tar.gz) to a folder of your choice.
Extract the archive in that folder.
Oxygen XML Developer is now installed in a new sub-folder called oxygenDeveloper.
Optionally, you can move the directory where you installed Oxygen XML Developer to your applications directory. You can also rename it to contain the product version information. For example, you can rename it as oxygenDeveloper17.1.
Start Oxygen XML Developer by running oxygenDeveloper.bat, which is located in the install directory.
To license your copy of Oxygen XML Developer go to Help > Register and enter your license information.

Configuring Windows Terminal Server

Windows Terminal Server configuration procedure.

Install Oxygen XML Developer on the server and make its shortcuts available to all users.
If you need to run multiple instances of Oxygen XML Developer, make sure you add the -Dcom.oxygenxml.MultipleInstances=true parameter in the .bat startup script.
Make sure you allocate sufficient memory to Oxygen XML Developer by adding the -Xmx parameter either in the .bat startup script, or in the .vmoptions configuration file (if you start it from an executable launcher).